Why self-host your SMS sending

The problem is not the price, it is the dependency

The cost of a cloud sending service is debatable. What is not debatable is what becomes of your business the day that service shuts down, changes its rates or suspends your account. In all three cases your sending stops, and you have no technical recourse.

Self-hosting moves the question: the binary is yours, the database is yours, the SIM cards are yours.

What sovereignty means, concretely

Three verifiable things:

• No message, no contact and no log passes through our servers. This is not a privacy policy, it is a property of the architecture: there is no network path for it.
• The telemetry the gateway sends us is limited to the licence key digest, the binary version, the machine fingerprint and the number of devices. Nothing else.
• Your data exports in full, whenever you want, without asking us.

The rule that makes the promise hold

A licence can be perpetual on paper and useless in practice, if a reachable activation server is required to start.

Our rule is explicit: a licence held for twelve months is permanently acquired. Past that threshold, our central server being unavailable has no effect on the product. No degradation, no countdown, no blocking banner.

Before that threshold, the rule still protects you: an unreachable server, whether a timeout, a name resolution failure or a server error, is never treated as an invalid licence. Only an explicit signed response can invalidate a key. And even then, sending is never cut without prior warning.

What it costs in return

You need a machine. A modest virtual private server, a desktop computer or a free-for-life cloud instance is enough: the binary is static and carries everything, including the web interface and its database.

You also have to accept responsibility for your backups. That is the price of sovereignty, and it comes down to copying one file.