Free during public beta. Paid tiers when they earn it.
The open framework is self-serve — create a free account and install in minutes, no approval step. Proprietary tooling (trw-distill, trw-loop, trw-swarm) ships through the curated alpha/beta tester program. Rolling out across a team? Talk to us.
Free
Everything you need to run the workflow in a real repo. No approval step, no card.
Prefer to read first? Browse the docs.
- Full workflow — requirements, execution, review, and delivery inside your repo.
- Memory that compounds: learnings, checkpoints, and session-start recall.
- 45 MCP tools and 26 bundled skills for repeatable workflows instead of ad hoc prompting.
- Verification gates for tests, type checks, and review before delivery.
- Source-available under BSL-1.1. Free during public beta.
Tester program
Early access to the proprietary tools (trw-distill, trw-loop, trw-swarm) for developers already running the open framework.
For individual developers, not team rollout — if you are evaluating TRW for a team, see the Enterprise path.
- trw-distill — seed agent memory from your git history before the first session.
- trw-loop — long-running unattended sessions with fail-closed safeguards.
- trw-swarm — multi-agent execution with verifier-owned completion checks.
- Admission to the tester program is curated and application-based while the tools are in alpha/beta.
Talk to us
For organizations running AI coding agents across multiple teams. A design-partner motion, scoped per case.
- Govern work across time — requirement-to-verification records and governed knowledge, across teams.
- Available to evaluate today: single-org team workspace, owner/admin/member/viewer roles, org-scoped audit trail and analytics, GDPR export.
- SSO/SAML/OIDC, SCIM, org-admin cross-team rollup, and self-host/VPC are design-partner conversations.
- No public list price — scoped per case.
Choose based on what problem you have now
Still proving that AI agents can work reliably in your repo? Start with the free framework. Want the proprietary tooling early? Apply to the tester program. Rolling TRW out across teams? Talk to us.
Start here
Framework
- Best for
- Individual developers evaluating TRW in a real repo.
- Where it runs
- Inside your repo and local environment.
- Data path
- Repo-local after install by default.
- Cost today
- Free during public beta.
- How to start
- Create a free account and install in minutes.
Proprietary preview
Tester program
- Best for
- Developers who want early access to proprietary tooling (trw-distill, trw-loop, trw-swarm).
- Where it runs
- Locally, alongside your open-framework install.
- Data path
- Repo-local — same model as the open framework.
- Cost today
- No public pricing — curated tester-program access.
- How to start
- Apply for the tester program with a note about your workflow.
Team rollout
Enterprise
- Best for
- Organizations planning rollout across multiple teams.
- Where it runs
- Local-first across teams; hosted org surfaces are part of the rollout conversation.
- Data path
- Org-scoped audit and analytics server-side when connected; the open framework stays repo-local.
- Cost today
- No public list price — design-partner, scoped per case.
- How to start
- Contact TRW about rollout fit and timing.
Common pricing questions
The framework is free and self-serve in open public beta. Proprietary tooling (trw-distill, trw-loop, trw-swarm) reaches testers first through a curated application. Nothing here carries a public price yet — when it does, it will be on this page.
Is the free framework a stripped-down demo?
No. The repo-local workflow is the core product path. The framework (trw-mcp, trw-memory) is fully functional in public beta — source-available under BSL-1.1. Proprietary tooling (trw-distill, trw-loop, trw-swarm) is invite-only through the tester program.
Do I need the hosted platform to get value?
No. The framework works entirely in your local environment. Hosted dashboards and org surfaces are on the roadmap — not a prerequisite for value.
Can we start free and expand later?
Yes — that is the intended path. Evaluate the framework in a real repo first. If it fits and organizational rollout is your next question, contact TRW about roadmap fit and timing.
Offline-first
The default framework path keeps your code and project state in your environment.
Low lock-in
You can stop using TRW without replatforming your codebase or build stack.
Built for review
Requirements, validation, and delivery evidence are part of the workflow instead of afterthoughts.