Frame the boundary
Agree the business capability, source accounts, data classification and acceptable discovery permissions.
Enterprise & government
Make the operating boundary part of the proof.
For regulated, public-sector and complex estates, portability evidence must respect identity, network, residency, approval and retention controls—not route around them.
A useful enterprise starting point
One representative workload, agreed success criteria.
Begin with a workload that exposes the real constraints: identity, networks, managed services, data, event flow and evidence requirements. The evaluation should reveal gaps, not hide them.
Review our interpretation
Validate the architecture, dependencies and unresolved questions against people who operate the system.
Define proof criteria
Choose the behaviours, target options, mocks and execution placement that make the result useful.
Choose the execution boundary
Run the same portable contract through a managed, customer-contained or sovereign operating profile.
Deployment profiles
One evidence model, different control boundaries.
ProfileBest forControl boundary
Managed isolated proofFast workload assessment, target testing and time-limited customer inspection.PortabilityLabs operated
Customer-contained executionSensitive tests deployed into a customer-controlled cloud account, subscription or project.Customer operated
Sovereign platformResidency, disconnected operation or a complete single-tenant management plane.Customer estate
Commercial shape
Price the assurance programme, not the scanner.
Enterprise scope can reflect active workload complexity, proof intensity, evidence retention, deployment profile and service level. Complete inventory should never be discouraged by per-resource metering.
Governance
Organisation boundaries, roles, approval gates, policy versions and evidence exports.
Security
Private connectivity, customer-controlled execution, data classification and isolation evidence.
Delivery
Implementation, workload onboarding, integration, training and an agreed support model.
Bring us a workload with real constraints.
We will use it to determine what can be evaluated now and what requires a customer-contained or sovereign delivery plan.