No credentials, on purpose
Your client does not need your logins to move to another agency. They need to know what their site runs on and who to ring. That is what the document is.
Businesses you build. People you love.
If something happens to you, everything important should keep running.
Torchpass writes one plain document per client — what their website runs on, what they already control, and what to do about it — and holds every one of them back until somebody who knows you says it is time.
No passwords held
A handover is knowledge, not keys. There is no vault.
Nobody sees anybody else
Each client gets theirs. None of them learn the others exist.
Easy to stop
Any one person can cancel it, at any point, for any reason.
How it works
Silence is only ever a signal to check in. People make the decision.
You check in on whatever schedule suits you. Miss one and Torchpass chases you, and only you, for as long as you set. Only after that does it ask somebody who knows you a single question — and nothing is ever released without their answer and a waiting period you can always stop.
01 Active
You checked in recently. Nothing happens and nobody is contacted.
02 Overdue
You missed one. Only you are chased. One click ends it.
03 Being confirmed
Someone who knows you is asked one question. They can say you are fine.
04 About to release
A final waiting period. You can still cancel it outright.
05 Released
Each client opens the document about their own website.
Security
There is nothing in here worth stealing, by design.
Torchpass never asks for a client password, so there is no vault to breach and no support override to abuse. What it holds is a description of how a website is put together — exactly what the next person needs, and worth very little to anybody else.
Read the security designIsolation the code can't skip
Every table is locked to its owner by the database itself, and the application holds no key that bypasses it. One client seeing another is not a bug we are watching for — it is a thing that cannot compile.
Even if we vanish
Print the packs. Every one is a plain page built to be printed and handed to a developer, and a printed page does not need us to still be in business.
Case study
A one-person agency. Forty client websites. One point of failure.
He runs a small web agency on his own. Every client site he has ever built runs through accounts only he can reach, and for most of those clients the website is the business.
If he disappeared tomorrow, each of those forty businesses gets a document about its own website — and not one of them gets anything before then.
Read the case study“My clients never signed up to depend on one person staying alive. Torchpass is how I stop that being their problem.”
Founder, independent web agency
- Client sites depending on him
- 40+
- People who could take over today
- 0
- Warning his clients would get
- None
What your client opens
One page about their own website. Never anybody else's.
Written for somebody who has never seen the inside of a hosting account, and ordered by consequence: what loses data first, then what goes offline, then what they already own and can stop worrying about.
See what they receive
What you are asking of one person
One question. And either answer is fine.
They hold no passwords, no client list and no files, and there is nothing to sign up to. If you go quiet for long enough this asks them once — and saying you are fine takes one tap and needs no explanation.
What you are actually asking of them
Pricing
Prepaid for years, so it can't lapse when it matters.
Never a monthly card charge that dies with its owner. Torchpass is paid annually or years in advance, so your plan stays protected through the exact moment it's needed.
See plansQuestions
Do my clients get access to anything now?
No. Their link works from the day you create it and shows them nothing at all until a release genuinely happens. There is nothing for them to log into, poke at or break while you are still the one responsible for it.
Could it release by mistake while I'm just offline?
Silence alone never releases anything. It takes a missed check-in, a grace period where only you are chased, somebody you named actively confirming, and a final waiting period. Any one of those people can stop it with one click, and so can you.
What about a coma, not death?
The person you named is asked whether you are still able to work, not whether you have died. If you are in hospital and coming back, they say so and the whole thing resets. They are never asked for evidence or a judgement call.
Do you store my clients' passwords?
No, and there is nowhere to put one. Moving to a new agency does not need your logins — it needs somebody to know what the site is built on and who to ask. That is what the document contains.
Fifteen minutes now.
Clarity forever.
Your first client takes about as long as writing the email you would have sent them anyway.
Create your plan