Gates that don’t drift
TDD, acceptance criteria, and review threads are enforced as CI checks and agent FAIL conditions — not polite suggestions in a prompt. Prompts drift. Gates don’t.
Otta is an opinionated, self-hostable AI dev pipeline. Every change is test-driven, visually verified, and gated on acceptance criteria before it merges — with a memory layer your agents actually keep.
Proven shipping a real production SaaS — last 90 days
Otta doesn’t bet quality on a clever prompt or a bigger model. The rules that keep code correct — a failing test first, a screenshot of every state, acceptance criteria that map to a real check — are wired into the pipeline as gates that can’t be skipped, no matter which agent or model does the work.
The pipeline
Six stages, each with a gate that can’t be skipped. Most tools show you an agent that writes code — this shows you what fires at every step to make sure that code is correct.
Plain-language intent becomes a fully-specified issue.
Say what you want. The system writes a Linear issue with a GIVEN/WHEN/THEN acceptance block, estimate, priority, and milestone — no ticket-grooming ceremony.
One agent, one git worktree, zero collisions.
Every issue builds in its own worktree on its own dev slot. Many issues run in parallel without stepping on each other.
The failing test is written before the code.
The builder writes the smallest red test, makes it green, then typechecks and opens a PR. Typecheck is not test coverage — and the pipeline knows the difference.
Runs the tests, opens the browser, checks the criteria.
The reviewer re-runs the focused tests, browser-verifies the happy path plus loading / empty / error states, and rejects any PR whose acceptance boxes lack real evidence.
Serialized merge, verified live before the next one.
Merges hit main one at a time. The deploy waits until the live health endpoint reports the exact merged commit before anything else moves.
Merge → semver tag → GitHub Release → release ledger.
The next version is computed from commit prefixes, tagged, and turned into a GitHub Release and a Linear release entry automatically.
Why it’s different
TDD, acceptance criteria, and review threads are enforced as CI checks and agent FAIL conditions — not polite suggestions in a prompt. Prompts drift. Gates don’t.
User-facing work isn’t done until a real screenshot of the happy, loading, empty, and error states has been checked. A DOM measurement is not a picture.
A git-canonical brain plus a cross-agent semantic recall bus means your agents remember decisions, gotchas, and dead-ends — across sessions and across tools.
Built on Jean (Apache-2.0). Your repos, your infra, your data — by default, on every tier. Data control isn’t an enterprise upsell.
Many issues build at once in isolated worktrees; they land on main one verified merge at a time. Speed where it’s safe, discipline where it counts.
This pipeline ships a real production SaaS every day. The metrics on this page are its own 90-day delivery record — not a demo.
Memory
Most coding agents start every task from a blank slate and re-make the same mistakes. Here, hard-won context is captured, versioned, and recalled — so the system gets sharper the longer it works on your code.
Canonical, exact-text project knowledge
Decisions, gotchas, and standing rules live in a version-controlled git repo. One hop to current truth, one hop to the reasoning behind it.
Cross-agent semantic memory
A self-hosted vector memory lets any agent — in any session, on any backend — recall what another already learned. Fuzzy search over hard-won context.
High-signal by design
The default is to write nothing. Only durable signal is captured — decisions, fixes, failed approaches — so recall stays sharp instead of drowning in transcripts.
Head to head
Generic agent platforms optimize for raw autonomy at enterprise scale. Otta optimizes for provable quality, persistent memory, and data you control.
Comparison reflects publicly documented positioning and independent reviews of enterprise agent platforms; capabilities change over time.
Pricing Plans
The local-first AI dev cockpit for solo builders.
Join waitlistThe complete AI-native dev workflow for individuals.
Join waitlistEverything in Free, and:
Expanded limits and cloud runners for power users.
Join waitlistEverything in Plus, and:
For growing teams that need tailored plans.
Book a callBe first to run agents that test-drive, visually verify, and gate every change before it merges. We're onboarding teams in waves — early access + founder pricing.
Join the waitlist for early access, or book a walkthrough to see the gates, the memory layer, and the live delivery record in action.