Creator path
Individual evaluators
For creators or operators who want to inspect the workflow, validate fit, and understand the product direction before a larger rollout conversation.
Beta Access
Beta access built for staged adoption.
C is in limited beta. Start with proof, move into pilot, and expand into team or enterprise rollout when the workflow is ready.
Creator Team Enterprise
Start
See the demo
Validate
Pilot the workflow
Expand
Add governance and rollout
Current posture
Access is structured around fit, proof, and rollout depth.
We are intentionally not pretending public self-serve pricing is the right model yet. Beta access is built around real workflow fit.
Proof first: inspect the product and public-safe demos before a deeper conversation.
Pilot second: if the workflow is real, a guided pilot or briefing follows.
Rollout third: governance, security, and deployment scope come after workflow fit is proven.
Access paths
Different buyers need different entry points.
The goal is to match the conversation to where you actually are, not squeeze everyone into premature packaging.
Team path
Small-team pilots
For teams that need to validate semantic editing, review behavior, and context continuity in a real working loop.
Enterprise path
Governed rollout conversations
For organizations evaluating approvals, security, connectors, and deployment posture before wider adoption.
Partner path
Strategic pilots and investor observers
For stakeholders who need a structured view of where the product is now and how beta access connects to the broader company story.
What beta access means in practice.
These are the most common questions about access, timing, and what comes next.
- How do I get beta access?
- Request access through the join form. The team will route you to the right conversation based on workflow stage and interest.
- Is there public pricing yet?
- No. Public self-serve pricing comes after beta, proof, and rollout systems are mature enough to support it honestly.
- What does a pilot look like?
- A pilot focuses on workflow fit and proof. Can the product do useful work in your context? Governance, security, and enterprise scope come after that question is answered.
Choose the right conversation