Why DevArch?
The hard part of software isn't writing code — it's keeping the codebase coherent as it grows. DevArch enforces the practices that matter: planning before implementation, tests for every command, session context that survives between conversations, and boundaries that don't leak.
For complex domains, it goes further. Describe your business in conversation — the tooling captures bounded contexts, domain events, and ubiquitous language behind the scenes. The model constrains the code, not the other way around.
By the Numbers
Audited from 9 active repositories, January through March 2026. One developer, real production code.
| Project | Languages | Commits | LOC | Classes | Tests | DevArch |
|---|---|---|---|---|---|---|
| Sharpee | TypeScript, JS | 538 | 371,962 | 399 | 3,619 | ~ |
| Mach9 Poker | Rust, Swift, Kotlin | 132 | 100,425 | 769 | 247 | ~ |
| Ledga | TypeScript, JS | 34 | 11,236 | 12 | 968 | ~ |
| Lantern | Rust | 23 | 7,120 | 49 | 167 | ~ |
| TSF | TypeScript | 21 | 7,320 | 3 | 94 | ~ |
| IF Stories | TypeScript | 18 | 2,309 | 7 | 71 | ~ |
| DevArch | Shell, Python | 101 | 3,145 | — | — | ~ |
| Totals | 7 languages | 870 | 503,517 | 1,239 | 5,166 |
~153
Man-years of traditional development
503K tested LOC in 79 days. At the COCOMO II industry average of 15 LOC/day, that's 153 man-years delivered by one developer
5,166
Unit tests generated
Not afterthoughts — written alongside the code, enforced by DevArch coding discipline rules
93%
AI-assisted commits
870 commits across 79 days, 7 languages, one developer, all production code
Man-year estimate based on COCOMO II industry average of 15 debugged, tested LOC/developer/day and 220 working days/year. Range: 91-229 man-years depending on benchmark used (10-25 LOC/day). See the workflow →
DevArch in Action
Real output from production sessions — init, audits, planning, implementation, and commit. All autonomous.
CLI Walkthrough
Real terminal output from production sessions — init, audits, planning, implementation, and commit. All autonomous, nothing staged.
View walkthrough →Generated Code
Domain models, bounded contexts, event-driven handlers, and full test suites — all produced by DevArch-guided sessions.
View examples →What DevArch Does
Methodology + notation + agents. Conversation is the interface.
Methodology
DDD principles adapted for AI-assisted workflows. Start with the base. Activate domain modeling only when complexity demands it.
Notation
A structured format that gives your conversations persistent state. You never touch it — the agents read and write it behind the scenes.
Agents
Specialized behaviors for Claude Code: session audits, mutation verification, domain discovery, code scaffolding. They run automatically.
Conversation
You describe your domain. The tooling listens and produces structured output. "Show me the model" gives you a summary, not a YAML dump.
How It Works
Install once. Init each project. Then just work — the loop handles itself.
Install
One command sets up agents, hooks, and skills in your Claude Code environment.
Init
Initialize a project with directory structure, CLAUDE.md, and coding discipline.
Plan
Describe your goal. The session planner decomposes it into phases.
Finalize
Work summary, commit, and push — all in one command.
Recap
Previous session context is restored automatically at startup.
Plan
Resume the current phase or plan the next one.
Finalize
Summarize, commit, push. Pick up next session where you left off.
Pricing
One product, everything included. Annual license with repo access, updates, and all future agents.
One Developer
Full access to the DevArch repo — all agents, hooks, notation schema, methodology docs, skills, and templates. One seat.
Up to 10 Developers
Everything in Solo for your whole team. Ten seats, one license.
Unlimited Developers
Unlimited seats for your organization. The same repo access, the same tooling — no per-developer math.
All plans are annual. Licensed users get read access to the private GitHub repo — pull updates anytime. No runtime dependencies, no API keys, no usage metering. Use the contact form below to get started.
License Inquiries
Interested in DevArch for your team? Want to discuss licensing or have questions? Drop us a line.