Your product keeps growing, but nobody's full-time job is the platform underneath it. We build Kubernetes with Ceph storage and GitOps, and either run it with you or hand it over with documentation.
We run what we recommend.
We build and run Kubernetes platforms, on your hardware or in your cloud.
Frybad, a Munich GmbH since 2021, designs, builds and runs platforms with Kubernetes, Ceph and GitOps.
Request an intro callSee all services
We also cover cloud-native DevOps & SRE (AWS, GCP, Azure), GPU servers, penetration testing and software development. We run our own hardware in a data centre in Munich. Fortlauf is our product. We built it, and we run it on our own hardware.
- GmbH since 2021, registered at the Munich Local Court (Amtsgericht München), HRB 270903
- our own hardware in a data centre in Munich
- Fortlauf: our product, in production since July 2026
Services
Leave VMware for Proxmox VE and Ceph: inventory, target design, migration sequence. We run Proxmox and Ceph ourselves, in production.
The cloud bill grows faster than the product, and releases depend on one or two people. We build pipelines, infrastructure as code and monitoring, cloud-native on AWS, GCP or Azure.
You need GPU compute, and the data has to stay in Germany. We provide GPU servers, quoted per configuration and term, as Kubernetes nodes or as virtual machines with a GPU.
A customer asks for a security test, or your device is about to ship. We test applications, cloud environments and connected devices, and report every finding with a proposed fix.
You need a new application or a rebuild, and nobody in-house is free to build it. We design the architecture, build the software and put it into operation, the same way we did with our own product.
Entry offers
Fixed-scope entry offer
Disaster Recovery Drill
Request this offerfrybad.de/en/contact/?thema=kubernetes-plattform&angebot=ernstfall-probe
Fixed-scope entry offer
VMware Exit Check
Request this offerfrybad.de/en/contact/?thema=vmware-proxmox&angebot=vmware-ausstiegs-check
Case study
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
What we run ourselves
We run our own hardware in a data centre in Munich.
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
Since 2 Oct 2026, the storage and system disks of our virtualisation hosts have been encrypted.
Period: since
What are you working on?
Tell us what runs today and what needs to change.