Destination evidence

Choose the infrastructure. See exactly what has been proven.

Deploy does not require Railway. The deep migration produces a portable release; destination qualification is a separate evidence layer. Railway and Render have live deep-certification evidence today. Other listed targets have provider handoff bundles that pass portable-conformance checks without being presented as live-account certifications.

Live Deep Certified

A real provider staging/reference deployment passed applicable state-equivalence, identity, authorization, health, rollback, and restore gates.

Portable Conformance

The provider handoff bundle and portable runtime contract pass automated conformance checks, but a live provider-account deployment is not claimed.

Portable Handoff

Portable Git, Docker, configuration, migration, and runbook artifacts can be delivered, with destination qualification completed per project.

Railway

Live Deep Certified

Base44 SwiftTask reference: exact source-state reconciliation, identity transition, authorization/RLS, live staging deployment, rollback, restore, and health revalidation passed.

Automated provider execution is available for qualified projects.

Render

Live Deep Certified

Base44 SwiftTask reference: exact 23-record/digest equivalence, identity transition, authorization/RLS, live staging deployment, rollback, restore, and repeated HTTP health checks passed.

Automated provider execution is available for qualified projects.

DigitalOcean

Portable Conformance

DigitalOcean App Platform Dockerfile/app-spec handoff passes the portable provider conformance battery. A live DigitalOcean account deployment has not yet been certified.

Portable handoff is available; live provider execution remains project/provider qualified.

AWS

Portable Conformance

OCI/Docker runtime, external PostgreSQL, secrets, health, and rollback contracts pass the portable provider conformance battery. No live AWS account deployment is claimed.

Portable handoff is available; live provider execution remains project/provider qualified.

Azure

Portable Conformance

Azure Container Apps handoff template and the portable runtime contract pass conformance checks. No live Azure account deployment is claimed.

Portable handoff is available; live provider execution remains project/provider qualified.

Google Cloud

Portable Conformance

Cloud Run handoff template and the portable runtime contract pass conformance checks. No live GCP account deployment is claimed.

Portable handoff is available; live provider execution remains project/provider qualified.

Kubernetes

Portable Conformance

Deployment/Service manifests, secret-backed configuration, port contract, and health probes pass automated conformance checks. No live cluster is claimed.

Portable handoff is available; live provider execution remains project/provider qualified.

Private VPS / on-prem

Portable Conformance

Docker Compose handoff, PostgreSQL contract, secret injection, health checks, and rollback expectations pass automated conformance checks. The customer's host remains project-qualified.

Portable handoff is available; live provider execution remains project/provider qualified.

What never changes by destination

A destination badge never waives project-specific migration checks. Production still requires the actual application to pass its applicable source acquisition, data, identity, authorization, files, functions, workflows, integrations, staging, reconciliation, approval, health, and rollback gates.