Migrating to Atlasflow

Migrating to Atlasflow

View as Markdown

Move an existing app from another platform to Atlasflow.

Migrating to Atlasflow is mostly about making sure your app runs as a container that listens on the right port. Once that's true, deploying is the same as any other Atlasflow project.

The universal checklist

No matter where you're coming from, every migration comes down to the same few steps:

  1. Containerize: add a Dockerfile, or rely on automatic builds if your stack is supported.
  2. Listen on port 3000: bind to 0.0.0.0:3000. See Container requirements.
  3. Respond on GET /: the health check expects a 2xx response.
  4. Move your config to environment variables: split values into build and runtime scopes.
  5. Connect the repository: create an Atlasflow project from your GitHub repo.
  6. Point your domain: add and verify a custom domain, then cut over DNS.

Platform guides

What's different about Atlasflow

TopicAtlasflow approach
SourceGitHub App; deploys on push to your default branch.
BuildsDockerfile, or Railpack auto-detection.
PortFixed at 3000; bind to 0.0.0.0.
RuntimeOne container per deployment, isolated on a microVM.
ConfigProject settings plus environment variables; no platform-specific config file.
DomainsVerified via DNS; TLS is automatic. See Custom domains.
PricingPer-second usage billing with included credits.

Cutting over safely

Deploy on Atlasflow and test against the preview URL before changing DNS. When you're confident, point your domain at Atlasflow and verify it. Keep the old platform running until traffic has fully moved and you've confirmed everything works.

Next steps

Pick your current platform from the list above, or start with Getting started if you're ready to create a project.