About
The playbook.
These pages are the notes our crew works from: how we build, the tools we trust, the security basics, how email gets set up and what happens on launch day. Every project follows the same playbook, so nothing depends on memory or luck.
How we operate
Written down for anyone to read. Every project follows the same playbook. Publishing it keeps us honest and gives you a yardstick.
- 01
How we build
Every project gets the same layout, one dedicated server, one front door, apps kept apart. You know what you're getting in week one, and it still looks the same in year three.
- 02
The toolkit
Linux, Docker, Kamal and Kamal Proxy. A short list of tools, small enough to learn properly and steady enough that we rarely have to think about them.
- 03
Security basics
No public SSH. Admin access over Tailscale only. Every server gets the same written-down hardening on the day it's created.
- 04
Email, done properly
People reading mail and apps sending mail are two separate jobs. Fastmail handles the first. Beacon handles the second. We set both up so they work together.
- 05
Launch day
One command and about half an hour. A new server comes up hardened, monitored and backed up, ready for real users.
Say hello
Want this playbook working on your next project?
Tell us what you're building and where it stands today. We'll reply with a scoped first step, using the same process and toolkit described on these pages.
How it starts
- 01A real person reads your note before the next working day ends.
- 02You get straight answers and a few sharp questions back.
- 03If we can help, we map out a first release on a 30-minute call.