Deployment options
Choose where your assurance runs.
Choose the boundary your security team needs. Keeping a test inside your cloud and keeping the whole platform inside your estate are different decisions.
| Question | Managed portal | Customer-hosted execution | Sovereign platform |
|---|---|---|---|
| Who hosts the portal? | PortabilityLabs | PortabilityLabs | Your organisation |
| Where is discovery performed? | Hosted worker using approved temporary AWS access | Customer-local collector by agreed design | Inside your estate by agreed design |
| Where does application testing run? | Only in an approved isolated venue | Dedicated target inside your approved account/network | Inside your estate |
| Where is evidence retained? | Managed platform | Local raw evidence; approved summary may reach managed portal | Customer-local stores |
| Is it self-service today? | Private early-access discovery and simulator path | Architecture and implementation by agreement | Architecture and implementation by agreement |
Keep test execution local
Customer-hosted
Use the managed portal while collection and tests follow an approved customer boundary.
See the architecture →Keep the whole platform localSovereign
Portal, identity, workers, keys and evidence belong inside the customer estate.
See the architecture →Review access and controlsSecurity & trust
Separate current controls, admission requirements and contractual questions.
Review the product →Need a controlled deployment?
Request access and discuss the workload, network and evidence boundary before any deployment is agreed.