Pick the rollout depth that matches your implementation.

Start with the live demo and public workspace path, then add rollout support when the route graph, publishing flow, and experiment cadence get more serious.

Launch

For teams getting their first app connected and learning the route model.

$0

Early product access

  • 1 workspace
  • Route graph + demo access
  • Flags, configs, and drafts
  • Basic Clara feed

Team

For teams that want onboarding help, rollout guidance, and feedback loops during implementation.

$199/mo

Billed annually

  • Everything in Launch
  • Publishing support
  • Setup guidance for SDK + edge
  • Shared rollout reviews

Enterprise

For organizations standardizing experiments, governance, and rollout patterns across apps.

Custom

For larger programs

  • Priority support
  • Commercial review
  • Security + procurement coordination
  • Roadmap collaboration

Security

Built for enterprise security requirements.

Capture runtime, delivery boundaries, and procurement details are designed for teams with real security review processes.

Capture boundaries

Scenarios run locally or in your CI environment. Execution stays inside the engineering controls your team already trusts.

Storage and delivery

Managed delivery serves stable image URLs by default. Enterprise evaluations can scope bring-your-own-storage rollout paths when vendor boundaries are stricter.

Procurement-ready

Security overview, DPA, subprocessors list, and rollout requirements are available for review.

FAQ

Frequently asked questions

What counts as a docs visual?

The current plans are organized around rollout depth, not raw traffic. The evaluation usually depends on route coverage, publishing setup, and the support needed during implementation.

What happens when I hit my limit?

The team will scope the next rollout step with you before hard limits become the bottleneck. The current product motion is still hands-on rather than quota-driven.

Can I try it without a credit card?

Yes. The demo is public, and the workspace path starts with sign-in rather than a billing step.

Start with one route

Start with the product truth, then deepen the rollout.

Open the demo, sign in when you want a real workspace, and use a walkthrough when the evaluation depends on your current routing or publishing setup.