Find the weak points before production does
We work with engineering teams in Switzerland and Germany on pipelines, hardening, databases and cloud infrastructure.
$ sudo bash audit.shFAIL NET-01 postgres listens on 0.0.0.0:5432PASS NET-02 ufw active, incoming denied by defaultFAIL NET-03 Docker publishes 5432 past ufwFAIL NET-04 Dokploy dashboard listens on 0.0.0.0:3000FAIL SSH-01 password login is onPASS SSH-02 PermitRootLogin prohibit-passwordWARN SSH-03 neither fail2ban nor crowdsec activePASS UPD-01 unattended-upgrades enabledWARN UPD-02 6 security updates pendingWARN BAK-01 no offsite backup job found4 FAIL · 3 WARN · 3 PASS · cloud firewall not visible
- build48 sOK
- tests2 m 10 sOK
- secrets scan6 sOK
- image scanFAILED2 critical findings
- signHELD
- deployHELD
Release stopped at image scan. Nothing reached production.
Fourteen nightly backups
Latest one restored in a drill, Sunday 03:00
- Restored
- 14.2 GB to a scratch host
- Restore time
- 6 min 12 s
- Check
- Row counts match on 412 tables OK
$ terraform planPlan: 3 to add, 1 to change, 0 to destroy.Policy check storage account "logs" is public FAIL 14 other policies PASSApply blocked until the failure is fixed.
- First call
- Free, no commitment
- After the call
- A written proposal: scope, steps, price
- Price
- Agreed in writing before work starts
Services
Four services, each with its own page
Pick the one closest to your problem. Each page says what you get and how the work runs.
DevOps
Releases that run the same way every time: build, tests and deployment in one pipeline, without a release night.
See the service02DevSecOps
Know what your servers expose. Hardened hosts, security checks in the pipeline, secrets out of the repository.
See the service03Databases
Slow queries found and fixed, backups restored in a drill, migrations rehearsed before the cutover.
See the service04Cloud management
Cloud infrastructure in code, with policy checks that review a change before it is applied.
See the serviceOne engagement, written up: From a monolith with deployment downtime to microservices on Kubernetes
Process
How an engagement runs
Four steps. You decide after each one whether there is a next one.
- 01
Book a call
Tell us what hurts: the release process, an audit finding, a slow database, a cloud account nobody fully understands. We ask questions and say plainly whether we can help.
- 02
Get a written proposal
Scope, steps and price in writing. You decide with the facts on the table.
- 03
Work in your systems
We work in your repositories, your pipelines and your cloud accounts, alongside your team. Our changes go through review like any other change.
- 04
Keep everything
Code, configuration and documentation stay in your repositories. Your team runs the result without us.
Tell us what is not working
A release process, an audit finding, a slow database or a cloud account that grew by itself. We tell you plainly whether we can help.
The first call is free and without commitment.