You know how it all really works — the deploy quirks, the 2am fixes, the reason that one setting exists. The Handover Folder turns that hard-won knowledge into a runbook a teammate can follow on their own, so a departure, a vacation, or a reorg becomes just a normal week.
You already keep the whole picture in your head: which service owns what, the safe way to deploy, the log line that means trouble, the workaround everyone forgot to write down. It works — right up until you are on holiday, or you move teams, or you simply want a weekend that stays yours.
So the knowledge stays tribal. A teammate hits a wall and pings you. On-call wakes someone at 2am for something you could fix in a minute. New hires spend three weeks learning what one good page could have told them on day one.
The fix is refreshingly ordinary: one runbook per system, a shared structure, and a habit of writing the answer down the first time you find it. That is the whole idea — and it is the whole product.
You do not need to be always available. You need the system to be followable without you.
One free page to prove the idea, one starter system for your first runbook, one complete continuity system. No subscription, ever.
A one-page handover checklist plus the runbook skeleton you can fill in for your trickiest system today — no account, no email.
owner · access · steps patternThe full starter system: a ready-made runbook template set — service overview, on-call, deploy, rollback, and ‘what breaks and why’ — for one system.
The Starter plus the full continuity system: an incident-response playbook, a self-serve onboarding path, and the team knowledge-map method.
Drop-in on-call docs: an escalation ladder, an alert triage sheet, and a first-15-minutes checklist — so the calm is written down before you need it.
Want to go deeper? Companion toolkits: SRE Platform Kit · DevOps Toolkit.
Whatever you run, the knowledge that keeps it alive deserves a calmer home than one person’s memory.
Leave cleanly. Hand over the system, not a mystery, and keep your reputation golden.
Find the answer at 2am without waking anyone. The runbook already knows.
Turn tribal knowledge into a shared standard so no one person is a single point of failure.
Sail through vacations, reorgs, and ‘the person who knew that moved on’ with your uptime intact.
Three small moves. Then it just quietly works.
Copy the skeleton into the tool you already use. One page per service is enough to start — you can deepen it later.
Use the owner · access · steps shape and plain language. Point to the secrets store; never paste the secret.
When you learn something the hard way, add the line right then. A runbook stays trustworthy only if it keeps up.
Your runbook should hold everything a capable teammate needs to run the system with confidence — the map, the steps, and the reasons behind them. It should never hold the secrets themselves.
That means no credentials, no tokens, no private keys pasted into a doc “just so it works.” Secrets belong in a real secrets store — Vault, your cloud’s secret manager, your CI’s encrypted variables. The runbook simply names them and points to where they live.
Everything in The Handover Folder is built around that one line. You get a calm home for the knowledge that makes a system followable, and a habit that keeps the sensitive parts exactly where they belong. A runbook is safe to share, copy, and read at 2am precisely because it carries no keys.
Still wondering? See the full FAQ →
No. The Handover Folder is a system plus a set of files you own — delivered as plain Markdown, a Notion template, and an Obsidian vault. There is nothing to log into and nothing to subscribe to. Use the tool your team already lives in.
Because a wiki is a place, not a method. The Handover Folder gives you the missing structure — what a runbook should contain and in what order — and drops straight into the wiki, Notion, or repo you already have.
Yes. The method is tool- and stack-agnostic. A runbook is just well-organized knowledge, so it fits cloud, on-prem, Kubernetes, a pile of cron jobs, or all of the above at once.
Never. The site is static and asks for nothing. Your runbooks live in your own files. And by design this is a runbook, not a secrets vault — keep credentials in a real secrets store and reference them by name.
No — and that is the point. Giant packs become shelfware the day you download them. This is a small, calm method you maintain, seeded with the exact templates worth keeping.
Every paid product has a 30-day, no-questions guarantee. If it does not earn its place in your team’s workflow, email us and we will refund you.
No spam, no daily firehose. Just the occasional genuinely useful note on runbooks, on-call, and spreading knowledge — and first word when we add new templates.
No spam, unsubscribe anytime. We never ask for your credentials or your runbooks. See our privacy policy.
Just want the free start? Get it instantly — no email required →