Free trial · first space this afternoon

Your critical runbook can't live in an ex-employee's Drive.

Spaces, pages, and revisions with per-team permissions. No per-viewer license, no runbook stuck in the personal Drive of someone who left.

REVISIONS · 12
PR
Priya R.2h ago
Updated rollback section
JM
John M.2d ago
Added post-rotation checklist
AL
Anna L.2w ago
Initial version published
Spaces › Infrastructure › Runbooks
AWS credential rotation
securityrunbook
1. Goal

Rotate the IAM admin credentials on the production AWS account.

2. Prerequisites
aws --version aws configure list-profiles
Confirm access to Movitera Vault
Rotate the key in the IAM console
Auto-saved 3s ago
For IT teams that have already lost a critical runbook the day someone left.

Team knowledge can't live in one person's head.

You look for the runbook and find four results. None of them works: one locked in a personal Drive, one in a 2023 Slack thread, one behind a license paywall, one in someone's WhatsApp.

GLOBAL SEARCH · IT
AWS credential rotation
4 results
drive.google.com/john-smith
runbook-aws-rotate.md
Personal Drive · John left 8 months ago
Access denied
#infra
"anyone know how to rotate the AWS key?"
Thread from 2023 · no reply since
Stale
notion.so/team/runbooks
AWS Credential Rotation · v4
Notion · your team doesn't have a viewer seat
License required
Team memory
Ask the person who did it last
Last person who knew: on vacation until Thursday
Tribal knowledge
MOV 0.1

The same procedure lives in five places.

When you need it, you pick the wrong one. Every new page fragments it further.

MOV 0.2

Someone leaves, the runbook disappears.

Onboarding starts from zero again. The last person never documented — or documented in a Drive nobody else can open.

MOV 0.3

Per-viewer licenses lock out half the team.

Notion and Confluence charge per viewer. Half the team ends up without access to what they need to read.

Four sources, zero answers. And somebody ends up opening the chat again to ask.

One place. Every edit. Every teammate.

Spaces, pages, and revisions in the same workspace as the rest of IT operations. Every edit becomes a revision. The whole team, already included.

01

One place, with per-team permissions.

Spaces by area, nested pages, semantic search. Whoever needs to see it, sees it — no more "which runbook is the real one?".

Infrastructure › Runbooks › AWS credential rotation
42 members · whole team
SPACES
Infrastructure32 pages
Runbooks14
Architecture8
Incidents10
Onboarding18 pages
Support24 pages
AWS credential rotation
securityrunbookUpdated 2h ago · Priya R. · v12

Rotate the IAM admin credentials on the production AWS account. Quarterly procedure plus incident trigger.

124 linhas
HISTORY · 12 REVISIONS
PR
Priya R.2h ago
Updated rollback section
JM
John M.2d ago
Added post-rotation checklist
AL
Anna L.2w ago
Initial version published
PR
Priya R.3w ago
Fixed CLI command
02

Every edit becomes a revision.

See who changed what and when, and roll back to any version in one click. The fear of breaking the page goes away.

03

The whole team reads — no ghost viewers.

No per-viewer license. Documenting stops being an extra cost. Everyone has access from day one.

From the first runbook to the next new hire's first week: knowledge lives with the team, not in one person's head.

From blank page to fully documented team.

Three steps. In one afternoon, runbooks stop disappearing.

#1

Create the first space

Infrastructure, onboarding, support — each area with its documents.

#2

Write your first runbook

Rich Markdown editor, auto-saved every 3 seconds. No plugins, no new syntax to learn.

#3

Invite the whole team

Permission per space or page. Everyone on the plan already included, no extra license.

Pricing

Free forever for individuals. $6/user/month for teams — that’s 5–10× less than Jira, Freshdesk, or Zendesk.

Individual

Free

Start free

Get started on your own — free forever.

  • Access to Vault
  • Work solo
  • Unlimited credentials

Pro

Recommended

$6.00 per user/month

Start your 14-day free trial

Full access for teams — 5–10× cheaper than most ticketing tools.

  • Access to Vault
  • Access to SRM
  • Access to Closure
  • Access to Tasks
  • Access to Wiki
  • Access to Forge
  • Access to Inventory
  • Unlimited credentials and .envs
  • Unlimited tickets
  • Unlimited activities
  • Unlimited users

Teams that stopped losing runbooks when someone leaves

Tech leads, SREs, and engineering managers who took documentation out of the personal Drive.

I moved the team off paid Notion. Same writing experience, no per-viewer charge. Paid for the whole Movitera plan in the first month.

J

Junior, Tech Lead at a B2B SaaS

Revision history made me comfortable letting editors loose. If someone breaks the page, I roll back in one click.

M

Marcela, SRE at a marketplace

Onboarding dropped from two weeks to three days. The Onboarding space became the default script.

R

Raul, Engineering Manager at a fintech

F.A.Q.

Short answers on Movitera Wiki.

Stop searching for the runbook. Start documenting.

Try free for 14 days. First space, first runbook, first invite — all this afternoon.