Our own product
Fortlauf: running a SaaS on our own infrastructure
Fortlauf is our product. We built it, and we run it on our own hardware. In production since July 2026: tenant isolation in the database, immutable document storage, delivery by GitOps, measured recovery.
- Industry
- Software, own product
- Period
- in production since July 2026 · as of October 2026
- Frybad's role
- architecture, development and operations
- Stack
- Kubernetes, PostgreSQL with CloudNativePG, Ceph, S3-compatible object storage, Flux, SOPS/age, authentik, SvelteKit, TypeScript, GitLab CI
Restore rehearsal on 30 Aug 2026: we restored both of Fortlauf's production databases (product data and sign-in) to coordinated points in time, in a separate test environment. Both were back in service 3 min 22 s after the restore configuration was applied; a repeat run the same day took about 3 min 30 s. Not included: the time to decide and prepare, and files kept outside the databases.
Measured
Planned database failover on 4 Oct 2026: we switched Fortlauf's product database to another replica while the service was running. The database cluster was fully back in service 19 s after the switch; writes paused for about 8 to 9 s, and no external request received a server error in that time. Not included: an unplanned outage.
Measured