Deployment overview
Choose between Managed SaaS and Customer-managed Azure based on who will operate the environment and its controls. Involve your security, privacy, platform, and product owners.
Compare the supported models
| Area | Managed SaaS | Customer-managed Azure |
|---|---|---|
| Azure subscription | Operated by VeriProof | Operated by the customer |
| Network policy | VeriProof service boundary | Customer-approved ingress, egress, DNS, and private connectivity |
| Identity | VeriProof service configuration | Customer identity design within supported product roles |
| Data region and stores | Confirm during diligence | Set and validate in the customer Azure architecture |
| Keys and secrets | Managed service controls | Customer Key Vault policy and supported secret references |
| Monitoring and incidents | VeriProof operations | Customer operations with agreed VeriProof support |
| Proof provider | Confirm for the deployment | Select and validate Azure SQL Ledger or Solana |
Customer-managed Azure
The deployment package places supported services and data stores in your approved Azure boundary. Your organization operates Azure; VeriProof provides release requirements, configuration guidance, and diagnostics.
Some configuration uses Hybrid for Customer-managed Azure. Enter that value only where the supplied deployment instructions require it.
Read the Customer-managed Azure guide before solution design.
Requirements outside the supported models
Intermittent connectivity and fully disconnected operation are architecture requirements, not separately released SDK modes.
- Intermittent connectivity explains what to measure and confirm.
- Disconnected environments states the current product boundary.
The released SDK uses one VeriProof endpoint. Any additional operating pattern requires a documented solution review and qualification plan.
Before provisioning
Record the agreed configuration and responsible owner for each area before provisioning:
- Azure subscription, region, service quotas, and approved resource providers
- identity, privileged access, emergency access, and access-review owners
- ingress, egress, private endpoints, DNS, certificates, and firewall policy
- data classification, capture, retention, deletion, backup, restore, and export requirements
- proof provider, verification method, monitoring, and reconciliation ownership
- deployment, upgrade, vulnerability remediation, incident response, and support responsibilities