PortabilityLabs — evaluation brief
Reviewed: 2026-10-25
Canonical guide: https://portabilitylabs.com/evaluate/

THE QUESTION
Which application would be hardest to move at short notice?

A USEFUL FIRST RESULT
An agreed workload boundary, a map of supported resources and connections, required success criteria, and a scoped simulator result with its time, checks and limitations.

CHECK THE FIT
Current AWS discovery covers 17 resource families and selected connections. Discovery, simulation and original-application execution are different capabilities. Check the exact AWS coverage before requesting access.
Start with one application your team knows, an engineering owner and made-up test values. Do not share AWS credentials, production records, logs or application code in an access request.

BEFORE CONNECTING ANYTHING
1. Review AWS coverage and choose a public architecture example. No account is needed. A product demonstration uses our own workloads; it does not connect your AWS account.
2. Have your engineer/security reviewer inspect permissions, data handling and the shared hosted-service boundary. Workload selection is not an IAM permission boundary.
3. Agree one customer-visible outcome, the execution method and what would count as a useful result. Stop if an essential dependency or required execution option is unsupported.
4. Request an invitation only if the fit is useful. The WorkOS waitlist takes your email; it does not create a workspace, connect AWS, deploy infrastructure or charge you.

CURRENT LIMITS AND ONBOARDING GATES
- Retrieved Lambda code is quarantined, not executed. A simulation pass is not proof that your original application migrated.
- Scheduled monitoring repeats the pinned workload definition; it does not automatically rediscover changes in AWS.
- Customer-hosted and sovereign deployments are designs requiring agreed implementation and acceptance, not self-service installations.
- Hosted privileged workers and data services remain shared. Stronger customer-specific containment is required before broad live-customer onboarding.
- Legal contracting identity, privacy and processing terms, retention and deletion, working support/security contacts and any service levels must be agreed before live onboarding.
Temporary AWS sessions may renew while role trust remains. To withdraw access, stop future assumption AND revoke existing sessions in AWS; disconnecting the portal alone is not emergency revocation.

COMMERCIAL DISCUSSION
Published starting points are on the pricing page. Confirm workload scope, allowances, execution/hosting costs, support, retention and export arrangements in a written proposal. Joining the waitlist is not a purchase or a service-level agreement.

SHARE THESE WITH YOUR REVIEWERS
Product walkthrough: https://portabilitylabs.com/examples/portability-evidence/
Architecture choices: https://portabilitylabs.com/examples/
Product demonstration and current invitation options: https://portabilitylabs.com/demo/
AWS coverage: https://portabilitylabs.com/aws/
Security and compromise boundary: https://portabilitylabs.com/security/
Trust and procurement: https://portabilitylabs.com/trust/
Data overview (not a completed legal notice): https://portabilitylabs.com/privacy/
Access removal: https://portabilitylabs.com/docs/connect-aws/#remove-access
Deployment designs: https://portabilitylabs.com/deployments/
Plans: https://portabilitylabs.com/pricing/
First workload: https://portabilitylabs.com/docs/get-started/
Product updates: https://portabilitylabs.com/updates/
Request access: https://portabilitylabs.com/contact/

Technical review material, not a contract, certification, regulatory opinion or guarantee of migration readiness. No customer data or deployable application package is included.