0–5 min
Install and activate
With the signed package and evaluation license already in hand, verify the checksum, start the compose stack, create the first administrator, and load the signed license.
15-minute Local evaluator · clock starts after package delivery
Reach one verified, mapped artifact without surrendering your evidence boundary
Request delivery before you schedule the evaluation; package and license fulfillment is a human step and is not included in the 15-minute clock. Success is not “the dashboard loaded.” Success is a fresh artifact from a verified source, mapped to a requirement and inspectable with provenance.
5–10 min
Choose a proof source
Use the clearly labelled disposable sample path to learn the UI, or connect a read-only GitHub App to an organization and repository you control.
10–15 min
Prove first value
Verify the connection, collect once, then open a fresh artifact and confirm its mapped control, captured time, content hash, validation, and freshness.
Disposable sample
Fastest UI orientation. Every sample object is labelled test data and must not be presented as production evidence or a real provider verification.
Live read-only GitHub
The release proof path. You choose the organization and repositories; verification rejects undeclared or inaccessible scope before collection.
Exact data boundary
- Evidence payloads, credentials, hashes, mappings, and audit history remain in your Local deployment.
- Licensing and update checks exchange only their documented metadata.
- Optional telemetry from your Local installation is off by default and never includes raw evidence, credentials, tenant IDs, email addresses, repository names, or artifact identifiers.