Server Account Handover — When You Go Down, Who Reboots the Server?
TimeWill Editorial · Updated 2026-06-19
When a solo developer or site owner passes away, the server doesn't die on its own — it keeps running until the bill goes unpaid. Your clients, users, and projects all depend on these servers. The 'bus factor' measures whether your project survives without you. There's one way to raise it: encrypt the login details for every server, database, domain, and API key, and name a technical executor.
Servers, databases, domains, API keys — these are the core assets of a solo developer or site owner. But your family, your clients, and your colleagues can't take over after something happens to you, because they don't have the logins. A handover document isn't written for you; it's written for the people who'll have to keep your projects running without you.
A Handover Document Template
Open with 'If you're reading this, I'm no longer here.' Then list: every server IP and provider, the SSH login method and key location, the database connection details and passwords, the list of domains and registrar information, and the API key inventory. Once it's done, encrypt it in TimeWill and tell your executor how to retrieve it.
FAQ
Q: How do I raise my bus factor from 0 to 1?
Write a project handover document. It should cover: the server provider, account, and where the SSH keys are stored; the database type, connection method, and password; the domain registrar, account, and transfer codes; a list of critical API keys; and the local code paths. Encrypt this document in TimeWill and name a technical friend as your executor.
Q: What about my clients' projects?
Freelancers owe it to their clients: if something happens to you, your clients suffer most — no one maintains their product. Add a 'digital legacy clause' to every client contract listing a technical colleague to contact in an emergency, and how the project code and credentials are held.
Q: How do I hand over an SSH private key?
You can't just email an SSH private key. Store it encrypted in TimeWill's password vault, released automatically on a heartbeat trigger. At the same time, generate a separate backup SSH keypair just for your executor and add that backup public key to every server you run, so the access is already provisioned — your executor doesn't have to wait until something happens to set it up (the private key is handed over only if it actually does).