For founders & operators

Your company should not depend on one person.

You hold the only logins to the registrar, the production cloud, the payment provider. Seal them in a Capsule with an emergency runbook — delivered to your co-founder or deputy only if you go silent, after reminders made sure it's really time.

End-to-end encrypted · Zero-knowledge · Weekly check-ins, 1–2 day grace

The situation

Sound familiar?

You hold the only logins to the domain registrar, the production cloud root account, and the company's payment provider. If you're unreachable for two weeks, no one can deploy, pay invoices, or stop the domain from lapsing.

What to put in a capsule
  • A Key holder with admin / root credentials and 2FA recovery codes.
  • A Text runbook: where everything lives, vendor and bank contacts, and “do this first.”
In practice

What people use it for

Domain/DNS access
Cloud/admin access
Stripe/billing/vendor
GitHub handover
Emergency runbook
Investor document locations
Operational knowledge
Key-person risk reduction
How it works

Three steps. No guesswork.

1

Map the single points of failure

Registrar, cloud root, billing, GitHub, the bank. Start with the one thing no one else could reach or understand without you.

2

Seal credentials plus the runbook

Encrypted in your browser before upload. The credentials open the doors; the runbook says which door first, and who to call.

3

A short rhythm, a fast handover

A weekly check-in with a 1–2 day grace period means the company is unblocked in days, not months — and a single click keeps it sealed while you are fine.

2/3

For the most sensitive credentials, a key capsule splits the encryption key 2-of-3: you, your deputy, and Capsulene each hold one share — no single person, and no server breach, can open it alone.

FAQ

Good questions

Isn't a shared password manager enough?

A shared vault helps while everyone is around — but it means someone already has standing access to everything, today. A Capsule releases access only when it's needed: you stay the only key-holder until silence is verified.

What belongs in the runbook?

Where everything lives (registrar, cloud, billing, repos), vendor and bank contacts, and “do this first.” Write it once; the capsule delivers it together with the credentials, so your deputy is never guessing.

Can different people receive different things?

Yes. Create one capsule per domain of responsibility — infrastructure to your CTO, banking to your co-founder — each with its own recipient, check-in schedule, and grace period.

Is this a legal instrument?

No. Capsulene provides digital continuity, not legal succession — use it alongside your shareholder agreements and estate planning. It covers what those documents rarely do: actual access.

Key-person risk, retired

Reduce key-person risk before it becomes an emergency.

One capsule with the credentials and the runbook, delivered to the right person only when it must be.

More ways people use Capsulene: