Feature
Usage Limits & Trial Model
Understand caps, what is measured during trial, and how OrchesTerra keeps evaluation safe and predictable.
OrchesTerra’s trial model is designed to help you evaluate governance outcomes quickly—without leaving your evaluation blocked by operational caps.
What “trial” is for
During the trial, you should be able to:
- validate repository discovery accuracy,
- run drift detection signals,
- see governed reconciliation in action,
- and evaluate generated IaC quality on a real workload.
How caps are used
Usage caps help keep the trial predictable:
- they limit number of seats and connected cloud accounts as defined by the trial tier,
- and they constrain certain execution-style actions where required.
Why this matters
Governance systems often require repeatability. A trial should allow enough repetition to make a decision, not just a single walkthrough.
For how to start, see start a 14-day trial and the trial plan details on pricing.
FAQ
Does trial prevent drift scans from being useful?
The trial is scoped so evaluation remains meaningful. If a capacity limit becomes relevant, OrchesTerra routes you toward a clear upgrade path rather than failing silently.