
Orchestrate 8 AI dev roles via local CLI for auditable, production-grade apps.
By Tanmay Verma, Founder · Last verified 06 Jul 2026
In short
umadev — Orchestrate 8 AI dev roles via local CLI for auditable, production-grade apps. Best for Solo developers wanting a full AI development team without managing multiple agents, Small teams needing consistent governance and audit trails for code generation, Developers already using Claude Code or Codex CLI who want structured workflows. Free to use.
See what real users actually say. We scan live discussions, reviews and complaints across the web and hand you an honest verdict — in under a minute.
3 free scans · no card needed · downloadable report
UmaDev is a standout open-source AI coding agent that prioritizes quality, auditability, and engineering discipline. Its unique role-based architecture, 112 governance rules, and 90% quality gate make it ideal for developers who need production-ready, compliant code. The free MIT license is exceptional for solo devs, but the lack of cloud hosting and multi-user features narrows its audience to those comfortable with local CLIs. If you already use Claude Code or Codex CLI and value structured workflows, UmaDev is a strong alternative to Bolt or Lovable.
Skip umadev if Skip UmaDev if you want a fully autonomous agent with no human review gates, or if you need a cloud-hosted solution with multi-user collaboration.
Compare with: umadev vs Draftbit, umadev vs Cognition AI, umadev vs Marvin
Last verified: July 2026
Across the latest 5 updates: 1 feature update and 4 changelog entries.
Added typed Seat Cards for each role, bidirectional handoff validation, two-layer artifact materialization, verdict structured tracing, and artifact versioning with DAG staleness detection.
Fixed mac flash screen, self-learning pitfall counter stuck, long transcript scroll anchor drift, duplicate diffs, and flaky CI. Enabled mouse selection to clipboard copy.
Fixed backend log screen takeover, Windows long-run display drift, /stop-preview not stopping. Guard mode now blocks and waits for approval.
Fixed deliberate build returning TODO templates as PRD/architecture. Review now actually validates. Memory corruption fix.
Fixed flicker, context table over 100%, session continuity in streaming. Preview routes to real project framework. Deep directory scan depth 8→16. Self-tuning search by usefulness feedback.
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
6 mentions across 2 sources (YouTube, GitHub).
How likely is umadev to still be operational in 12 months? Based on 4 signals — momentum (how recently it shipped), wrapper dependency, revenue model, and web presence.
Last calculated: July 2026
How we score →UmaDev is an open-source, MIT-licensed Rust binary that turns a single requirement into a production-grade application by orchestrating eight specialized AI roles — PM, architect, designer, frontend, backend, QA, security, and DevOps. It runs locally and reuses your existing logged-in CLI tools (Claude Code, Codex CLI, or OpenCode) as execution backends, so you don't need extra API keys or cloud infrastructure. The agent enforces 112 governance rules, a configurable quality gate (default 90%), and a 418-document knowledge base (as of v1.0.32) to maintain consistency, security, and compliance with SOC 2, ISO 27001, and EU AI Act. It features human-in-the-loop confirmation gates, parallel critic reviews in read-only forks, and produces an auditable delivery pack with a compliance scorecard. Key capabilities include role-specific orchestration with typed Seat Cards (v1.0.32), bidirectional handoff validation, memory persistence via facts.jsonl, RAG (BM25 plus optional local semantic), and a self-healing TUI. Compared to Bolt or Lovable, UmaDev's strength is its engineering discipline: it simulates a team with quality gates and compliance mapping. The free open-source model is generous, but the local-only CLI and learning curve may deter users seeking a fully autonomous or cloud-hosted solution.
UmaDev redefines AI-assisted development by simulating a real dev team with eight specialized roles, governed by a coordinator. This architecture, combined with 112 governance rules and a configurable 90% quality gate, ensures that every output is auditable and meets high standards. The tool's recent updates (v1.0.28–1.0.32) have significantly improved reliability: evidence fabrication is eliminated, review processes are no longer rubber stamps, memory corruption is fixed, and a new typed Seat Card and bidirectional handoff system enhance role separation and contract validation. The self-tuning search and per-seat knowledge routing (v1.0.26) further improve relevance and efficiency. Strengths: UmaDev excels at producing production-grade, auditable code with clear compliance mappings (SOC 2, ISO 27001, EU AI Act). The quality gate scorecard and delivery proof pack are invaluable for teams needing audit trails. The tool's ability to reuse existing CLI backends (Claude Code, Codex CLI, OpenCode) without managing API keys is a major convenience for users of those tools. The free, open-source model is a huge advantage. Weaknesses: UmaDev is a local-only CLI/TUI tool with a steep learning curve. It requires a logged-in backend with its own subscription (e.g., Claude Pro). The 9-stage pipeline is optimized for new builds from scratch, not for quick edits or small changes. Windows support is recent (v1.0.20) and may still have edge cases. Teams needing cloud hosting, multi-user collaboration, or an IDE plugin will be disappointed. Best fit: Solo developers and small teams already using Claude Code or Codex CLI who want structured workflows, quality gates, and audit trails. It's particularly suited for building production apps where compliance and consistency matter.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Concrete scenarios for the personas umadev actually fits — and what changes day-one when you adopt it.
You have a rough idea for a course booking app. You run `umadev init` in an empty directory, then type your requirement. UmaDev clarifies requirements, generates PRD, architecture, UI/UX docs, implements frontend (with preview), backend, runs quality gate (default 90%), and produces a proof pack.
Outcome: You get a production-grade app with tests, a 90%+ quality scorecard, and an auditable delivery ZIP — all from a single prompt, using your existing Claude Code subscription.
You want to enforce coding standards across your team. After installing UmaDev, you run `umadev ci` on your source files. The governance rules scan for hardcoded colors, emoji icons, secret leaks, and AI-slop patterns.
Outcome: CI fails on violations, preventing bad patterns from merging. Developers get clear feedback, and the team gradually adopts consistent, high-quality code.
as of 2026-07-06
as of 2026-07-06
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
The company stage and team size where umadev's pricing actually pencils out — and where peers do it cheaper.
UmaDev is completely free and open-source (MIT license). It's ideal for solo developers and small teams who already have a paid subscription to Claude Code or Codex CLI. Compared to Bolt or Lovable, which charge for cloud-hosted code generation, UmaDev offers a more disciplined, auditable workflow at zero tool cost.
How long it actually takes to get something useful out of umadev — broken out by persona, not the marketing-page minute.
Install with `npm install -g umadev` (~1 minute). Ensure one backend CLI (Claude Code, Codex CLI, or OpenCode) is installed and logged in. Run `umadev init` in your project directory. For first-time users, the initial build from scratch takes 10–20 minutes depending on complexity, but you can observe progress in the TUI.
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
Common stack mates teams adopt alongside umadev, with the specific reason each pairing earns its keep.
Used umadev? Help shape our editorial sentiment research.