If I Get Hit by a Bus

I'm one person. One person can get hit by a bus. I host your CRM — so I owe you a straight answer about what happens to your shop if I'm not here. Here's the actual plan: four layers, roughly in the order of how quickly each one kicks in. Any one alone is meaningful. All four together, your shop doesn't stop because I did.

1. Anytime export, from inside the CRM

   An Import / Export page in your settings — same place you imported your starting data — lets you download your full database any moment you want it. Two formats: a .sql file (a plain-text SQL dump of your whole database — restorable into any Postgres install, or readable as text in any editor) and a .csv bundle (every table, zipped). Both are open formats. Any developer can read them. You're never holding a file you can only open with my software. This is the layer that matters most, and it's the one that works instantly, with no cooperation from anybody — including me.

2. Monthly export, automatically emailed to you

   Once a month, an email lands in your inbox with secure links to your latest .sql + .csv bundle. One click and the file is yours — save it wherever you keep your other business records. Links rotate every 7 days, and Layer 1 above means you can grab a fresh copy any time you want one. The monthly email is the nudge; you holding the file is the point. If I vanished tomorrow and you did nothing else, you'd still have a recent, complete, open-format copy of your entire business sitting in your inbox.

3. Your instance stands alone, and it's backed up nightly

   Your CRM is a single-tenant deployment — your own database, your own application, your own backups, behind your own domain. Nothing about it is entangled with another customer's shop, so nothing has to be untangled in a hurry. Backups run nightly, encrypted, with off-site retention and restores verified on a regular cadence. Whoever picks this up after me inherits one self-contained instance and a working restore — not a slice of somebody else's platform.

4. A weekly check-in, so you're never the last to know

   I host the code rather than shipping it to you, so you deserve to know promptly if I stop. Your CRM checks a public heartbeat once a week — a timestamp I refresh every time I push code. If it goes stale past the threshold, your CRM emails you automatically, with a recovery guide and a path forward. You don't have to be the one who notices, and you're not relying on anyone's goodwill to find out: your own system tells you. And by the time that email arrives, Layers 1 through 3 have already put a complete, current, open-format copy of your business in your hands — so the news is inconvenient, not existential.

And underneath all four, the exit you can take on a good day, not just a bad one: the buy-out. If you ever want the code itself, you can purchase the source outright and be fully independent — not as an emergency measure, but whenever you decide you want it. Most owners never do, because Layers 1 and 2 already give them the thing they actually wanted: their data, in their hands, in a format anyone can read. But the door is there, and it opens on your schedule rather than mine.

I'd rather over-build for this and never need it than wave my hands at it. The pitch of Fieldamigo is that your shop is yours — your instance, your data, your workflows. That has to hold in the worst case too, or it's just a longer leash on the same collar.

"If I get hit by a bus tomorrow, your shop runs Wednesday."

Status: All four layers are live. This page updates as anything material changes.