Config-as-Code deployment automation
We built Mantis as a simpler, self-contained alternative to legacy deployment tools: version-controlled deployments, multi-tenant access control, and remote execution over mTLS.
Why we built Mantis
We wanted a deployment server that ships as a self-contained binary and keeps its whole definition in Git.
Mantis is a modern, self-contained platform — it runs in containers or on bare metal, with no language runtime to install.
Our goal is simple: reliable execution, complete audit trails, and optional automatic rollback when a deployment fails.
Under the hood
- Self-contained service binaries — no language runtime to install
- Tenant-scoped isolation for deployment resources, and hash-chained audit trails
- Tokio async runtime with graceful shutdown
- Listen (push) and poll (pull) execution modes
What we believe
The principles that guide how we build Mantis.
Reliability First
The dispatch queue retries and reassigns work when an execution server fails, so deployments are picked up again rather than dropped — within a bounded retry and expiry window.
Security by Design
mTLS between the control plane and your agents — certificates issued from a built-in CA and tracked to expiry — plus fine-grained RBAC and hash-chained audit trails.
Source Available
The full source is published under the Business Source License 1.1 and converts to AGPLv3 on its Change Date. Read it, audit it, run it.
Developer Experience
A REST API with an OpenAPI spec, and documentation with worked examples.
Technology stack
What Mantis is built on.
Ready to try Mantis?
Deployment automation with version control, multi-tenant access control, and rollback. Self-hosted, free forever for personal, academic and nonprofit use.