Evaluate the framework first. Use contact when rollout planning becomes the question.
TRW is free during public beta — create a free account and install in minutes, no approval required. Advanced proprietary tooling (trw-distill, trw-loop, trw-swarm) is available through the alpha/beta tester program. Organizational rollout planning is handled through docs plus contact.
Free
Free during public beta. Create a free account instantly — no approval required.
- Core workflow: requirements, execution, review, and delivery stay inside your repo once installed.
- Knowledge continuity through learnings, checkpoints, and session-start recall.
- 43 MCP tools and 26 bundled skills for repeatable workflows instead of ad hoc prompting.
- Verification gates for tests, type checks, and review before delivery.
- Open public beta — create a free account instantly, no approval required.
Tester program
Use this when your question shifts from "does TRW fit our workflow?" to "what does rollout planning look like later?"
Apply for the alpha/beta tester program to get early access to proprietary tooling (trw-distill, trw-loop, trw-swarm). Admission is curated and application-based.
- Hosted dashboards and synced telemetry are part of the broader TRW roadmap.
- Admin and organization-level surfaces are still a guided rollout conversation, not a generally available team product.
- Best used when your question is about future rollout fit, timing, or operational needs beyond one user.
- Contact-led evaluation is the right path for companies thinking beyond a single repo or operator.
Talk to us
For organizations running AI coding agents across multiple teams. A design-partner motion, scoped per case — no public list price.
See /for/enterprise for the full organizational capability detail.
- 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, org-scoped analytics, GDPR export, local-first open framework.
- Enterprise identity federation (SSO/SAML/OIDC, SCIM), org-admin cross-team rollup, and self-host/VPC: talk to us about fit for your environment.
- Design-partner motion, scoped per case — no public list price.
Choose based on what problem you have now
If you are still proving that AI agents can work reliably in your repo, start with the framework. If the workflow already makes sense and your next question is about rollout planning, governance, or timing, talk to TRW instead of assuming the hosted or organization-level path is ready now.
| Decision area | Framework | Platform beta | Enterprise |
|---|---|---|---|
| Best for | Individual developers evaluating TRW in a real repo workflow. | Teams and companies assessing future rollout fit and hosted roadmap needs. | Multi-team organizations evaluating org-wide rollout fit and governance evidence. |
| Where it runs | Inside your repo and local environment. | Hosted TRW platform connected to your local framework installs. | Across teams via the hosted platform, above any IDE, model, or host via MCP. |
| Data path | Repo-local after install by default. | Adds hosted sync and dashboards when configured and available. | Org-scoped audit and analytics server-side when connected; the open framework stays repo-local. |
| Buying motion | Read the docs, create a free account, and install in minutes. | Learn the model first, then contact TRW for rollout planning. | Design-partner, per case — talk to us about org rollout fit. No public list price. |
Common pricing questions
The framework is free and self-serve in open public beta. Proprietary tooling (trw-distill, trw-loop, trw-swarm) is invite-only through the tester program. Organization-level rollout conversations are separate because the admin and hosted path is still taking shape.
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 current beta is centered on getting the framework workflow right for real repo work. Hosted surfaces are a separate conversation, not a prerequisite for value.
Can we start local and add the platform later?
Yes. In practice today, that means evaluating the workflow first. If it fits and you are thinking about organizational rollout later, 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.