Solutions IT process documentation

The runbook is written while you run it.

Stepwright records on Windows, so it sees the consoles, RDP sessions and legacy admin tools a browser extension never will. Each procedure comes out numbered, screenshotted and narrated.

Create your first runbook See how it works

Free plan, no credit card. Windows recorder and browser extension.

In short

Stepwright documents IT procedures by recording them on the real systems — desktop consoles, RDP sessions, admin panels, legacy apps — and building a numbered runbook with a screenshot and a written instruction for every step. Your spoken narration becomes step context, secrets can be redacted on paid tiers, and a console change means re-recording only the steps it affected.

The runbook lives in one admin's head, so a routine task becomes an incident the week they are away.

The procedures that exist are walls of text. Nobody can tell which control in a crowded console they mean.

Half the work happens in RDP sessions, hypervisor consoles and legacy panels that browser capture cannot see.

One console redesign and every document goes stale, so people stop reading them and ping you instead.

How a procedure becomes a runbook.

You perform the task once on the real systems while Stepwright captures the screen and what you say about it. Out comes a numbered runbook with a screenshot per step and a narrated video of the same run. When a console changes, you record only the steps that moved.

01 / 04

Record on the systems the work actually happens on

Active Directory, your RMM, a hypervisor console, a remote session into a line-of-business app from 2009. The Windows recorder captures all of them the same way it captures a browser tab, so nothing gets left out of the runbook because the tool could not see it.

  • RDP session
  • Hypervisor console
  • MMC snap-in
  • Legacy admin panel

02 / 04

Say the preconditions out loud, not just the clicks

'Confirm the backup completed before you touch the primary.' The checks and the gotchas are the part of a runbook that stops an outage, and they are the part a click recording loses. Speak them and they land as step context. Hostnames and acronyms go in the custom vocabulary on Teams so they transcribe clean.

Infrastructure · Runbook

Failover

eu-central-1 · primary

Standby ready

Last backup 18 minutes ago
Replication lag 0.4s
Open sessions 37
Change window Required
A spoken note captured with the recording: “Replication lag on db-02 has to be under a second.”

03 / 04

Take the credentials out before the runbook goes wider

Guides are private by default. On paid tiers, redact hostnames, tokens, connection strings and customer records in the screenshots, so a procedure can go to a contractor, an auditor or the rest of the team without the secrets it was performed with travelling along with it.

Stepwright: take the credentials out before the runbook goes wider

Redacted before sharing

16 fields

  • Hostnames
  • API keys
  • Connection strings

04 / 04

After a console redesign, record the steps that moved

Vendors move buttons. Re-record the two steps that changed and the runbook updates in minutes, narrated video included. Export to PDF, HTML or Markdown for the wiki, a ticket or the knowledge base you already run.

What an IT team gets out of it.

Fewer single points of failure

Procedures leave one admin's head and become guides the team can run, so a day off stops turning a routine task into an incident.

Reaches desktop and legacy tools

Native Windows recording captures RDP sessions, hypervisor consoles and old admin panels that browser-extension tools cannot see at all.

Screenshots end the ambiguity

Each step shows the exact control that was used, so 'click the settings gear' is never guesswork in a console with forty of them.

Jargon transcribed correctly

Custom vocabulary on Teams keeps hostnames, product names and acronyms intact in the written steps instead of letting generic transcription mangle them.

Safe to hand to a contractor

Private by default, encrypted in transit and at rest, with redaction on paid tiers to strip secrets and customer data before a runbook leaves.

Documentation people still trust

Updating in minutes after a console change is what keeps a runbook accurate, and accurate is the only reason anyone reads one instead of pinging you.

Questions from IT teams.

Related

Yes, and it is the main reason IT teams pick it. Stepwright is a native Windows desktop recorder, so RDP sessions, hypervisor and admin consoles, MMC snap-ins and legacy line-of-business apps are captured the same way a browser tool is. Browser-extension capture cannot see any of those.

Guides are private by default and encrypted in transit and at rest. On paid tiers you redact the screenshots — tokens, passwords, internal hostnames, customer records — before the runbook is shared with anyone.

Add them to the custom vocabulary in settings, which is part of the Teams plan. Your spoken narration then lands accurately in the written steps, so IT-specific terms appear as written rather than as whatever generic transcription guessed.

Yes. Export any guide to PDF, HTML or Markdown and paste or embed it where your team already looks. Stepwright captures and maintains the procedure; your wiki stays its home.

Record the next routine task.

You were going to do it anyway. The runbook is the by-product. The free plan needs no card.

Create your first runbook See pricing