Compatible with how public-sector procurement actually works.
Five tiers of deployment scope, four contracting frameworks. Pick the tier that matches the programme; we map it onto the right framework for the destination jurisdiction.
- PR.01
Pilot deployments
Single-city, single-agency or single-operator pilots. Fixed scope, signed SOW, success metrics agreed before code ships.
Cadence·60–90 days - PR.02
City rollouts
Production deployment across one urban jurisdiction. Identity-federation, payments orchestration and audit trail wired into the city's existing systems.
Cadence·90–150 days - PR.03
Regional deployments
Multi-city or county-scale. Shared identity backbone, region-aware data residency, and coordinated rollout cadence with regulatory checkpoints.
Cadence·4–9 months - PR.04
National infrastructure programmes
Country-scale digital infrastructure programmes. Sovereign deployment, ministry-level governance, statutory export readiness.
Cadence·6–18 months - PR.05
White-label platform licensing
Re-brand, re-deploy under your jurisdiction or operator brand. Source escrow, shared-runbook handover, separate compliance attestation chain.
Cadence·Per agreement
Frameworks supported.
- PC.01
Dynamic Purchasing Systems
Available through DPS catalogues for digital, cloud, and platform infrastructure procurement.
Scope·EU · UK · Nordic - PC.02
G-Cloud-style frameworks
Compatible with G-Cloud and equivalent national catalogue frameworks for SaaS and managed services.
Scope·UK · Commonwealth - PC.03
OJEU / Find-a-Tender
Responds to public restricted, open and competitive dialogue procedures published under OJEU and FTS.
Scope·EU · EEA · UK - PC.04
National framework agreements
Delivered through national framework agreements and ministry-level master service agreements where DPS does not apply.
Scope·AF · MENA · regional
Procurement and contracting routes are confirmed during the EP.03 environment-selection step. Pre-intake fit confirmation does not require a procurement decision.