FAQ

# What does Atlasflow run?

Containerized web applications. You connect a GitHub repository, and Atlasflow builds a container image and runs it on a microVM. Any language or framework that runs in a container works.

# Do I need a Dockerfile?

No. If you have one, Atlasflow uses it. If you don't, it auto-detects your stack and builds it. See Supported frameworks.

# What port does my app need to listen on?

Port 3000, bound to 0.0.0.0. Atlasflow's edge proxy forwards traffic there. See Container requirements.

# How do deployments get triggered?

Automatically, on every push to your project's default branch. You can also trigger a manual redeploy.

# Can I deploy multiple apps from one repository?

Yes. Create one project per app and set each project's root directory.

# Is there a CLI?

Not today. Atlasflow is driven by Git pushes and the dashboard.

# How am I billed?

Per second, for compute, memory, storage, and traffic, with monthly included credits. Each plan has a monthly minimum.

# Do I need a paid plan to deploy?

Yes. A workspace needs an active subscription to create deployments.

# Can I run in multiple regions?

Multi-region is available on the Team plan. Hobby and Pro run in a single region.

# Does Atlasflow offer a managed database?

Managed database, storage, and queues are coming soon. For now, connect to an external provider via runtime environment variables.

# How do custom domains and TLS work?

Add a domain, create the DNS records shown, and Atlasflow verifies ownership and issues TLS certificates automatically. See Custom domains.

# Where are my logs?

Build logs and runtime logs are on each deployment. Retention depends on your plan.

# Related

• Getting started
• Troubleshooting