Manta reviews every change on your own machine, blocks what must not land, and produces audit-ready evidence of the decision.
Three agents review each commit. On push, Manta routes the change to up to nine relevant agents. It runs on your own AI account — we never see your code, and we never bill you for tokens.
$ git push origin main Manta Pre-Push Review 12 files changed · routed to 8 of 9 agents security-sentinel CRITICAL 0 WARNING 1 compliance-guardian CRITICAL 0 WARNING 1 spec-guardian CRITICAL 0 WARNING 0 zero-trust-guardian CRITICAL 0 WARNING 0 observability-guardian CRITICAL 0 WARNING 0 test-architect CRITICAL 0 WARNING 3 perf-analyzer CRITICAL 0 WARNING 0 code-quality CRITICAL 0 WARNING 0 CONFIRMED src/api/users.ts:84 Email address written to request log · GDPR Art. 5(1)(c) Raised independently by security-sentinel and compliance-guardian. ✗ PUSH BLOCKED · 1 confirmed warning Single-agent warnings are advisory and did not block. Recorded to the enforcement trail.
The data boundary
Reviews execute locally, on your runner, with your key. What reaches the control plane is findings metadata — never a diff, never a snippet, and never the scanner's raw matches, because those lines are the credentials it just caught.
{
"severity": "CRITICAL",
"path": "src/auth/login.js",
"line": 12,
"rule": "hardcoded-credential",
"cwe": ["CWE-798"],
"verdict": "BLOCK"
}
You do not have to take our word for it. Run manta-emit.sh --dry-run and read
the exact bytes, or --explain for the redaction policy. Redaction fails shut:
if the policy cannot load, nothing is emitted at all.
The pipeline
The split is not arbitrary. Three agents run at commit — the checks where committing is itself the harm. The rest run at push, routed by what the change actually touches, so a CSS commit does not wake the migration guardian.
One script. Agents, git hooks and config land in your repo. No service to run.
Three agents read the staged diff — secrets, quality, migrations. Criticals block.
Up to nine agents, selected by what changed. A warning blocks only when two agents agree.
Metadata syncs in the background — never on the commit path — and becomes the trail.
Free edition and Enterprise
Manta's free edition is 20 agents and 21 commands, open source under Apache 2.0, and it stays that way. Enterprise is 33 and 32 — the difference is the governance layer, and eleven of those agents are served from the control plane while your subscription is active.
20 agents · 21 commands · Apache 2.0 · no account
33 agents · 32 commands · hosted enforcement record · 11 agents served under subscription
| Manta | Manta Enterprise | |
|---|---|---|
| Agents | 20 | 33 |
| Commands | 21 | 32 |
Review at git commit | 3 agents | 3 agents |
Review at git push | 3–4 agents, trigger-routed | up to 9 agents, trigger-routed |
| A warning at push | blocks | blocks only when two agents agree |
Code generation — /write, /scaffold, /ui | ✓ | ✓ |
| Research → Plan → Implement, with a GO/NO-GO gate | ✓ | ✓ |
| Security scan | OWASP + secrets | + dependency CVEs, licence conflicts, dead deps |
Spec governance — spec-guardian | — | ✓ |
| Compliance — GDPR, HIPAA, PCI-DSS, SOC 2 | — | ✓ |
| Zero-trust — IAM, mTLS, RBAC, token TTLs | — | ✓ |
| Observability checks on new endpoints | — | ✓ |
| Test-coverage enforcement | — | ✓ |
| Health scoring and trends across audits | — | ✓ |
Penetration testing — /pentest | — | on demand |
Log analysis — /log-analysis | — | ✓ |
| Hosted enforcement record and evidence bundles | — | ✓ |
| Licence | Apache 2.0, free forever | Commercial subscription |
Enterprise adds 13 agents; 11 of them are served from the control plane while a subscription is active. Counts are generated from the shipped rosters, not typed by hand.
GDPR, HIPAA, PCI-DSS and SOC 2 checks run on every push — not the week before the
audit. Active only for the frameworks your CONSTITUTION.md declares.
Health scores, trend tracking against previous reports, and risks surfaced before the architecture sets — real visibility, not last quarter's gut feeling.
OWASP Top 10 and hardcoded secrets on the commit path; zero-trust and observability
checks at push; dependency CVEs and licence conflicts with /security-scan;
penetration testing on demand with /pentest.
Architectural drift, scope violations and API contract deviations are caught before the PR is opened. The spec stays the single source of truth.
Compliance evidence
GRC platforms integrate at the cloud layer and cannot see the code layer. Manta sits exactly there, so it can evidence controls they can only ask you about.
Q3 2026 · GDPR · acme
| Art. 32 — security of processing | 1,284 commits screened |
| Art. 17 — right to erasure | 1 gap, 2 repositories |
| Change management | 4 criticals blocked at commit |
| Enforcement gaps | 7 bypasses, each with actor |
Bundles lead with their own limitations — uncovered repositories, unresolved checks, every bypass, and every verdict replayed from an earlier identical review rather than freshly run — because a document that overstates coverage is worse than none.
A gate nobody can override is a gate people route around. Overrides are allowed and recorded — who, when, which finding, and why.
A periodic summary to Slack or any JSON endpoint. Coverage, blocks and bypasses as totals — never a leaderboard of your engineers.
The review that runs on a laptop runs on a pull request, so a machine without Manta installed cannot quietly skip it.
Built for
manta-emit.sh --dry-run.Get in touch
Tell us a little about your situation and we will get back to you within one business day. No sales pitch — a direct conversation about whether Manta fits.
Prefer email? ray@mantacron.com