For engineering leads and IT managers

Find the weak points before production does

We work with engineering teams in Switzerland and Germany on pipelines, hardening, databases and cloud infrastructure.

audit.shExample output
$ 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
Pipeline runExample output
  1. build48 sOK
  2. tests2 m 10 sOK
  3. secrets scan6 sOK
  4. image scanFAILED2 critical findings
  5. signHELD
  6. deployHELD

Release stopped at image scan. Nothing reached production.

Restore drillExample output

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 planExample output
$ 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

Process

How an engagement runs

Four steps. You decide after each one whether there is a next one.

  1. 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.

  2. 02

    Get a written proposal

    Scope, steps and price in writing. You decide with the facts on the table.

  3. 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.

  4. 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.