All Docs
FeaturesSaaS FactoryUpdated March 12, 2026

Multi-Cloud & Alternative Deployment Target Support

Multi-Cloud & Alternative Deployment Target Support

Available from: v1.0.156

The SaaS Factory autonomous deployment pipeline now supports multiple cloud and hosting platforms. Vercel remains the default, but projects can be deployed to AWS, Railway, Fly.io, and Netlify using the same fully autonomous pipeline.

Supported Deployment Targets

PlatformTypeNotes
VercelServerless / EdgeDefault. Unchanged behaviour.
AWSCloud InfrastructureRecommended for enterprise / self-hosted tier
RailwayContainer-based PaaSLightweight, fast provisioning
Fly.ioEdge-distributed PaaSLow-latency, globally distributed
NetlifyServerless / StaticStatic sites and serverless functions

How It Works

Previously, three core platform components were hard-coded to Vercel:

  1. Project bootstrapping (bootstrap.ts) — created Vercel projects directly
  2. Deployment triggering & readiness polling (unified-loop.ts) — called triggerVercelDeploy and waitForDeployReady
  3. Environment variable propagation — used pushEnvVarsToVercel

All three are now abstracted behind a provider-agnostic interface. Each supported platform has a corresponding adapter that implements:

  • bootstrapProject() — provisions the project on the target platform
  • triggerDeploy() — initiates a deployment
  • waitForDeployReady() — polls until the deployment is live
  • pushEnvVars() — writes environment variables to the target platform

The autonomous loop (unified-loop.ts) calls the interface — it has no knowledge of which platform is active.

Configuration

Set the DEPLOY_TARGET environment variable in your project configuration to select a deployment platform:

# Available values: vercel (default), aws, railway, fly, netlify
DEPLOY_TARGET=aws

Vercel is used when DEPLOY_TARGET is unset or set to vercel.

Enterprise Self-Hosted Tier

Enterprise customers on AWS or GCP can now use the full autonomous deploy pipeline. Previously, the pipeline would bootstrap and build the project but could not push deployments to non-Vercel infrastructure — this was a documented blocker for the Enterprise self-hosted tier.

With v1.0.156, the pipeline:

  • Bootstraps projects on the customer's chosen platform
  • Pushes environment variables to the correct secrets store
  • Triggers and monitors deployments without any manual intervention
  • Reports deployment status back into the platform's observability dashboard

Refer to docs/self-hosted-deployment.md for full infrastructure setup instructions per platform.

Existing Vercel Deployments

No migration is required. All existing Vercel-deployed projects continue to operate exactly as before. The Vercel adapter is a drop-in replacement for the previous hard-coded implementation and is backwards compatible.

Related