Ensure and prove your software follows the rules.
Toevan governs your repository's entire state.
Pull requests are blocked as a GitHub check when they break your compliance, security, or architecture rules; main is re-evaluated against the same versioned constraints on every change; and every decision writes signed, auditor-ready evidence pinned to the exact commit, with verdict attestations delivered to your connected integrations.
Built for regulated engineering teams shipping AI-assisted code.
- Signed SLSA attestations
- GDPR compliant
- EU servers
Why now
AI ships code faster. It breaks the rules more often.
AI assistants write clean, locally correct diffs at a pace no review process was designed for. Each one can still put business logic in a controller, hardcode a credential, route cardholder data into a logger, or skip the control your next audit depends on. The diff looks fine. The system drifts.
Rules files ask the model to behave. Toevan verifies it did.
A CLAUDE.md or .cursorrules file is a request. A merge gate is a guarantee. Toevan is that guarantee for your whole repo: PRs blocked at the gate, main re-evaluated on every change, signed evidence your auditor can verify. You can't audit a nudge.
What shifts when assistants write the code
Source: Apiiro, Faster Code, Greater Risks (Fortune 50 codebase research, Dec 2024 to Jun 2025)
Exposed PII and cardholder data is regulatory penalty surface: GDPR fines reach 4% of global annual turnover or 20 million euros, and PCI DSS non-compliance runs up to $100,000 a month.
It isn't one study. Apiiro watched monthly security findings rise tenfold in six months, GitClear measured code duplication up 81% across 623 million changed lines since 2023, and Gartner now recommends architecture-first validation for AI-generated code.
What the gate enforces
One gate. Three domains of governance.
Seventeen deterministic constraint types, adopted as versioned blueprints, all writing to the same evidence trail.
Compliance & data
6 frameworks mappedPII, PHI, and PAN flow rules, deletion and breach-notification requirements, time-limited exceptions, and every verdict mapped to SOC 2, ISO 27001, PCI-DSS, HIPAA, GDPR, FedRAMP, and DORA controls.
Security & supply chain
7 constraint typesHardcoded secrets across 52 patterns, known CVEs via OSV.dev, license compliance, unencrypted storage, and Terraform, CloudFormation, and Kubernetes misconfigurations.
Architecture & structure
10 constraint typesLayer boundaries, dependency direction, circular dependencies, forbidden imports, naming conventions, and complexity budgets. The rules that keep a codebase changeable stop being suggestions.
How it works
From connect to gated in one afternoon.
Connect a repository
Install the GitHub App. Toevan indexes your codebase into a dependency graph with tree-sitter parsing and LSP semantic resolution. Deterministic analysis, no AI involved, and your code stays inside your boundary.
Adopt blueprints
Blueprint DNA extraction detects the architecture already living in your code and proposes it back as enforceable rules. Review, tune, adopt. Or start from marketplace packages like Security Essentials, PCI-DSS v4.0, SOC 2, ISO 27001, HIPAA, GDPR Baseline, FedRAMP, DORA, and Clean Architecture.
Gate every pull request
Each PR is evaluated against your adopted blueprints. Same input, same verdict, every time. Violations block merge with the exact file and line, and every decision writes an evidence record.
The product
Define. Enforce. Fix. Prove.
Your rules, live
The canvas renders your real dependency graph: layer structure, imports, sensitive data flow, and what a PR changes before it merges. Click a node to see its blueprints, violations, and source. Architecture docs nobody reads become a map everybody uses.
- Layer, dependency, data-flow, and PR-diff views
- PII, PHI, and PAN tags propagate through the graph
- What-If simulation previews a change's impact before you make it
Violations are blocked, not suggested
Toevan runs as a GitHub check on every pull request. Architecture boundaries, security rules, and compliance controls evaluate deterministically against the symbol graph, and violations annotate the exact file and line. A hardcoded secret blocks the merge exactly like a layering breach or a missing control: a blocked PR tells you why, and what it would take to pass.
- Deterministic verdicts: same input, same output
- Exact file and line annotations on the PR
- Time-limited exceptions with review and auto-expiry
The gate ships its own fixes
Every violation arrives with an AI-generated fix: current versus suggested code and the reasoning behind it. Apply one, or fix every fixable violation in a single batch run while a live console streams each step. Blast-radius and build validation keep the agent honest.
- One-click Apply Fix, validated before it lands
- Fix all runs the whole PR as one commit
- Automatic re-check verifies the new verdict
Also in the box
Governance for the whole lifecycle
Audit-ready by construction
The evidence is the enforcement.
Every check, exception, and decision writes an immutable, SHA-pinned record at enforcement time, mapped to the controls your auditor asks about. Attestation tools record claims about controls. Toevan's record only exists because the control executed on that exact commit.
- Append-only evidence store, 3-year retention, CSV and JSON export
- Control mapping across SOC 2, ISO 27001, PCI-DSS v4.0, HIPAA, GDPR, FedRAMP, and DORA
- Auditor-ready PDF reports per framework, date range, and repository
Verify it without trusting us
One command replays every hash offline. If the chain holds, the history is intact. No trust in Toevan required.
Audit prep becomes an export, not a quarter.
Your first gated PR can land this afternoon.
Start governing your softwareAttestation
Every verdict ships as a signed attestation
Each PR gate decision ships as a supply-chain attestation: an in-toto statement with the SLSA Verification Summary predicate, sealed in a DSSE envelope and anchored to a public transparency log. Your auditor, your deploy gate, or any policy engine verifies it with open tooling. Toevan is not in the loop.
- Signed at enforcement time, never asserted afterward
- Hash-only log entries: existence is public, your code is not
- Verifies with stock cosign against a published key, in your own repo
The proof lives in your repo, not ours.
Integrations
Wired into the tools you already run
The gate lives in GitHub, and the proof travels to the systems your team and your auditors already trust. Every connection is validated live against the vendor before it is stored, and credentials are never shown again.
Pricing
Pricing is temporarily unavailable
We could not load current pricing. Rather than show figures that might be out of date, we would rather tell you. Get in touch and we will confirm them.
Talk to usFAQ
The questions engineers ask first
Which languages does the indexer support?
Go, TypeScript, JavaScript, Python, Java, Kotlin, and Dart today. The index is built with tree-sitter, so verdicts come from your real symbol graph, not from pattern matching on text.
Is the enforcement really deterministic?
Yes. Blueprint constraints evaluate against the dependency graph with no model in the loop: same input, same verdict, every run. AI is used where it helps, generating fixes and explaining violations, never for deciding whether your software complies.
Does my code leave my boundary?
Indexing runs against your repositories through the GitHub App, and Enterprise plans run fully self-hosted or in your VPC. Your code is never used for training, and AI fix generation can be pointed at your own model endpoints.
What happens when the gate is wrong?
You request an exception: justification, scope, and duration, reviewed by the right owner and auto-expiring on schedule. The exception itself becomes evidence. Gates that can't bend get turned off; this one bends on the record.
Do you only support GitHub?
GitHub today, via a GitHub App with check runs and PR annotations. GitLab and Bitbucket are on the roadmap; if one of them is your blocker, tell us and it moves up.
How long does onboarding take?
Connect a repository and the index builds in minutes. Blueprint DNA extraction proposes rules from your existing structure the same day, so the first gated PR usually lands within the first afternoon.
Is this just an architecture linter?
No. The same gate runs structural rules, security scanning, and compliance constraints, and every verdict writes audit evidence. Scanners find problems and stop there; Toevan governs the whole lifecycle: define the rules, enforce them on every PR, head branch, manage the exceptions, and prove it all to an auditor.
Does the gate slow developers down?
It replaces waiting, not adds to it. The gate runs as a GitHub check alongside your existing CI, and a violation arrives with the exact file and line plus a suggested fix, which beats a review comment saying the same thing two days later. When a rule genuinely doesn't fit, a time-limited exception keeps the work moving, on the record.
Does a green report mean full compliance?
No, and every blueprint says so explicitly. Toevan enforces and evidences the code-visible subset of each framework: for DORA, the technical pillars (asset identification, protection and prevention, detection) and component-level third-party risk, per commit. Organisational obligations (incident-reporting clocks, resilience testing, registers, governance) stay with your process, and each blueprint documents exactly which controls it does not check, so a green report is never mistaken for the whole regulation.
Design partner program
Not paranoid. Early.
We're onboarding a small group of design partners for H2 2026: regulated engineering teams shipping AI-assisted code, from Series B to enterprise. Bring one repository and an upcoming audit; the first audit cycle is the proof.