About
How we actually work.
We've documented our operating discipline in public, the architecture, the tools, the security baseline, the email setup, and how we onboard a new client. Same playbook for every engagement, because consistency is what reliability is made of.
Operating discipline
Documented in public. The same playbook applies to every client. If we can publish how we operate, we can be held to it.
- 01
The architecture
The same shape for every client, one dedicated server, a single proxy, isolated apps. Predictable on day one, predictable on day eight hundred.
- 02
The stack
Linux, Docker, Kamal, Kamal Proxy. A toolchain chosen because it's small enough to fit in one head and stable enough to leave alone for weeks.
- 03
Security baseline
Public SSH is closed. Admin access is via Tailscale. Every server is hardened to the same documented baseline, on day one.
- 04
How we handle email
Two different products solve two different email problems. Fastmail for humans reading email. Outsend for servers sending email. Both, configured together.
- 05
How we deploy a client
One command. About thirty minutes. A new client server stands up, hardened, monitored, backed up, ready for users.
Get in touch
Want the same operational discipline applied to your business?
Tell us where you are now. We'll come back with a concrete plan using exactly the architecture, stack, and process you've just read about.
What to expect
- 01We read every inquiry within one business day.
- 02A candid reply with follow-ups, no boilerplate.
- 03If there's a fit, we scope the work on a short call.