Scoped pilot
Edge
A customer-bound runner package for approved targets, bounded collection plans, and retained evidence.
Before activation
- enrolled environment
- independent secrets
- durable storage
- approved targets
- authenticated smoke run
A focused pilot. A clear basis to expand.
Start with the evidence review your team needs to complete. Define the deliverables and acceptance checks, then choose the deployment boundary. Pricing is scoped to that work; there is no public price list.
The starting engagement
Start with one evidence review.
For the compliance lead preparing the record and the reviewer who needs to trust it.
One project, one framework objective, one approved source boundary, and a named reviewer.
Define what the review must prove before expanding to more teams or systems. The pilot tests your configured workflow against agreed acceptance criteria.
- A scoped audit workplan
The requirement references, assessment period, source systems, owners and review steps for the selected objective.
Acceptance check Your team can identify what is in scope, what is excluded, and who accepts each part of the work.
- A source-linked review set
Selected artifacts, proposed mappings and an explicit queue of missing or contradictory evidence.
Acceptance check A reviewer can trace each proposed mapping to its source. Unsupported conclusions remain unresolved.
- A recorded review and handoff
Named human decisions with rationale, plus the export and verification path agreed for this pilot.
Acceptance check A second reviewer can inspect the decisions and repeat the agreed integrity checks. Failed checks remain visible.
- A measured expansion decision
Observed preparation time, review touches and rework compared with your starting baseline.
Acceptance check You decide whether to expand using the recorded work and unresolved gaps. Savings are measured, not assumed.
The proposal names the supported collection and export paths, required setup and exclusions. AI proposes; human reviewers accept evidence. A pilot does not issue a certification or an independent audit opinion.
What determines the price
A scoped proposal makes the delivery work, responsibilities and exclusions visible before the pilot begins.
- Work in scope
- The selected objective, evidence volume, participating reviewers and the collection methods the pilot needs.
- Environment and setup
- The deployment boundary, identity integration, approved sources, storage and any work needed to activate the supported paths.
- People and responsibilities
- Implementation support, customer source owners and the named reviewer responsible for accepting the work. Additional scope is identified separately.
Choose where the work runs
The same pilot questions apply to each path. Your network, identity and data requirements determine the configuration that must be validated before activation.
Managed pilot
Cloud
A managed control-plane pilot using the implemented evidence, review, release, and verification paths.
Before activation
- confirmed framework and connector scope
- named identities
- custody plan
- pilot acceptance criteria
Private environment design
Enterprise
Dedicated deployment, tenant identity, isolation, support, and audit-firm collaboration designed against buyer requirements.
Before activation
- buyer-approved architecture
- identity and isolation design
- service boundary
- activation evidence
Production availability depends on the configured path passing its activation checks. A deployment description is not evidence that your environment is activated.
Bring your security reviewer into the conversation.
Review the published capability boundaries and the evidence available for diligence.