Security principles

Isolation

Every project runs in its own namespace with its own network policy. Workloads cannot reach each other, the host, or internal Progity systems.

Least privilege

Workloads run as non-root without privileged mode, without host mounts and without access to the container runtime socket. Egress is restricted.

Ephemeral build workspaces

Builds run in short-lived workspaces that are destroyed afterwards. What persists is the image, its digest, its metadata and its logs.

Secret handling

Secrets are write-only in the interface, stored separately from project data, injected at runtime, and never returned to the browser or exposed to an AI agent.

Audit trail

Every revision, build, deployment, check, review, approval and rollback is recorded with an actor and a timestamp.

Release immutability

A release is an immutable artifact addressed by digest. It cannot be edited after the fact, only superseded.

Explicit production approval

Nothing reaches production without a person approving it. An AI agent connected through MCP can prepare a release but cannot promote it.

Rollback

Any previous release can be restored without a rebuild, which keeps recovery fast and predictable.

EU operation

The platform is operated from the EU by the Progity software studio. Workloads run in the Czech Republic on proven server hosting from an established provider, VEDOS (formerly WEDOS), on infrastructure with an operating record behind it.