The stack.
What runs SuppyHQ, where it runs, and who can touch it.
Most software companies hide their stack. I'd rather show mine. If you're trusting your customer data with SuppyHQ, you should know exactly where it lives and how it's locked down.
Here it is, by layer, in plain language.
Where it runs
One dedicated server at Hetzner, in Germany. One box.
Cloudflare sits in front for DDoS protection and TLS. Public traffic hits Cloudflare first, then is forwarded to the origin over HTTPS. The origin's firewall only accepts traffic from Cloudflare's IP ranges. Anything else gets dropped at the door.
What it runs
Ruby on Rails 8. I've been writing Rails since 2010 and shipped a dozen apps in it. Nothing here is new to me.
SQLite for the database, on the same disk as the app. The data lives next to the code that reads it.
Cloudflare R2, in Western Europe, for attachments and the original emails.
Postmark sends and receives every email. I don't run that part myself. Email deliverability is a full-time job, and they do it better than I would.
OpenRouter and TypeSafe run the AI parts: summaries, suggested replies, and sorting. I don't run those either. Each one sees only what its task needs, and the privacy page lists exactly what.
Fusionaly for marketing-page analytics. I built it, I host it on the same box.
LogNorth for uptime, errors, alerts, and logs. Also mine, also self-hosted. When SuppyHQ pages me at 2 AM, the page comes from a box I run.
Chasen for deploys and backups. I built that one too.
Who can touch it
Nobody from the internet. SSH on the public side is closed.
I get in through Tailscale, a private network that connects my laptop directly to the server.
Deploys run from a second machine of mine on the same private network. A push to one branch on GitHub starts them.
The Tailscale network has exactly one human on it: me. If my laptop is stolen, the device is revoked from my phone in 30 seconds.
Backups
Chasen backs up every database to Cloudflare R2. A live copy streams there as the data changes, and a full backup goes there every hour and before each deploy, kept for 6 months. Both are encrypted at rest and in transit.
I restore both now and then, and every database comes back and passes SQLite's integrity check.
If the primary box dies, I can restore from the last backup to a fresh box in under an hour. I've practiced it.
Will this scale forever?
No, and I'm not pretending it will.
SQLite and one box are right for SuppyHQ at this size. The target is founders and small teams with up to 5,000 customers, batched email, not real-time chat. The math works.
As traffic and users grow, I'll adapt. Postgres when SQLite's writes start to hurt. A second box when one isn't enough. Each move only when the math stops adding up, not before.
I won't over-engineer for traffic I don't have. That's how solo products die: three years on infrastructure no customer notices.
When something breaks
I email the customer when the fix ships. Same close-the-loop rule as the support code.
One server. One database. One person on the keys.
If you're trusting SuppyHQ with your customer data, this is the box it sits on and the door I use to reach it.
Start free
Read next: Privacy · The support code
SuppyHQ: Every feature · Free, Solo and Teams plans