What "your data, your server" actually means

Every software company says something warm about "your data". Here is what the phrase means concretely when a tool is self-hosted — and, just as important, what new responsibilities it hands you. No mysticism, no legal theater: just where the bytes are and who can touch them.

Where your records physically live

When you run a tool from this store, every record it keeps — clients, invoices, bookings, waivers, compliance logs — is a row in one database on a server you chose: your shared-hosting account's MySQL database, or a single SQLite file in the app's data folder. There is no second copy on our servers, because the software does not talk to our servers. Nothing phones home; there is no license check-in that could see your data, and no analytics beacon riding along.

With SaaS, the same records live in the vendor's cloud, under the vendor's account system, subject to the vendor's retention rules, breach surface, and business continuity. That is not automatically bad — it is simply a different owner of the filing cabinet.

No third-party processor for core records

If you operate under GDPR or similar rules, every company that touches personal data on your behalf is a processor you must account for. A self-hosted tool shortens that list: your hosting provider is on it, and the vendor of the software is not, because the vendor never receives the data.

One honest exception, clearly marked: our AI document tools send the documents you choose to process to the one model provider you configure — OpenAI, Anthropic, or a local Ollama model on your own machine — using your own API key. That traffic goes directly from your server to your chosen provider. Choose Ollama and even that leaves nothing.

Exports: leaving must always be cheap

Data you cannot take out is data you do not own. The tools here treat export as a standing feature, not a support ticket: records export to CSV and JSON from the admin screens — and because the database itself is yours, the ultimate export is the database. Any developer can read it; the schema is plain tables with sensible names, and the full unobfuscated source code documents every one of them.

Compare that with the exit path from a typical SaaS: request an export, get what the vendor decided to include, in the format the vendor decided to write, on the timeline the vendor decided to offer.

Backups: the responsibility you inherit

Here is the honest half of the bargain. On SaaS, backups are the vendor's problem. Self-hosted, they are yours:

• What to back up: one database plus one data folder (uploads and files). That is the complete state of the application.
• How: your hosting panel's backup button, a nightly `mysqldump`, or simply copying the SQLite file. Any of these is a real, restorable backup.
• When: on a schedule you set. Weekly is a sane floor for a small business; before every update is a sane habit.
• Prove it once. A backup you have never restored is a hope, not a backup. Restore one copy into a scratch database a single time and you will trust the routine forever after.

The same applies to updates — new versions are yours to apply, on your schedule (upload the new files; the database migrates itself in place) — and to server hygiene: HTTPS and a supported PHP version are your host's checkboxes, but you have to tick them.

Continuity: the quiet, underrated benefit

A subscription tool can be discontinued, acquired, repriced, or feature-gated while your data sits inside it. A self-hosted tool you have already purchased keeps running regardless of what happens to the vendor — including us. You hold the complete source; it depends on no external service; your data is in an open database beside it. The worst case for a vanished vendor is software that keeps working exactly as it did yesterday, forever.

That is what "your data, your server" means here: shorter processor lists, exports that are trivially cheap, continuity that does not depend on anyone's runway — paid for with backup and update duties that are small, but real, and yours. Neither model is morally superior; they allocate the same responsibilities to different people. The difference is that self-hosting lets you decide who holds each one, and prices the whole arrangement once instead of monthly. If that trade reads well to you, the self-hosting walkthrough shows how little the setup involves, and every product page here — Invora to Rentara — lists its honest limitations before you spend a cent.