ControlLayer is packaged like an operational workspace, not a marketing funnel. Each tier keeps the same calm interface language used across the product while making it explicit where preview ends and governed rollout begins.
Deployment posture
The pricing surface mirrors the product stance: dense information, clear boundaries, and no implied live-billing behavior in preview mode.
Live billing posture
Disabled in preview
This environment keeps billing language descriptive only. Real charging, invoicing, and provider-side payment actions stay outside the demo surface.
Rollout gate
Human review first
Every tier keeps implementation posture explicit so operators know when a surface is preview-safe, pilot-ready, or still waiting on governance sign-off.
Data handling
Tenant-safe by default
The pricing surface stays aligned with the same boundary used elsewhere in the product: safe demo data, typed workflows, and no hidden provider calls.
Best for evaluation
PS0
demo-safe
Use the full operational shell, seeded contract data, and guided queues without enabling live billing, live provider writes, or customer export risk.
For governed pilots
PS240
per tenant / month
Adds tenant-scoped rollout planning, implementation checkpoints, and cleaner stakeholder packaging for teams moving from preview to controlled pilot.
For broader operations
PS640
per tenant / month
Reserved for teams that need wider governance packaging, denser reporting posture, and tighter review boundaries before circulation expands.
Capability comparison
Read-only, preview-safe packaging
| Capability | Preview | Rollout | Governance |
|---|---|---|---|
| Operational shell | Shared workspace preview | Tenant rollout framing | Leadership-ready posture |
| Contract and evidence queues | Demo-safe route access | Pilot handoff packaging | Governed circulation posture |
| Review controls | Visible, read-only cues | Checkpoint ownership lanes | Boundary and sign-off emphasis |
| Implementation support | Self-serve evaluation | Guided tenant onboarding | Cross-team operating cadence |
Boundary notes
The public pricing surface is intentionally clear about the edges of the demo. It should help teams understand rollout posture without pretending checkout, provisioning, or provider-side automation already exists.
Preview boundary
No live billing or customer self-provisioning is active here.
Teams can review packaging, operating posture, and rollout expectations, then move into a controlled human-led setup path when they are ready.
Recommended next move
Start in preview, then graduate into rollout only when your review lanes and ownership model are clear.
That keeps the interface honest, matches the product's governance language, and prevents a pricing page from over-promising what the underlying platform is not ready to automate yet.