Evaluate the framework first. Use contact when rollout planning becomes the question.
TRW is free during beta, but access is currently limited while onboarding hardens. The first question for most people is whether the framework improves a real repo workflow. Organizational rollout planning comes later and is handled through docs plus contact.
Framework
Free
Free during beta. Access is currently limited while onboarding hardens.
- Core workflow: requirements, execution, review, and delivery stay inside your repo once installed.
- Knowledge continuity through learnings, checkpoints, and session-start recall.
- 24 MCP tools and 24 bundled skills for repeatable workflows instead of ad hoc prompting.
- Verification gates for tests, type checks, and review before delivery.
- Beta access is currently approved case-by-case while onboarding hardens.
Platform / rollout
By invitation
Use this when your question shifts from "does TRW fit our workflow?" to "what does rollout planning look like later?"
- 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.
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 |
|---|---|---|
| Best for | Individual developers evaluating TRW in a real repo workflow. | Teams and companies assessing future rollout fit and hosted roadmap needs. |
| Where it runs | Inside your repo and local environment. | Hosted TRW platform connected to your local framework installs. |
| Data path | Repo-local after install by default. | Adds hosted sync and dashboards when configured and available. |
| Buying motion | Read the docs, then request beta access when the workflow fits. | Learn the model first, then contact TRW for rollout planning. |
Common pricing questions
The main thing to know is that access is controlled, not upsold. The framework is the primary entry point. 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 gate is about controlled rollout and onboarding quality, not about hiding the real product behind a crippled demo.
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.