The standard
your agents follow
while you
Install the CTO GitHub App once on your org. Every commit and pull request across every repo is judged against your ratified Engineering Standard, drift is scored with evidence, and weekly contributor-ranked reports land with concrete rule-edit recommendations — so AI-native teams keep shipping without accruing methodology debt.
Four steps. Every week.
Zero drift.
Define
Generate a canonical cto.config.md and ratify an Engineering Standard your whole org commits to. Policy-as-code, reviewed once.
Compare
9 analyzers measure every repo in your org against the standard — agent context, test coverage, ownership, dependencies, security, org, history, secrets.
Detect
Every PR and every repo scored on-track / drifting / at-risk against your ratified standard, with evidence and delta since last week.
Act
Weekly contributor-ranked reports land with concrete rule-edit recommendations, plus agent-ready artifacts — CLAUDE.md, AGENTS.md, .cursorrules — so coding agents enforce the standard where code is written.
Sits inside GitHub
as an advisory check.
Install once.
Every repo in your org, watched.
Install globally via npm
Node ≥22, npm ≥10. Hosted login uses the same account as the dashboard.
Authenticate with your workspace
Browser-based OAuth. No API keys on disk.
Bootstrap policy + run your first scan
A draft cto.config.md appears in your repo root along with a prioritized top-5 action list — install the GitHub App next to judge every PR against it.
Open the hosted dashboard
Repo appears in the fleet view. Weekly contributor-ranked reports start landing automatically.
Priced per repo.
Like a linter, not a seat tax.
One repo, GitHub App installed. Weekly contributor reports. CLI + hosted dashboard. Great for solo founders and side projects.
- 1 connected repo
- Every PR judged against your standard
- Weekly contributor-ranked reports
- Shareable report links
- Community support
For AI-native teams shipping 10+ PRs/day across their whole GitHub org. PR-level judgments, ownership enforcement, Slack digest.
- Unlimited repos, org-wide install
- PR-level standard checks
- Slack + email digests
- Board-ready PDF export
- Priority support
Cross-repo intelligence, SSO, custom analyzers, on-prem scanning, and a named solutions engineer.
- Cross-repo fleet view
- SSO / SCIM
- Custom analyzers
- On-prem scanner
- Solutions engineer
Questions engineering leads ask.
Is CTO a linter?
No. Linters enforce syntax. CTO governs methodology — the layer above individual tools that keeps the whole system coherent. Think Jira-to-Agile, not ESLint-to-code.
Does it block merges?
By default, no. CTO ships as an advisory GitHub check with pass/warn/fail signals. Teams can opt into branch protection once they trust the signal.
What languages do you support?
v0 and v1 target JavaScript and TypeScript repos specifically. Other languages are best-effort. The constraint is deliberate — we'd rather produce high-trust findings for one ecosystem than shallow breadth across many.
How is my code used?
Analysis happens in your connected workspace. We never train on customer code. Only scan metadata and generated reports are persisted.
Who owns the cto.config.md file?
Your team. It lives in your repo as a committed file. CTO reads it, suggests edits, and enforces it — but it's your source of truth.
Does this replace code review?
No. CTO flags methodology drift — stale agent context, ownership gaps, ballooning files, policy violations. Engineers still review code. CTO makes sure the standard is being followed even when no one has time to check.
Stop hoping your agents follow
your engineering standard.
Make it auditable. Install the GitHub App and generate your cto.config.md in under 5 minutes.