Isolation
Every project runs in its own namespace with its own network policy. Workloads cannot reach each other, the host, or internal Progity systems.
Security
Shipvise runs code created by customers and AI tools. That is why the platform is built around the following security principles.
Shipvise is in public beta. The scope of these protections may vary by plan and product stage, so availability is stated directly alongside the relevant feature or plan.
Every project runs in its own namespace with its own network policy. Workloads cannot reach each other, the host, or internal Progity systems.
Workloads run as non-root without privileged mode, without host mounts and without access to the container runtime socket. Egress is restricted.
Builds run in short-lived workspaces that are destroyed afterwards. What persists is the image, its digest, its metadata and its logs.
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.
Every revision, build, deployment, check, review, approval and rollback is recorded with an actor and a timestamp.
A release is an immutable artifact addressed by digest. It cannot be edited after the fact, only superseded.
Nothing reaches production without a person approving it. An AI agent connected through MCP can prepare a release but cannot promote it.
Any previous release can be restored without a rebuild, which keeps recovery fast and predictable.
The platform is operated from the EU by the Progity software studio. Shipvise-managed environments run in the Czech Republic on infrastructure from the established provider VEDOS (formerly WEDOS). Customer-managed production can remain in the customer’s own region and infrastructure.
If you believe you have found a vulnerability in Shipvise, write to security@shipvise.com. Tell us what you did, what happened, and how we can reproduce it. We will confirm receipt and keep you informed.
Bring the project to Shipvise, verify the release on staging and move it through a controlled path to production. Keep your infrastructure or use a Shipvise-managed environment.