Controlled delivery · No standing access · Zero-knowledge Key holders for credentials
Operational access & context
Domain & DNS
Cloud & production
Billing & payroll
Repositories
Vendors
“Do this first”
CAPSULENEContinuity layer
One Capsule per area of responsibility
Weekly check-in · short grace period · reminders
No standing access today
Verified absence
Role-based recipients
CTO — infrastructure
Co-founder — banking & billing
Operations lead — vendors
Each deputy receives only their part, only when it is needed.
Domain & DNS, Cloud & production, Billing & payroll, Repositories, Vendors, “Do this first” flow into the CAPSULENE continuity layer, where one capsule per area of responsibility and weekly check-in · short grace period · reminders are defined and no standing access today. Verified absence: cto — infrastructure; co-founder — banking & billing; operations lead — vendors. Each deputy receives only their part, only when it is needed.
A quick check
If you became unreachable tomorrow, could your company still:
If the answer is not an immediate yes, your company has a continuity gap.
access the domain and DNS?
keep production running?
manage billing and payroll?
reach critical vendors?
understand what to do first?
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 are unreachable for two weeks, nobody can deploy, pay invoices, or stop the domain from lapsing.
What to put in a Capsule
A Text Capsule runbook: where everything lives, vendor and bank contacts, and “do this first.”
A Key holder — zero-knowledge — for admin or root credentials and 2FA recovery codes.
A setup that works
Suggested setup
Text Capsule + Key holder
Weekly check-in · 1–3 day grace period
Deliver to your co-founder or deputy
Business continuityAccess guidanceInstruction Capsule
Registrar, cloud root, billing, repositories, the bank. Start with the one thing no one else could reach or understand without you.
2
Write the runbook, seal the credentials
The runbook — a Text Capsule — says which door to open first and who to call. Credentials go in a Key holder, encrypted in your browser before anything is uploaded.
3
A short rhythm, a fast handover
A weekly check-in with a short grace period means the company is unblocked in days, not months — and one click keeps everything sealed while you are fine.
2/3
For the most sensitive credentials, a Key holder splits the encryption key 2-of-3: you, your deputy, and CAPSULENE each hold one share. No single person can open it alone, and stored server data alone cannot decrypt it.
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 is needed: you remain the only key-holder until your absence is verified.
What belongs in the runbook?
Where everything lives (registrar, cloud, billing, repositories), 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 area 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: access and context.
Founders & Businesses
Reduce key-person risk before it becomes an emergency.
One Capsule with the runbook and the credentials, delivered to the right person only when it must be.
