Edge
A scoped evidence-lane pilot where collection must run inside an approved customer boundary.
Scoped pilot engagement
Choose the boundary before the package.
Edge, Cloud, and Enterprise are deployment paths, not a promise that every connector or service is already active. We confirm the evidence lane, operating boundary, identities, custody, and acceptance criteria before quoting the engagement.
Three packages, one proof discipline
Every engagement starts with a bounded proof plan and explicit activation gates. Public pricing is not posted because the commercial scope depends on the actual systems, frameworks, network boundary, and evidence-custody requirements.
Cloud
A managed pilot using ControlFrame's implemented evidence, review, release, and verification paths.
Managed pilot engagement
Enterprise
A buyer-specific private environment designed around identity, isolation, support, and audit collaboration requirements.
Custom enterprise agreement
Deployment capability matrix
Contracted scope supersedes this planning comparison.
- Included
- Implemented in the package’s configured scope.
- At activation
- Becomes available once that package’s activation gate passes.
- Contracted
- Defined by the signed engagement, never inferred from this page.
Swipe horizontally to compare Cloud and Enterprise →
| Capability | Edge | Cloud | Enterprise |
|---|---|---|---|
| Operating boundary | Customer-bound runner package Approved targets and bounded collection plans. At activation | Managed control-plane pilot Custody boundary documented before activation. At activation | Dedicated deployment boundary Designed and reviewed against buyer requirements. Contracted |
| Evidence workflow | Full workflow, one pilot lane Collect, retain, review, release, and verify in scope. Included | Implemented governed paths Evidence, review, release, and offline verification, scoped by the pilot statement of work. Included | Same workflow, validated extensions Extended only for capabilities validated during enterprise activation. Included |
| Activation gate | Authenticated smoke run required Enrolled environment, independent secrets, durable storage, approved targets. At activation | Confirmed scope and custody Framework and connector scope, named identities, custody plan, pilot acceptance criteria. At activation | Buyer-approved activation evidence Architecture, identity and isolation design, and the service boundary. At activation |
| Framework and connector scope | One named evidence lane The approved target is named before collection begins. At activation | Confirmed in the SOW Never inferred from a logo count. Contracted | Contracted against verified requirements Framework packs, connector packs, and custom source modeling. Contracted |
| Identity and service commitments | Pilot-scoped credentials only Identities and runner credentials exist only for the approved environment. At activation | Documented pilot access Access and support terms cover the configured scope. Contracted | Contracted after activation evidence SAML, SCIM, production service levels, and support commitments. Contracted |
What the packaging review produces
A named evidence lane, approved systems and identities, a custody boundary, activation dependencies, human release responsibilities, pilot acceptance criteria, and a commercial quote. No production capability is represented as active until its configured path has passed the agreed evidence gate.