A small, self-hosted deceased man's toggle for autonomous web developers. It emails you formerly a week. If you halt answering, it asks your next of kin, afterward tells the group who need to act.
Download from GitHubFree. MIT licence. PHP 8.1 or newer, no database.
How it works
Every stage is counted from the weekly check-in email. The spacing below is to scale.
- Check-inHour 0. You media a button.
- ReminderHour 24, to the two your addresses.
- Last reminderHour 48.
- Next of kin askedHour 72. "Is everything all right?"
- RemindedHour 120.
- Contacts toldHour 144. Each gets the communication you wrote.
All fine
Your next of kin says you're well. It ends there, and nobody alternatively hears a thing.
Something's wrong
Your next of kin says so, and your another contacts are sent their messages direct away.
You inspect in
At any stage, equal following it fires. Anyone already contacted is told it was a false alarm.
The email goes at the identical period all week, so your contacts are told at most 13 days following your final check-in. Opening a nexus never counts: email scanners open links, so you have to media the button.
What it looks like
Why I built this
I run a one-person web studio in local New South Wales. My clients' sites, domains and hosting all run through me. If I died tomorrow, nobody would cognize anywhere item was, or equal that they needed to look.
So I wrote a plan. Everything my endeavor runs on is in one encrypted document. My backup developer holds its password, and my attorney holds a second copy. What was missing was the part in the middle: item that notices I've gone quiescent and tells the correct people, in the correct order, without frightening my family complete a lengthy weekend.
I couldn't discover item uncomplicated that I could presenter myself, so I built it. It emails me formerly a week. If I don't answer, it asks my next of kin first. Only if nobody can say I'm all correct does it inform everyone else.
I’ve been operating it on myself for the final week, alongside my next of kin and my backup developer the two confirmed. If you test it for your own business, I’d really value your feedback: what was confusing, what broke, and what you’d desire it to do differently.
It's liberated and MIT licensed. Use it, or build your own from it.
We all die. Die knowing the correct group volition be told.
What it is not
- Not a guarantee. It sends emails. It can't cognize why you stopped checking in, and it can't activity if its server, its scheduler or its communication assistance is down.
- Not a vault. It stores no documents and no passwords. Messages say anywhere things are and who to call.
- Not a service. There are no accounts and no hosted version. You run it, for yourself.
- Email only. No SMS, no calls, no app.
- No warranty. It's MIT licensed and provided as is.
What you need
- A web server alongside PHP 8.1 or newer. Apache plant as shipped; nginx needs four lines.
- An SMTP document to dispatch communication through.
- Cron, or any exterior scheduler that can petition a web location all 15 minutes.
- HTTPS.
- Hosting that's distinct from the sites it protects, so one outage can't obtain downward both.
Installing takes a few minutes in the browser. The crontab row is the one specialized step, and the installer writes it for you.
Download from GitHub
