Audit your docker-compose.
Compose is easy to write and easy to ship with a hole in it. Paste your docker-compose.yml and get a production audit — exposed database ports, hardcoded secrets, missing restart policies, :latest images, and more — per service, with the fix.
The holes compose makes easy
A compose file that works on your laptop and a compose file that's safe in production are not the same file. The gaps are quiet: a database with a host port mapping that's now on the public internet, a password sitting in plaintext under environment, a service with no restart policy that won't come back after a reboot, an image: postgres with no tag that pulls a different version next month. None of them error; all of them bite later.
This catches common patterns in the submitted file. Ongoing enforcement requires explicit coverage and verification for each managed service, release, and host; a control plane does not make a one-time audit universally persistent.
Catch it once here. Keep it caught everywhere.
For configured managed services, Infraveil can report process and health evidence and apply bounded restart or recovery policy. It does not guarantee that a one-time Compose fix persists, cover every container or host, or produce a complete tamper-proof record.
See how it works