Config-as-Code deployment automation
We built Mantis as a faster, simpler alternative to legacy deployment tools: version-controlled deployments, multi-tenant access control, and remote execution over mTLS.
Why we built Mantis
Existing deployment tools are slow and hard to extend, built on aging technology stacks.
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 automatic rollback when something goes wrong.
Under the hood
- Self-contained service binaries — no language runtime to install
- Tenant-scoped isolation and cryptographic 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 do not stall.
Security by Design
Always-on mTLS between every component, fine-grained RBAC, and hash-chained audit trails.
Open Source Core
Our core is open source. We believe in transparency and community-driven development.
Developer Experience
A REST API with an OpenAPI spec, and documentation with worked examples.
Technology stack
What Mantis is built on.