Step 1
Prepare your host
Confirm the supported platform, Docker requirements, disk capacity and backup location. Assign a technical owner. Read the package instructions before setup.
Assisted Local evaluation
Reach one verified, mapped artifact in your own environment
Start with an evidence task your team needs to complete. Package and license fulfillment is a human step. We confirm source scope, host requirements and delivery before you install. Setup time depends on your host, source permissions and access approvals.
What the evaluation includes
The current standard Compliance Pro evaluation lasts 14 days from license issuance, with no grace period. Confirm delivery and your setup window before issuance. It does not create a paid subscription or convert automatically. Your license and delivery message state the exact expiry.
The evaluation uses your host and supported source access. We confirm assistance and availability for your task before delivery. This is separate from the planned AI Readiness preview, whose enrollment is not open.
Export useful records before expiry. After expiry, the qualified evaluation path restricts evidence views and exports. Previously downloaded packets remain ordinary files you can retain and inspect. Your team decides which files and backups to keep or delete.
Step 2
Connect a proof source
Use a disposable sample to learn the UI, then connect a supported read-only source. For GitHub, choose an organization and repositories you are authorized to inspect.
Step 3
Review and export
Verify the connection, collect once and inspect the source, capture time, content hash, freshness and control links. Review suitability before exporting a packet.
Disposable sample
Learn the UI with clearly labelled test data. Samples must not be presented as production evidence or a real provider verification.
Live read-only GitHub
Choose the organization and repositories you control. Verification checks declared scope before collection. Inspect the artifact to confirm that it answers your actual evidence request. A successful collection alone does not establish compliance.
Exact data boundary
- Evidence and source credentials are stored in your Local deployment. You control exports and optional sync.
- Source APIs, optional AI, licensing and update checks have distinct data flows. Review them before enabling a connection.
- Optional telemetry from your Local installation is off by default. Review the operating guide and package settings.