Our own product

Fortlauf: a SaaS product we build ourselves and run on our own hardware

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

Fortlauf is our product. We built it, and we run it on our own hardware.

It has been in production since July 2026. This page shows how we run it and what we have measured along the way. What Fortlauf does and who it is for is on the product’s own website.

Starting point

The same requirement kept coming up in our projects. Instead of rebuilding it project by project, we turned it into a product. Fortlauf is a multi-tenant SaaS that processes and retains tax-relevant documents for several customers. That sets the requirements for running it:

  • Customers’ data must be strictly separated.
  • Stored documents must not be changed or deleted afterwards.
  • Recovery must be proven, not just planned.
  • It runs in Germany, on hardware we know.

What we did

  • Tenant isolation in the database. PostgreSQL itself enforces the separation between customers, using row-level security. The application connects with a role that cannot bypass those rules. A bug in the application alone therefore does not expose another customer’s data.
  • Database with replicas. PostgreSQL runs on Kubernetes with CloudNativePG, with replicas and automatic failover.
  • Immutable document storage. Documents sit in S3-compatible object storage with Object Lock. A stored file can be neither overwritten nor deleted before its retention period ends, not even with administrator rights; we tested this on 29 Jul 2026.
  • Separate sign-in. The product has its own identity instance based on authentik, separate from our internal services.
  • Delivery by GitOps. Every component is versioned automatically and rolled out to a separate test cluster first, then to production. Configuration lives in the repository and is applied with Flux; secrets are encrypted with SOPS.
  • Backups at a second location. Fortlauf’s database backups are kept, encrypted, at a second location in Germany; since 5 Oct 2026 they have been encrypted before they leave our hardware.

The platform underneath (hardware, Ceph, monitoring) is described on Infrastructure: where your data lives.

What this means for your project

What we recommend on operations, tenant isolation and recovery, we have tested on our own product in production. We use the same building blocks in client projects: Kubernetes platforms, built and run and Software development and architecture.

Result

In production since July 2026.

The restore rehearsal also checked tenant isolation: after the restore, a user signed in against the restored data and saw only their own records. The application ran with the same restricted role as in production.

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

What we would do differently today

Rehearse the restore before go-live. Our first rehearsal ran about a month after launch. It found three errors in our own restore runbook that only showed up when it was actually run. A runbook that has never run is an assumption.

Encrypt backups before transfer from day one. Backups to the second location initially went out without our own encryption before transfer; since 5 Oct 2026 we encrypt them first. Today we would set it up that way from the start.

What next?

Fortlauf

Questions about the product?

What Fortlauf does and how to use it is on the product's website.

Go to fortlauf.de (leaves frybad.de)

Want something similar run for you?

Planning a SaaS or a platform with the same requirements for isolation, recovery and data location? Talk to us.

Request an intro call