# Fly.io: Fly docs Fly docs ## Fly docs - [Fly docs / Fly docs / Reference (335 pages)](https://docs.fly.io/_llms/fly-docs/fly-docs/reference.txt): flyctl. ### Getting Started - [Getting started](https://docs.fly.io/getting-started/index.md): Begin with Fly.io: the quickstart, hellofly demo, deep dive app, framework guides, and essentials, plus links to Fly Launch, Machines, networking, storage. - [Sign up and sign in to Fly.io](https://docs.fly.io/getting-started/sign-up-sign-in.md): Sign up for Fly.io with fly auth signup using email, Google, or GitHub, then sign in from your terminal with fly auth login, plus a browser fix for WSL users. - [Quickstart: Launch your app](https://docs.fly.io/getting-started/launch.md): Deploy your first app on Fly.io: install flyctl, sign up or log in, then run fly launch, which generates a Dockerfile and config for most frameworks. - [Launch a demo app](https://docs.fly.io/getting-started/launch-demo.md): Deploy the hellofly demo app to Fly.io with flyctl: run fly launch with a prebuilt image, check fly status, open the app, deploy changes, then delete it. - [Get started with your language or framework](https://docs.fly.io/getting-started/get-started-by-framework.md): Pick your stack: Fly Launch scanners detect and deploy Rails, Django, Laravel, Phoenix, Next.js, Go, Rust, .NET, and more, or fall back to any Dockerfile. - [Fly.io essentials](https://docs.fly.io/getting-started/essentials.md): Learn the core concepts of Fly.io: Fly Machines, Fly Launch, and Fly Apps, how fly launch, fly.toml, fly deploy, and fly scale fit together, plus a glossary. - [Migrate from Heroku](https://docs.fly.io/getting-started/migrate-from-heroku.md): Migrate a Heroku app to Fly.io: export config vars, run fly launch, move data to Managed Postgres, set up Redis and workers, then move your custom domain. - [Troubleshoot your deployment](https://docs.fly.io/getting-started/troubleshooting.md): Fix common Fly.io deployment problems: 502 and 503 errors, failed builds, wrong listen addresses, failing health checks, stuck Machines, and networking issues. - [Guides and Examples](https://docs.fly.io/guides.md): A short index of Fly.io guides: the going-to-production checklist, running cron jobs with Supercronic, and running an SSH server on a Fly Machine. #### Deep Dive - [Deep dive demo](https://docs.fly.io/deep-dive/index.md): An hour-long Fly.io demo deploying MDN's Web Dictaphone with Postgres, Tigris, and Upstash Redis WebSockets in Django, Next.js, Node, Phoenix, or Rails. - [Launch the demo](https://docs.fly.io/deep-dive/launch-deep-dive.md): Install flyctl, then run fly launch --from with the Django, Node.js, Next.js, Phoenix, or Rails dictaphone repo to deploy the deep dive demo on Fly.io. - [Whisper](https://docs.fly.io/deep-dive/whisper.md): Add speech-to-text to the deep dive demo with fly launch --attach, which runs OpenAI Whisper on an L40S GPU Machine that is reachable only over Flycast. - [Recap](https://docs.fly.io/deep-dive/recap.md): Wrap up the Fly.io deep dive after deploying a full-stack app with object storage, realtime updates, and AI, plus links to production, pricing, support. ##### What You Get - [Your Fly App](https://docs.fly.io/deep-dive/application.md): The Fly.io deep dive demo runs on two Fly Machines with autostop and autostart. Scale them vertically or with fly scale count, edit fly.toml, and redeploy. - [Deep Dive: PostgreSQL](https://docs.fly.io/deep-dive/postgresql.md): Fly Postgres in the deep dive demo starts as one Machine in its own app. Add an HA cluster and read replicas, and keep it on the private network only. - [Tigris](https://docs.fly.io/deep-dive/tigris.md): Tigris object storage serves the demo's audio files across regions with no setup. Make a bucket public, or migrate from S3 gradually with shadow buckets. - [Upstash Redis](https://docs.fly.io/deep-dive/redis.md): Upstash Redis in the deep dive demo broadcasts pubsub updates to each Machine, which tells browsers over WebSockets. It also caches for Node and Rails. ##### Runtimes reference - [Django demo reference](https://docs.fly.io/deep-dive/django.md): How the Django dictaphone demo fits together: Django Storages on Tigris, Channels on Redis, Postgres via DATABASE_URL, and Celery jobs that call Whisper. - [Next.js demo reference](https://docs.fly.io/deep-dive/nextjs.md): Walk through the Next.js dictaphone source: server.js WebSockets, the app/audio route for clip GET, PUT, and DELETE, pg for Postgres, pubsub.js for Redis. - [Node.js demo reference](https://docs.fly.io/deep-dive/nodejs.md): Tour the Express.js dictaphone demo: EJS views, the pg module, AWS SDK access to Tigris, express-ws WebSockets, and a Redis queue that updates browsers. - [Phoenix demo reference](https://docs.fly.io/deep-dive/phoenix.md): See how the Phoenix dictaphone demo uses LiveView, Ecto with Postgres, ExAws.S3 for Tigris, and Phoenix.PubSub.Redis, plus the Whisper audio controller. - [Rails demo reference](https://docs.fly.io/deep-dive/rails.md): Rails dictaphone demo internals: Stimulus controllers, Active Record on Postgres, Active Storage on Tigris, Action Cable on Redis, Sidekiq Whisper jobs. ### Guides (Blueprints) - [Guides and Blueprints](https://docs.fly.io/blueprints/index.md): Architecture patterns and how-to guides for Fly.io: per-user Machines, AI agents, MCP servers, deployments, private networking, scaling, and background jobs. #### Architecture Patterns - [Deploy OpenClaw on Fly.io](https://docs.fly.io/blueprints/deploy-openclaw.md): Deploy the OpenClaw AI agent gateway on Fly.io with a download-and-run script that creates the app, volume and secrets, then connect Discord, Telegram or Slack. - [Run Hermes Agent on Fly.io](https://docs.fly.io/blueprints/hermes-agent-on-fly-io.md): Run the Hermes AI agent from Nous Research on a Fly.io Machine with a volume for its state, configure an LLM key, and reach its web dashboard through fly proxy. - [Warm pools of user Machines](https://docs.fly.io/blueprints/warm-pool-user-machines.md): Make per-user apps start instantly: keep a pool of pre-provisioned Fly apps, volumes, and booted Machines, then claim one and configure it when a user signs up. - [Remote MCP Server Hosting: Deploy MCP Servers on Fly.io](https://docs.fly.io/blueprints/remote-mcp-servers.md): Host a remote MCP server on a Fly Machine that any MCP client can reach over HTTP and that stops when idle, as a multi-tenant app or one app per user. - [High availability: run multiple Machines](https://docs.fly.io/blueprints/resilient-apps-multiple-machines.md): A Fly Machine runs on one host and won't move if that host fails. Run at least two Machines per process, using autostop/autostart or standbys to limit cost. - [N-tier architecture](https://docs.fly.io/blueprints/n-tier-architecture.md): What n-tier architecture is, how presentation, web, and data tiers map to Fly Machines, private networking, and Postgres, and how to deploy a multi-tier app. - [Shared Nothing Architecture](https://docs.fly.io/blueprints/shared-nothing.md): Scale a Rails app as a shared-nothing monolith on Fly.io, with per-tenant SQLite on volumes, Phusion Passenger, Fly-Replay routing, and backups. - [Sticky sessions (session affinity)](https://docs.fly.io/blueprints/sticky-sessions.md): Send a user's requests to the same Fly Machine with the fly-force-instance-id request header from the client or the fly-replay response header from your server. - [Multi-region databases with read replicas and fly-replay](https://docs.fly.io/blueprints/multi-region-fly-replay.md): Run your app with a primary database and regional read replicas on Fly.io, and use the fly-replay header to send write requests to the primary region. - [Cell-based architecture](https://docs.fly.io/blueprints/cell-based.md): Give each user of your app a dedicated Fly Machine that stops when idle and restarts on access, routed with fly-replay and fly-force-instance-id. #### Deployment & Developer Workflow - [Working with Docker on Fly.io](https://docs.fly.io/blueprints/working-with-docker.md): How Fly.io turns Docker images into VMs: no Docker daemon, ephemeral filesystems, prebuilt images for faster deploys, image tags, and multi-container Machines. - [Custom deploy workflows: staggered and selective deploys](https://docs.fly.io/blueprints/custom-deploy-workflows.md): Roll out fly deploy to stopped Machines, one region, or one process group at a time, to deploy gradually without restarting Machines running long jobs. - [Zero-downtime deployments](https://docs.fly.io/blueprints/seamless-deployments.md): Get zero-downtime deploys on Fly.io with health checks that work, a rolling, canary, or bluegreen strategy, and release_command for migrations. - [Roll back a deploy](https://docs.fly.io/blueprints/rollback-guide.md): Undo a bad Fly.io deploy: find a previous release image with fly releases --image, redeploy it, tag images clearly, and handle database migrations separately. - [Git Branch Preview Environments on Github](https://docs.fly.io/blueprints/review-apps-guide.md): Deploy ephemeral review apps for every pull request using a GitHub Actions workflow and the fly-pr-review-apps Action on Fly.io, with custom specs and secrets. - [Separate staging and production environments](https://docs.fly.io/blueprints/staging-prod-isolation.md): Isolate production from staging on Fly.io by giving each environment its own organization, with separate members, apps, and fly.toml files. - [Per-User Dev Environments with Fly Machines](https://docs.fly.io/blueprints/per-user-dev-environments.md): Host isolated dev or code-execution environments for each user on Fly Machines, with one app per user, optional volumes, and a fly-replay router for subdomains. - [Use Docker base images for faster deploys](https://docs.fly.io/blueprints/using-base-images-for-faster-deployments.md): Build a shared base image as its own Fly.io app, push it to the Fly registry, and use it in FROM so each deploy rebuilds only your app, not every dependency. - [Managing Docker Images with Fly.io's Private Registry](https://docs.fly.io/blueprints/using-the-fly-docker-registry.md): Tag and push Docker images to registry.fly.io, deploy them with fly deploy --image, and reuse images across apps in your Fly.io organization without fly launch. #### Networking & Connectivity - [Run private apps with Flycast](https://docs.fly.io/blueprints/private-applications-flycast.md): Deploy a private HTTP service reachable only on your org's network with Flycast on Fly.io, routed by Fly Proxy so stopped Machines wake on demand. - [Connect to your private network with WireGuard](https://docs.fly.io/blueprints/connect-private-network-wireguard/index.md): Create a WireGuard peer with fly wireguard create and connect your laptop to your Fly.io organization's private network to reach apps and Flycast services. - [Connect AWS and other clouds with WireGuard](https://docs.fly.io/blueprints/bridge-deployments-wireguard.md): Join a server on AWS or another cloud to your Fly.io private network as a site-to-site WireGuard peer, so Machines and outside services talk privately. - [Route requests to per-user Fly Machines](https://docs.fly.io/blueprints/connecting-to-user-machines.md): Route HTTP requests to per-user Fly Machines through a router app with fly-replay, including port matching, authenticating replayed requests, and antipatterns. - [Run an SSH server on a Fly Machine](https://docs.fly.io/blueprints/opensshd.md): Install and run OpenSSH in your Fly.io app so rsync, scp, sshfs, VS Code Remote, Ansible, or Kamal can connect over SSH, with key setup and port 22 mapping. #### Scaling, Performance & Observability - [Stream logs from user apps with NATS](https://docs.fly.io/blueprints/observability-for-user-apps.md): Monitor apps your users run on Fly.io: deploy the fly-telemetry forwarder, subscribe to the NATS log stream, and route each user app's logs back to that user. - [Autoscale Fly Machines with autostop or fly-autoscaler](https://docs.fly.io/blueprints/autoscale-machines.md): Pair fly-autoscaler with Fly Proxy autostop/autostart to keep a fixed number of stopped Machines ready to start as traffic rises and falls through the day. - [Autostart and autostop private apps with Flycast](https://docs.fly.io/blueprints/autostart-internal-apps.md): Let Fly Proxy start and stop Machines for a private app on demand by giving it a Flycast address instead of public IPs, for new apps or existing ones. - [Setting Hard and Soft Concurrency Limits on Fly.io](https://docs.fly.io/blueprints/setting-concurrency-limits.md): Tune soft_limit and hard_limit for Fly Machines by load testing a copy of your app, then let autostop/autostart scale within those limits. - [Using Fly Volume forks for faster startup times](https://docs.fly.io/blueprints/volume-forking.md): Preload ML models, SQLite databases, or other large files onto a Fly Volume once, then fork it so new Machines boot with the data already in place. - [Run HIPAA-compliant healthcare apps](https://docs.fly.io/blueprints/going-to-production-with-healthcare-apps.md): Evaluate Fly.io for HIPAA: encryption in transit and at rest, network isolation, and access control. Then launch a pilot, sign a BAA, and deploy to production. #### Background Jobs & Automation - [Long-running tasks and machine lifecycle](https://docs.fly.io/blueprints/long-running-tasks.md): Why auto_stop_machines can stop a Machine that's still running background work, how Fly Proxy decides a Machine is idle, and two patterns that keep tasks alive. - [Building Infrastructure Automation without Terraform](https://docs.fly.io/blueprints/infra-automation-without-terraform.md): Fly.io has no Terraform provider. Get repeatable deploys with flyctl and GitHub Actions, or call the Machines API directly for custom orchestration. - [Background job queues with Celery, BullMQ, and Fly Machines](https://docs.fly.io/blueprints/work-queues.md): Move slow work like PDFs, emails, and API calls out of web requests into a work queue, using Celery for Python, BullMQ for Node, or on-demand Fly Machines. - [Task scheduling guide with Cron Manager and friends](https://docs.fly.io/blueprints/task-scheduling.md): Compare ways to run scheduled jobs on Fly.io, from Cron Manager's one-off Machines to Supercronic, scheduled Machines, and in-app schedulers. - [Crontab with Supercronic](https://docs.fly.io/blueprints/supercronic.md): Run cron jobs inside your app container on Fly.io with Supercronic: add a crontab, install it in your Dockerfile, and scale a single cron process group. - [Deno KV with LiteFS Cloud](https://docs.fly.io/blueprints/deno-kv-litefs.md): Back Deno KV with a SQLite database on LiteFS to run a Deno Deploy app on Fly.io. LiteFS Cloud has been sunset, so this guide is kept for reference. ### Model Context Protocol (MCP) - [Model Context Protocol](https://docs.fly.io/model-context-protocol/index.md): Run Model Context Protocol servers on Fly.io: fly mcp launch for stdio servers, plus choosing a transport, deploy method, host, and access control. - [Launch an MCP Server with fly mcp launch](https://docs.fly.io/model-context-protocol/launch.md): fly mcp launch deploys an npx, uvx, go run, or Docker stdio MCP server to a Fly Machine and configures your client; fly mcp inspect and destroy follow. - [flyctl mcp server](https://docs.fly.io/model-context-protocol/flyctl-server.md): Add the flyctl MCP server to Claude, Cursor, or Zed with fly mcp server, see which flyctl commands it supports, test in MCP inspector, or run it remotely. - [Fly agent setup](https://docs.fly.io/model-context-protocol/setup-agent.md): Set up Claude Code, Codex, Cursor, and other coding agents for Fly.io in one command. fly setup agent installs the Fly skills and the hosted Fly MCP server. - [Fly agent skills](https://docs.fly.io/model-context-protocol/agent-skills.md): Install the Fly.io agent skills into Claude Code, Codex, Cursor, and other coding agents with fly skills install, then update, pin, or remove them. - [Examples](https://docs.fly.io/model-context-protocol/examples.md): Copy-paste fly mcp launch commands for Fetch, internal DNS, Slack, Filesystem with a volume, GitHub, and Desktop Commander MCP servers, with secrets. #### Deploy with - [Deploy with](https://docs.fly.io/model-context-protocol/deploy-with.md): Compare fly launch, fly machine run, and the Machines API for deploying a stdio MCP server, using the Filesystem MCP Server with a volume as the example. - [Deploy an MCP Server with fly launch](https://docs.fly.io/model-context-protocol/deploy-with/fly-launch.md): Deploy an MCP server with fly launch on Fly.io from a short Dockerfile, use --flycast for private access, and redeploy changes to fly.toml with fly deploy. - [fly machines run](https://docs.fly.io/model-context-protocol/deploy-with/flyctl-machines.md): Deploy an MCP server with fly machine run on Fly.io: create the app, allocate IPs, add a volume, and start a Machine that uses fly mcp wrap as its entrypoint. - [Deploy an MCP Server with the Machines API](https://docs.fly.io/model-context-protocol/deploy-with/machines-api.md): Deploy an MCP server with the Machines API on Fly.io using curl and an org token to create the app, IP addresses, volume and Machine through REST calls. #### Deploy on - [Deploy on](https://docs.fly.io/model-context-protocol/deploy-on.md): Why to run each MCP server on its own Fly Machine instead of your laptop: isolation, plus access to volumes, SQLite databases, and app internal state. - [A Fly Machine](https://docs.fly.io/model-context-protocol/deploy-on/fly-machine.md): Run a remote MCP server on a Fly Machine: launch the flyio/mcp filesystem image on Fly.io, test it in the MCP inspector, and connect Claude Desktop. - [Your application](https://docs.fly.io/model-context-protocol/deploy-on/your-app.md): Run an MCP server inside your own Phoenix or Rails app on Fly.io with Tidewave, then point Cursor or another MCP client at it through mcp.json. #### Transports - [MCP Transports](https://docs.fly.io/model-context-protocol/transports.md): MCP transports on Fly.io: stdio (recommended), Streamable HTTP, and deprecated SSE, demonstrated with Anthropic's Everything MCP Server and printEnv. - [SSE](https://docs.fly.io/model-context-protocol/transports/sse.md): Deploy an SSE MCP server on Fly.io as is: expose its port, disable smoke checks in fly launch, and connect the MCP inspector or Cursor to the /sse URL. - [stdio](https://docs.fly.io/model-context-protocol/transports/stdio.md): Run a stdio MCP server remotely on Fly.io by wrapping it with fly mcp wrap in the Dockerfile and connecting from Claude Desktop through fly mcp proxy. - [Streaming HTTP](https://docs.fly.io/model-context-protocol/transports/streaming-http.md): Deploy a Streamable HTTP MCP server on Fly.io unchanged: expose port 3001, launch without smoke checks, and connect the MCP inspector or Cursor to the /mcp URL. #### Access control - [Access Control](https://docs.fly.io/model-context-protocol/access-control.md): Securing an MCP server on Fly.io starts with HTTP Authorization, since most stdio MCP servers were never meant to be exposed to the internet. - [Wireguard tunnels and Flycast](https://docs.fly.io/model-context-protocol/access-control/flycast.md): Keep an MCP server off the public internet on Fly.io with a private IPv6 address and Flycast, then reach it with fly mcp proxy using .internal or .flycast URLs. - [HTTP Authorization](https://docs.fly.io/model-context-protocol/access-control/http-authorization.md): Protect an MCP server on Fly.io with basic or bearer HTTP authorization: set FLY_MCP secrets on the app and pass matching flags to fly mcp proxy. ### App Guides - [Chat: A 6PN Example with NATS](https://docs.fly.io/app-guides/6pndemochat.md) - [Appkata: Gogs - standalone Git Server](https://docs.fly.io/app-guides/git-gogs-server.md) - [Run an NGINX proxy on Fly](https://docs.fly.io/app-guides/global-nginx-proxy.md) - [Apollo GraphQL + Edge Caching](https://docs.fly.io/app-guides/graphql-edge-caching-apollo.md) - [GraphQL on Fly with Hasura](https://docs.fly.io/app-guides/graphql-on-fly-with-hasura.md) - [Deploy gRPC and gRPC-Web Services](https://docs.fly.io/app-guides/grpc-and-grpc-web-services.md) - [Deploy Livebook on Fly.io](https://docs.fly.io/app-guides/livebook.md): Deploy Livebook to one Fly Machine with a 1GB volume: a ready fly.toml, LIVEBOOK_PASSWORD secret, shared-cpu-2x sizing, and auto stop and start notes. - [Appkata: MQTT - Event driven messaging](https://docs.fly.io/app-guides/mqtt.md) - [Use a MySQL Database](https://docs.fly.io/app-guides/mysql-on-fly.md): Run self-managed MySQL on Fly.io from the official image: volume, secrets, [processes] datadir and auth plugin flags per version, fly proxy, and backups. - [Global NATS Cluster](https://docs.fly.io/app-guides/nats-cluster.md) - [Appkata: Node-RED - Flow Programming](https://docs.fly.io/app-guides/node-red.md) - [OpenResty: NGINX + Lua](https://docs.fly.io/app-guides/openresty-nginx-plus-lua.md) - [Fly.io and PlanetScale](https://docs.fly.io/app-guides/planetscale.md): Connect a Node app on Fly.io to PlanetScale read-only regions, pick the closest replica per region, and replay writes to the primary with fly-replay. - [Postgres: A single server deployment for Fly](https://docs.fly.io/app-guides/postgres.md) - [Puppeteer JS Renderer](https://docs.fly.io/app-guides/puppeteer-js-renderer.md) - [Redis - standalone Redis Server](https://docs.fly.io/app-guides/redis.md) - [Appkata: Redistls - Redis Server with TLS](https://docs.fly.io/app-guides/redistls.md) - [Global Image Processing Service](https://docs.fly.io/app-guides/run-a-global-image-service.md) - [Run A Private DNS Over HTTPS Service](https://docs.fly.io/app-guides/run-a-private-dns-over-https-service.md) - [Smokescreen - Sanitize outbound web requests](https://docs.fly.io/app-guides/smokescreen.md) - [VS Code - Remote Server over SSH](https://docs.fly.io/app-guides/vscode-remote.md) ### Apps on Fly.io #### Apps on Fly.io - [Apps on Fly.io](https://docs.fly.io/apps/index.md): Fly Apps docs hub: Fly Launch for deploying and scaling, runtime and build secrets, and production guides on availability, tuning, and concurrency. - [Fly Apps overview](https://docs.fly.io/apps/overview.md): See what makes up a Fly App on Fly.io, a group of Machines with config, IPs, certificates, secrets and volumes, and the ways to create one. - [Get information about an app](https://docs.fly.io/apps/info.md): Inspect a running Fly App with fly status, fly machine status, fly ips list, fly config show, fly ssh console, and fly logs, with sample output. - [Restart apps or Machines](https://docs.fly.io/apps/restart.md): Restart all Fly Launch Machines in an app with fly apps restart, or reboot specific Machines by ID with fly machine restart to reset the root filesystem. - [Delete an app](https://docs.fly.io/apps/delete.md): Permanently delete a Fly App with fly apps destroy, removing its Machines, volumes, snapshots, IPs, secrets, and images and ending charges. - [Move an app between organizations](https://docs.fly.io/apps/move-app-org.md): Move an app to another Fly.io org with fly apps move or the dashboard. Expect brief downtime and reconfigure Upstash Redis, Tigris, and Postgres. #### Fly Launch - [Fly Launch](https://docs.fly.io/launch/index.md): Create, configure, deploy, and scale apps with Fly Launch on Fly.io using fly launch, fly.toml, fly deploy, and fly scale, plus autostop and GitHub Actions. - [Create an app with Fly Launch](https://docs.fly.io/launch/create.md): Create an app on Fly.io with fly launch: when it generates a Dockerfile, how framework scanners work, the --image and --dockerfile options, and next steps. - [Deploy an app](https://docs.fly.io/launch/deploy.md): Run fly deploy to build and release your app on Fly.io Machines. See how the image is chosen, deploy strategies, release commands and smoke checks. - [Scale Machine CPU and RAM](https://docs.fly.io/launch/scale-machine.md): Scale Machine CPU and RAM on Fly.io with the [[vm]] section in fly.toml, fly scale vm presets, fly scale memory, per process group, or fly machine update. - [Scale the Number of Machines](https://docs.fly.io/launch/scale-count.md): Scale a Fly.io app horizontally with fly scale count or by cloning and destroying Machines, across regions and process groups, apps with volumes, or to zero. - [Autostop/autostart Machines](https://docs.fly.io/launch/autostop-autostart.md): Let Fly Proxy stop, suspend and restart your Machines based on traffic on Fly.io. Configure auto_stop_machines, auto_start_machines and min_machines_running. - [Autoscale based on metrics](https://docs.fly.io/launch/autoscale-by-metric.md): Deploy fly-autoscaler to scale worker Machines on Prometheus queue depth or Temporal workflows, using FAS_ env vars and Expr Machine counts. - [Add volume storage to a Fly Launch app](https://docs.fly.io/launch/volume-storage.md): Attach Fly Volumes to a Fly Launch app: add [mounts] to fly.toml, create one volume per Machine and region, deploy, and verify with fly volumes list. - [Run multiple process groups in an app](https://docs.fly.io/launch/processes.md): Run several programs in one Fly.io app with process groups in fly.toml, attach services to a group, and scale each group with fly scale or fly machine clone. - [Continuous Deployment with Fly.io and GitHub Actions](https://docs.fly.io/launch/continuous-deployment-with-github-actions.md): Deploy to Fly.io automatically on every push with GitHub Actions: create a deploy token, store it as FLY_API_TOKEN, and add a workflow that runs flyctl deploy. - [Monorepo and multi-environment deployments](https://docs.fly.io/launch/monorepo.md): Deploy several apps from a monorepo on Fly.io: set the working directory, point fly deploy at a fly.toml with --config, a Dockerfile, and a --build-target. - [Troubleshoot apps when a host is unavailable](https://docs.fly.io/apps/trouble-host-unavailable.md): Recover apps on Fly.io when a host goes down: scale to zero and back up, redeploy, restore a volume from a snapshot, or rebuild a single-node Postgres app. - [App configuration (fly.toml)](https://docs.fly.io/reference/configuration.md): Configure a Fly.io app in fly.toml: build settings, deploy strategy, env vars, http_service and services, mounts, VM size, checks, processes, statics and files. #### Secrets - [Secrets and Fly Apps](https://docs.fly.io/apps/secrets.md): Set, stage, list and unset app secrets on Fly.io with fly secrets, see how the encrypted vault injects them as env variables, and mount secrets as files. - [Build Secrets](https://docs.fly.io/apps/build-secrets.md): Use secrets in a Docker build on Fly.io: mount them in a RUN step with --mount=type=secret, pass values with fly deploy --build-secret, and test locally. #### Production Apps - [Going to production checklist](https://docs.fly.io/apps/going-to-production.md): Production checklist for Fly.io apps: SSO, tokens, secrets, Managed Postgres, Machine sizing, multi-region scaling, custom domains, metrics, CI/CD. - [App Availability and Resiliency](https://docs.fly.io/apps/app-availability.md): Fly.io resiliency features, from two Machines per process group and standby Machines to health check routing, and what your app must handle itself. - [Tips to fine-tune your app on Fly.io](https://docs.fly.io/apps/fine-tune-apps.md): Benchmark an app on Fly.io: compare edge and app response metrics, check routing with debug.fly.dev, and factor in concurrency and autostop. - [App handover guide](https://docs.fly.io/apps/app-handover-guide.md): Hand an app to a client on Fly.io: build in their org from day one, or run fly apps move and rebuild Postgres, Upstash Redis, and Tigris by hand. - [Guidelines for concurrency settings](https://docs.fly.io/apps/concurrency.md): Set soft_limit, hard_limit, and connections vs requests concurrency in fly.toml, and see how Fly Proxy uses them for load balancing and autostop. ### Language & Framework Guides - [Language & Framework Guides](https://docs.fly.io/languages-and-frameworks/index.md): Every language guide for Fly.io: in-depth docs for Elixir, Rails, Laravel, Django, JS, Rust and Python, plus starters for Go, .NET, Crystal and WordPress. - [Deploy a Static Website](https://docs.fly.io/languages-and-frameworks/static.md): Deploy and host a static website on Fly.io. Serve your HTML, CSS, and JavaScript with nginx in a small Docker image and deploy it with flyctl. - [Deploy a .NET App](https://docs.fly.io/languages-and-frameworks/dotnet.md): Deploy a .NET app to Fly.io. Create an ASP.NET Core web app, configure it with fly launch, and deploy it to a Fly Machine with fly deploy. - [Deploy a Go App](https://docs.fly.io/languages-and-frameworks/golang.md): Deploy a Go app to Fly.io. fly launch detects Go, generates a Dockerfile and fly.toml for your web server, and deploys it to a Fly Machine. - [Deploy with a Dockerfile](https://docs.fly.io/languages-and-frameworks/dockerfile.md): Deploy an app from your own Dockerfile on Fly.io with fly launch, then add env vars to fly.toml, set secrets, and redeploy with fly deploy. - [Deploy a Crystal App](https://docs.fly.io/languages-and-frameworks/crystal.md): Deploy a Crystal app to Fly.io and connect it to Postgres. Configure the app with fly launch and ship it with fly deploy. - [Deploy WordPress](https://docs.fly.io/languages-and-frameworks/wordpress.md): Deploy WordPress to Fly.io using the official WordPress Docker image and a MySQL database, configured and launched with fly launch. - [Deploy a Ruby App](https://docs.fly.io/languages-and-frameworks/ruby.md): Deploy a Ruby app to Fly.io. Any Rack app with a Gemfile and config.ru, like Sinatra, can be launched with fly launch and shipped with fly deploy. #### Elixir - [Elixir on Fly.io](https://docs.fly.io/elixir/index.md): Deploy Phoenix and LiveView apps to Fly.io and cluster Elixir nodes across regions. Jump to getting started, the basics, or advanced BEAM guides. ##### Getting Started - [Deploy a Phoenix App](https://docs.fly.io/elixir/getting-started/index.md): Deploy an Elixir Phoenix app to Fly.io with Postgres. Generate the app, configure it with fly launch, and ship it with fly deploy. - [Migrate an Elixir App from Heroku](https://docs.fly.io/elixir/getting-started/migrate-from-heroku.md): Move a Phoenix app with Postgres, Oban and a custom domain from Heroku to Fly.io: fly launch, import secrets, copy the database, and a command cheat sheet. - [Deploy an Existing Elixir App](https://docs.fly.io/elixir/getting-started/existing.md): Move an existing Elixir or Phoenix app to Fly.io: launch with fly launch, attach Postgres, deploy, and troubleshoot your first release. ##### The Basics - [Elixir: The Basics](https://docs.fly.io/elixir/the-basics.md): Elixir basics on Fly.io: open an IEx shell into a running production app, cluster Erlang nodes into one distributed network, and troubleshoot deploys. - [IEx into Your Running App](https://docs.fly.io/elixir/the-basics/iex-into-running-app.md): Open an IEx shell into a running Elixir app on Fly.io with fly ssh console and the --pty flag, and wrap the command in a short shell script for quick access. - [Clustering Your Application](https://docs.fly.io/elixir/the-basics/clustering.md): Cluster Elixir nodes on Fly.io with dns_cluster and node names built from the app name and private IPv6 address, then scale across regions with a static cookie. - [Troubleshooting](https://docs.fly.io/elixir/the-basics/troubleshooting.md): Troubleshoot Elixir deploys on Fly.io: test releases and Docker builds locally, check IPv6 config, tune connection limits, and debug clustering. ##### Advanced guides - [Elixir: Advanced Guides](https://docs.fly.io/elixir/advanced-guides.md): Advanced Elixir on Fly.io: GitHub Actions CI/CD, Observer and Livebook against production, clustering from your laptop, and SQLite3 as a database. - [GitHub Actions for Elixir CI/CD](https://docs.fly.io/elixir/advanced-guides/github-actions-elixir-ci-cd.md): Set up a GitHub Actions CI workflow for an Elixir project with a Postgres service, dependency caching, and retries, then auto-deploy it to Fly.io. - [Connecting Observer to Your App in Production](https://docs.fly.io/elixir/advanced-guides/connect-observer-to-your-app.md): Run Erlang Observer locally and connect it to a production Elixir app on Fly.io over a WireGuard tunnel to inspect and kill processes, with a helper script. - [Connecting Livebook to Your App in Production](https://docs.fly.io/elixir/advanced-guides/connect-livebook-to-your-app.md): Connect a local Livebook to your production Elixir app on Fly.io over WireGuard, covering Elixir version requirements, the node name, and the shared cookie. - [Explore Your Production App with Livebook](https://docs.fly.io/elixir/advanced-guides/interesting-things-with-livebook.md): Use Livebook connected to your Elixir app on Fly.io for business intelligence, querying production data and charting it with VegaLite and Kino. - [Easy Clustering from Home to Fly.io](https://docs.fly.io/elixir/advanced-guides/clustering-from-home-to-your-app-in-fly.md): Cluster a local Elixir node with an Elixir app running on Fly.io over WireGuard, with cookie and IPv6 setup plus a bash script that automates the connection. - [Elixir: SQLite3](https://docs.fly.io/elixir/advanced-guides/sqlite3.md): Run a Phoenix app with SQLite3 on Fly.io by storing the database on a volume, running migrations on startup, and copying data over from Postgres or MySQL. #### Rails - [Rails on Fly.io](https://docs.fly.io/rails/index.md): Run Rails and Hotwire apps on Fly.io servers near your users. Start with the starter app, then The Basics for production and Advanced Guides for scale. ##### Getting Started - [Deploy a Rails App](https://docs.fly.io/rails/getting-started/index.md): Deploy a Rails app to Fly.io. Generate a new app, run fly launch to create a Dockerfile and fly.toml, and deploy it in a few minutes. - [Deploy an Existing Rails App](https://docs.fly.io/rails/getting-started/existing.md): Move an existing Rails app to Fly.io: provision Postgres and Redis, launch with fly launch, deploy, and troubleshoot common issues. - [Dockerfiles and fly.toml](https://docs.fly.io/rails/getting-started/dockerfiles.md): Fix common issues after fly launch on Rails: rerun bin/rails generate dockerfile, add packages, put SQLite on a volume, add swap, enable YJIT and caching. - [Experimental Fly Rails Gem](https://docs.fly.io/rails/getting-started/fly-rails.md): Deploy Rails to Fly.io with the experimental fly-rails gem: bin/rails fly:launch and fly:deploy, then eject to a fly.toml and Dockerfile for flyctl. ##### The Basics - [Rails: The Basics](https://docs.fly.io/rails/the-basics.md): Rails basics on Fly.io: credentials and secrets, deploys and migrations, Postgres, Redis for Turbo Streams, Tigris for Active Storage, Sidekiq, consoles. - [Environment Configuration](https://docs.fly.io/rails/the-basics/configuration.md): Configure a Rails app on Fly.io with secrets, non-sensitive env vars in fly.toml, and encrypted credentials files unlocked by setting RAILS_MASTER_KEY. - [Deployments](https://docs.fly.io/rails/the-basics/deployments.md): Deploy a Rails app to Fly.io with fly deploy, view release history, debug failed deploys with fly logs, and control how database migrations run on deploy. - [Active Record](https://docs.fly.io/rails/the-basics/active-record.md): Build a Rails app with a scaffolded Postgres table and deploy it to Fly.io with fly launch, which detects the app needs Postgres and provisions it. - [Active Storage](https://docs.fly.io/rails/the-basics/active-storage.md): Set up Rails Active Storage on Fly.io with a Tigris bucket, automatically through fly launch or with fly storage create and the dockerfile-rails generator. - [Turbo Streams & Action Cable](https://docs.fly.io/rails/the-basics/turbo-streams-and-action-cable.md): Deploy Rails Turbo Streams and Action Cable on Fly.io by creating an Upstash Redis database, setting REDIS_URL, and testing live updates across browsers. - [Sidekiq Background Workers](https://docs.fly.io/rails/the-basics/sidekiq.md): Run Sidekiq background workers for a Rails app on Fly.io as a separate process group in fly.toml, backed by Redis, and scale app and worker counts. - [Running Tasks & Consoles](https://docs.fly.io/rails/the-basics/run-tasks-and-consoles.md): Open a Rails console, an interactive shell, or run rake and custom Rails tasks on a production app on Fly.io using fly ssh console with the pty flag. ##### Advanced guides - [Rails: Advanced Guides](https://docs.fly.io/rails/advanced-guides.md): Advanced Rails on Fly.io: LiteFS, multiple Fly apps from one project, Phusion Passenger, multi-region deploys, AnyCable, the Machines API, and SQLite3. - [AnyCable](https://docs.fly.io/rails/advanced-guides/anycable.md): Replace Action Cable with AnyCable in a Rails app on Fly.io, adding anycable-go, nginx and foreman to the Dockerfile and running everything on one 512MB VM. - [Rails: Multiple Fly Applications](https://docs.fly.io/rails/advanced-guides/multiple-applications.md): Run extra services like Redis alongside a Rails project as separate Fly.io apps, each in its own subfolder with its own fly.toml, deployed on its own. - [LiteFS](https://docs.fly.io/rails/advanced-guides/litefs.md): Replicate a Rails app's SQLite database across regions with LiteFS on Fly.io, using the dockerfile-rails generator and fly machine clone to add a replica. - [Machine API](https://docs.fly.io/rails/advanced-guides/machine.md): Launch Fly Machines from a Rails Active Job using the fly.io-rails gem, running each background task on its own Machine and deleting it when it exits on Fly.io. - [Multi-region Deployments](https://docs.fly.io/rails/advanced-guides/multi-region.md): Run a Rails app in multiple regions on Fly.io, with pointers to the fly-ruby gem, global Redis for caching and Action Cable, and Postgres read replicas. - [Rails: SQLite3](https://docs.fly.io/rails/advanced-guides/sqlite3.md): Use SQLite3 as the database for a Rails app on Fly.io by creating a volume, mounting it in fly.toml, and pointing DATABASE_URL at a file on the volume. - [Phusion Passenger](https://docs.fly.io/rails/advanced-guides/phusion-passenger.md): Replace Puma with nginx and Phusion Passenger in a Rails app on Fly.io using the passenger-full Docker image, plus nginx site and environment variable config. ##### Cookbooks - [Cookbooks](https://docs.fly.io/rails/cookbooks/index.md): Rails Dockerfile cookbooks for Fly.io: minimal images, databases, Node.js and API-only apps, plus recipes for copying sources, faster builds and deploys. - [Minimal Rails application](https://docs.fly.io/rails/cookbooks/minimal.md): Write a minimal Rails Dockerfile and deploy it to Fly.io, then shrink the image from 948MB to 209MB by moving to ruby:slim and a multi-stage build. - [Rails with Databases](https://docs.fly.io/rails/cookbooks/databases.md): Add databases to a Rails Dockerfile on Fly.io: Upstash Redis for Action Cable, SQLite on a volume, then Postgres via fly postgres attach, or MySQL. - [Rails with Node.js](https://docs.fly.io/rails/cookbooks/node.md): Four ways to add Node.js to a Rails Docker image on Fly.io, NodeSource, merged images, Volta, or a node base image, compared by size, with an esbuild demo. - [Rails API-only Applications](https://docs.fly.io/rails/cookbooks/api.md): Deploy a Rails API-only app with a React client on Fly.io: a multi-stage Dockerfile builds the client into public/ and a controller serves JSON versions. - [Copy source](https://docs.fly.io/rails/cookbooks/sources.md): Copy a Rails project into a Docker image for Fly.io: pin Ruby, Bundler, Yarn and Node versions, add .dockerignore, set RAILS_MASTER_KEY, fix binstubs. - [Optimizing your build](https://docs.fly.io/rails/cookbooks/build.md): Speed up Rails Docker builds on Fly.io: copy Gemfile before source, run bundle and yarn installs in parallel stages, and reuse gems with a RUN cache mount. - [Optimizing your deployment](https://docs.fly.io/rails/cookbooks/deploy.md): Tune a deployed Rails app on Fly.io: preload jemalloc for memory allocation, turn on YJIT with RUBY_YJIT_ENABLE, and add swap using swap_size_mb. #### Laravel - [Laravel on Fly.io](https://docs.fly.io/laravel/index.md): Deploy a Laravel app to Fly.io with fly launch, which detects Laravel, offers Postgres, Redis and Tigris, and generates a Dockerfile, fly.toml and .fly/. ##### The Basics - [Laravel: The Basics](https://docs.fly.io/laravel/the-basics.md): Laravel basics on Fly.io: PHP and Node versions, custom deploys, stack trace logging, queues and the cron scheduler, a persistent storage folder, Tigris. - [PHP and Node Versions](https://docs.fly.io/laravel/the-basics/php-node-version.md): Set the PHP and Node.js versions for a Laravel app on Fly.io with build args in fly.toml or --build-arg flags on fly deploy, and see the default versions. - [Customizing Deployments](https://docs.fly.io/laravel/the-basics/customizing-deployments.md): Customize Laravel deployments on Fly.io with startup scripts in .fly/scripts and a release_command for migrations, and detect release runs with RELEASE_COMMAND. - [Post Deployment](https://docs.fly.io/laravel/the-basics/post-deployment.md): Manage a deployed Laravel app on Fly.io: open a shell with fly ssh console, view logs with fly logs or the dashboard, and keep log files on a volume. - [Logging Stack Traces](https://docs.fly.io/laravel/the-basics/logging-stack-traces.md): Get full stack traces in Laravel logs on Fly.io by adding includeStacktraces to the stderr channel's formatter_with settings in config/logging.php. - [Cron and Queues](https://docs.fly.io/laravel/the-basics/cron-and-queues.md): Run Laravel's scheduler and queue workers on Fly.io by adding cron and worker process groups to fly.toml alongside the app process that serves web traffic. - [Persisting the Storage Folder](https://docs.fly.io/laravel/the-basics/laravel-volume-storage.md): Persist the Laravel storage folder on Fly.io by creating a volume for each Machine, mounting it in fly.toml, and re-initializing the folder at startup. - [Tigris for CDN File Storage](https://docs.fly.io/laravel/the-basics/laravel-tigris-file-storage.md): Store Laravel files in a Tigris bucket on Fly.io: create it with fly storage create, map its credentials to the S3 driver, and serve public files. ##### Database guides - [Database guides](https://docs.fly.io/laravel/database-guides.md): Connect a Laravel app on Fly.io to MySQL, PostgreSQL, Redis or SQLite, and the different ways to run php artisan migrate on deploy. - [Laravel and MySQL](https://docs.fly.io/laravel/database-guides/laravel-mysql.md): Connect a Laravel app on Fly.io to MySQL running as a Fly app or on PlanetScale, using .internal addresses, secrets, and fly proxy for local access. - [Laravel and PostgreSQL](https://docs.fly.io/laravel/database-guides/laravel-pgsql.md): Connect a Laravel app on Fly.io to Postgres with fly postgres attach or manual setup, set DB_URL for Laravel 11, and connect from your local machine. - [Laravel and Redis](https://docs.fly.io/laravel/database-guides/laravel-redis.md): Connect a Laravel app on Fly.io to Redis, either a self-hosted Redis Fly app with a volume and password or Upstash Redis, from production and locally. - [Laravel and SQlite](https://docs.fly.io/laravel/database-guides/laravel-sqlite.md): Use SQLite as the database for a Laravel app on Fly.io: set DB_CONNECTION in fly.toml, keep the file on a volume, and look to LiteFS for multiple Machines. - [Laravel Database Migration](https://docs.fly.io/laravel/database-guides/laravel-db-migrations.md): Run php artisan migrate for a Laravel app on Fly.io four ways: a release_command in fly.toml, a startup script, or two fly ssh console methods. ##### Advanced guides - [Laravel: Advanced Guides](https://docs.fly.io/laravel/advanced-guides.md): Advanced Laravel on Fly.io: multiple Fly apps for Redis and other services, LiteFS for SQLite, GitHub Actions CI/CD, Symfony, Inertia SSR, Dockerfiles. - [Laravel: Multiple Fly Applications](https://docs.fly.io/laravel/advanced-guides/multiple-applications.md): Run a Redis server as a separate Fly.io app inside your Laravel project folder, with its own fly.toml, password secret, and volume, reached over .internal DNS. - [Laravel Multi-SQLite: LiteFS](https://docs.fly.io/laravel/advanced-guides/global-sqlite-litefs.md): Replicate a Laravel app's SQLite database across Fly.io Machines with LiteFS, including litefs.yml and FUSE setup and fly-replay middleware for writes. - [Laravel GitHub Actions: CICD](https://docs.fly.io/laravel/advanced-guides/github-actions.md): Auto-deploy a Laravel app to Fly.io from GitHub Actions: launch the app, push it to a GitHub repo, and add a deploy token and the flyctl-actions workflow. - [Using Symfony](https://docs.fly.io/laravel/advanced-guides/using-symfony.md): Deploy a Symfony app on Fly.io by letting fly launch treat it as Laravel, then disabling the .env requirement and trusting the Fly Proxy in Symfony config. - [Using Inertia SSR](https://docs.fly.io/laravel/advanced-guides/using-inertia-ssr.md): Deploy a Laravel Inertia app with server-side rendering on Fly.io by adding Node to the Dockerfile and running the SSR server as its own process group. - [Customizing the Dockerfile](https://docs.fly.io/laravel/advanced-guides/customizing-dockerfile.md): Customize the Laravel Dockerfile that fly launch generates on Fly.io, from skipping the static asset build to installing SQL Server PHP extensions before COPY. #### Django - [Django on Fly.io](https://docs.fly.io/django/index.md): Run Django on Fly.io: fly launch detects and deploys Django apps. Start with the starter app guide, move an existing project off Heroku, or go advanced. ##### Getting Started - [Deploy a Django App](https://docs.fly.io/django/getting-started/index.md): Deploy a Django app to Fly.io. Build a sample app, generate a Dockerfile with fly launch, serve it with Gunicorn, and add Postgres. - [Deploy an Existing Django App](https://docs.fly.io/django/getting-started/existing.md): Move an existing Django app to Fly.io: configure settings, launch with fly launch, attach Postgres, and troubleshoot your first deploy. ##### Advanced guides - [Django: Advanced Guides](https://docs.fly.io/django/advanced-guides.md): Advanced Django guides for Fly.io, currently covering staging environments: spin up a separate staging app for each change using GitHub Actions. - [Staging environments with GitHub actions](https://docs.fly.io/django/advanced-guides/staging-environments-with-github-actions.md): Create a Django staging environment for each pull request on Fly.io with GitHub Actions and fly-pr-review-apps, optionally using a staging Postgres cluster. #### Python - [Python on Fly.io](https://docs.fly.io/python/index.md): Run Python apps on Fly.io close to users worldwide. Start with the FastAPI speedrun, then use The Basics to set up and manage production Python apps. ##### The Basics - [Python: The Basics](https://docs.fly.io/python/the-basics.md): Python basics on Fly.io: install flyctl and run fly launch, set up a local Python environment with poetry, and shrink images with multi-stage builds. - [Setting up a Python Environment](https://docs.fly.io/python/the-basics/initial-setup.md): Set up a local Python environment with Poetry and virtual environments before deploying to Fly.io, with uv, pip, Pipenv and pyenv listed as alternatives. - [Multi-stage Builds](https://docs.fly.io/python/the-basics/multi-stage-builds.md): Write a multi-stage Dockerfile for Python apps on Fly.io that builds dependencies with Poetry in a full image and copies them into a slim runtime image. ##### Python Framework Guides - [Python Framework Guides](https://docs.fly.io/python/frameworks.md): Python framework guides for Fly.io, each deploying a simple app: FastAPI for type-hinted APIs, Flask for WSGI web apps, and Streamlit for data apps. - [Deploy a FastAPI App](https://docs.fly.io/python/frameworks/fastapi.md): Deploy a FastAPI app to Fly.io. fly launch detects FastAPI, generates a Dockerfile and fly.toml, and deploys your Python API to a Fly Machine. - [Deploy a Flask App](https://docs.fly.io/python/frameworks/flask.md): Deploy a Flask app to Fly.io. fly launch detects Flask, generates a Dockerfile that serves it with Gunicorn, and deploys it to a Fly Machine. - [Deploy a Streamlit App](https://docs.fly.io/python/frameworks/streamlit.md): Deploy a Streamlit app to Fly.io. fly launch detects Streamlit, generates a Dockerfile and fly.toml, and deploys your data app to a Fly Machine. ##### Do More - [Do More](https://docs.fly.io/python/do-more.md): Extend a Python app on Fly.io with extra services: attach and connect a Postgres database, add S3-compatible object storage, and run Ollama behind an API. - [Add Postgres](https://docs.fly.io/python/do-more/add-postgres.md): Connect a Python app on Fly.io to Fly Postgres with a DATABASE_URL secret, query it with asyncpg, and run a local Postgres in Docker for development. - [Add Object Storage](https://docs.fly.io/python/do-more/add-object-storage.md): Add S3-compatible object storage to a Python app on Fly.io: create a Tigris bucket with flyctl, then list and use buckets from your code with boto3. - [Add Ollama](https://docs.fly.io/python/do-more/add-ollama.md): Connect a Python app on Fly.io to an Ollama server over Flycast, set OLLAMA_HOST as a secret, and generate llama3.1 responses with the ollama AsyncClient. #### Javascript - [JavaScript on Fly.io](https://docs.fly.io/js/index.md): Run JavaScript apps on Fly.io: start with the Node.js starter app, then use The Basics for production setup, and get help from the community forum. - [Deploy a Shopify App](https://docs.fly.io/js/shopify.md): Deploy and host a Shopify app on Fly.io. fly launch reads your Shopify app config, sets secrets and env vars, and deploys it in one command. ##### The Basics - [JavaScript: The Basics](https://docs.fly.io/js/the-basics.md): JavaScript basics on Fly.io for Express, Fastify and Node apps: Dockerfiles, dependencies, databases, volumes, Tigris storage, ports, secrets, scaling. - [Dockerfiles](https://docs.fly.io/js/the-basics/dockerfiles.md): Deploy Node.js, Bun, and Deno apps on Fly.io with a Dockerfile, either your own or one generated by fly launch and adjusted with dockerfile-node options. - [Dependencies](https://docs.fly.io/js/the-basics/dependencies.md): Fix Node.js and Bun dependency problems when deploying to Fly.io, including missing, miscategorized, legacy peer, and native npm modules, using dockerfile-node. - [Databases](https://docs.fly.io/js/the-basics/database.md): Connect a JavaScript app on Fly.io to a database through DATABASE_URL with Prisma, Drizzle, Knex, pg, sqlite3, or MongoDB, plus SSL and migration advice. - [JavaScript: Volumes](https://docs.fly.io/js/the-basics/volumes.md): Persist files and SQLite data for a JavaScript app on Fly.io by creating a volume for each Machine, mounting it in fly.toml, and writing to the mount path. - [Object Storage](https://docs.fly.io/js/the-basics/object-storage.md): Add Tigris S3-compatible object storage to a JavaScript app on Fly.io with fly storage create, then access the bucket from S3Client with no extra configuration. - [Listening Ports](https://docs.fly.io/js/the-basics/listening-ports.md): Make a Node.js app reachable on Fly.io by matching internal_port in fly.toml to your app port, listening on 0.0.0.0, and adding services for extra ports. - [Secrets](https://docs.fly.io/js/the-basics/secrets.md): Set production secrets for a JavaScript app on Fly.io with fly secrets set or by importing a dotenv file, then read them via process.env, Deno.env, or Bun.env. - [Scaling](https://docs.fly.io/js/the-basics/scaling.md): Scale a JavaScript app on Fly.io by choosing memory and swap, using the Node.js cluster module for multiple CPU cores, and adding more Machines. ##### JS Framework Guides - [JS Framework Guides](https://docs.fly.io/js/frameworks.md): Deploy guides for JavaScript frameworks on Fly.io: Astro, Deno, Meteor, Next.js, Nuxt, RedwoodJS, Remix and SvelteKit, each building a simple app. - [Deploy an Astro App](https://docs.fly.io/js/frameworks/astro.md): Deploy an Astro app to Fly.io, static or SSR. fly launch detects Astro, generates a Dockerfile and fly.toml, and deploys it in a few commands. - [Deploy a Deno App](https://docs.fly.io/js/frameworks/deno.md): Deploy a Deno app to Fly.io. Package a Deno server in a Docker image, configure it with fly launch, and deploy it to a Fly Machine. - [Deploy a Meteor App](https://docs.fly.io/js/frameworks/meteor.md): Deploy a Meteor app to Fly.io. fly launch detects Meteor, generates a Dockerfile and fly.toml, and deploys your app to a Fly Machine. - [Deploy a Next.js App](https://docs.fly.io/js/frameworks/nextjs.md): Deploy a Next.js app to Fly.io. fly launch detects Next.js and generates a Dockerfile and fly.toml, with standalone builds for smaller images. - [Deploy a Nuxt App](https://docs.fly.io/js/frameworks/nuxtjs.md): Deploy a Nuxt app to Fly.io. fly launch generates a Dockerfile and fly.toml for your Nuxt project and deploys it to a Fly Machine. - [Deploy a RedwoodJS App](https://docs.fly.io/js/frameworks/redwood.md): Deploy a RedwoodJS app to Fly.io. fly launch generates a Dockerfile and fly.toml for your Redwood project and deploys it to a Fly Machine. - [Deploy a Remix App](https://docs.fly.io/js/frameworks/remix.md): Deploy a Remix app to Fly.io. fly launch detects Remix, generates a Dockerfile and fly.toml, and deploys your app to a Fly Machine. - [Deploy a SvelteKit App](https://docs.fly.io/js/frameworks/svelte.md): Deploy a SvelteKit app to Fly.io. fly launch generates a Dockerfile and fly.toml for your SvelteKit project and deploys it to a Fly Machine. ##### Prisma - [Prisma](https://docs.fly.io/js/prisma/index.md): Pick a database for a Prisma app on Fly.io. Compares SQLite and PostgreSQL for scaling, recommends starting with Postgres, and links setup for each. - [Sqlite](https://docs.fly.io/js/prisma/sqlite.md): What fly launch sets up for Prisma with SQLite on Fly.io: an auto-extending volume, migrations at boot, Litestream backups to Tigris, and a setup script. - [Prisma with PostgreSQL](https://docs.fly.io/js/prisma/postgres.md): Deploy a Prisma app with PostgreSQL on Fly.io: release_command runs prisma migrate deploy, seeds run at launch, and pgloader converts an old SQLite DB. #### Rust - [Rust on Fly.io](https://docs.fly.io/rust/index.md): Launch Rust apps on Fly.io servers around the world. Begin with the Axum speedrun, then The Basics for setting up and running production Rust apps. ##### The Basics - [Rust: The Basics](https://docs.fly.io/rust/the-basics.md): Rust basics on Fly.io: install the toolchain with rustup, install flyctl and log in, then deploy most Rust frameworks with a single fly launch. - [Cargo Chef](https://docs.fly.io/rust/the-basics/cargo-chef.md): Build Rust apps for Fly.io with a cargo-chef Dockerfile that caches dependency builds in a separate layer and ships the binary in a slim Debian runtime image. ##### Rust Framework Guides - [Rust Framework Guides](https://docs.fly.io/rust/frameworks.md): Rust framework guides for Fly.io, each deploying a simple app: Axum, Actix Web, Warp, Rocket, Poem, and Dioxus LiveView over WebSockets. - [Deploy an Axum App](https://docs.fly.io/rust/frameworks/axum.md): Deploy an Axum app to Fly.io. Clone our Axum template or serve your own Router on port 8080, and fly launch generates a cargo-chef Dockerfile. - [Deploy an Actix Web App](https://docs.fly.io/rust/frameworks/actix-web.md): Deploy an Actix Web app to Fly.io. Clone our template or bind your own HttpServer to 0.0.0.0:8080, then fly launch builds it with cargo-chef. - [Deploy a Warp App](https://docs.fly.io/rust/frameworks/warp.md): Deploy a Warp server to Fly.io. Clone our Warp template or create one with cargo new, serve it on port 8080, and ship it with fly launch and cargo-chef. - [Deploy a Rocket App](https://docs.fly.io/rust/frameworks/rocket.md): Deploy a Rocket app to Fly.io. Clone our Rocket template or build a new app with cargo, and fly launch creates a cargo-chef Dockerfile for small images. - [Deploy a Poem App](https://docs.fly.io/rust/frameworks/poem.md): Deploy a Poem web app to Fly.io. Start from our Poem template or a new cargo project, listen on 0.0.0.0:8080, and fly launch handles the Dockerfile. - [Deploy a Dioxus Liveview App](https://docs.fly.io/rust/frameworks/dioxus-liveview.md): Deploy a Dioxus Liveview app to Fly.io. Serve server-rendered Rust UI over WebSockets with Axum, then fly launch builds and ships it to a Fly Machine. ### Fly Machines - [Fly Machines](https://docs.fly.io/machines/index.md): Start here for Fly Machines, fast-launching VMs on Fly.io. Find the Machines introduction, the REST API, and flyctl commands for running and updating Machines. - [An introduction to Fly Machines](https://docs.fly.io/machines/overview.md): Get to know Fly Machines, the fast-launching VMs behind Fly.io: run one with fly machine run, follow the lifecycle, scale by clone or update, and pick regions. #### Machines API - [Machines API](https://docs.fly.io/machines/api/index.md): Manage apps, Machines, volumes, certificates and tokens with the Fly.io Machines REST API. Find each resource reference, the OpenAPI spec and the fly-go client. - [Working with the Machines API](https://docs.fly.io/machines/api/working-with-machines-api.md): Connect to the Fly Machines API on Fly.io: choose the public or internal base URL, authenticate with a bearer token, and review response codes and rate limits. - [Apps](https://docs.fly.io/machines/api/apps-resource.md): Machines API Apps resource: create, get, list by org_slug, and delete Fly Apps, plus allocating IPs, setting secrets, and isolated app networks. - [Certificates](https://docs.fly.io/machines/api/certificates-resource.md): Manage custom domain certificates via the Machines API: request ACME certs, import PEM certs, check DNS validation, and delete certificates. - [Machines](https://docs.fly.io/machines/api/machines-resource.md): Create, list, update, stop, suspend, start, and delete Machines on Fly.io with the Machines API, plus leases, metadata, wait states, and config properties. - [Tokens](https://docs.fly.io/machines/api/tokens-resource.md): Request an OpenID Connect token for a Fly Machine with POST /v1/tokens/oidc in the Machines API, setting the aud claim to get a signed JWT. - [Volumes](https://docs.fly.io/machines/api/volumes-resource.md): Volumes endpoints in the Machines API: list, create, update, extend, and delete Fly Volumes, list snapshots, restore from one, or snapshot on demand. #### Machines and flyctl - [Run a new Machine](https://docs.fly.io/machines/flyctl/fly-machine-run.md): Run a new Fly Machine on Fly.io with fly machine run: build or pull an image, pick a region, set resources, env vars and services, or open a temporary shell. - [Update a Machine](https://docs.fly.io/machines/flyctl/fly-machine-update.md): Update an existing Fly Machine with fly machine update to change its image, CMD, resources, services, env vars, mounts, files or standby status on Fly.io. #### Guides and Examples - [Machines Guides and Examples](https://docs.fly.io/machines/guides-examples.md): Browse guides and examples for Fly Machines, the fast-launching VMs on Fly.io, and find practical ways to put Machines to work in your own projects. - [Run Machines with flyctl](https://docs.fly.io/machines/guides-examples/machines-app-using-flyctl.md) - [Managing Machines with the Machines API](https://docs.fly.io/machines/guides-examples/managing-machines-with-the-api.md): Machines API patterns: clone a Machine's config, set fly_process_group metadata so flyctl manages it, define services, and sync autostop/autostart. - [Machine Placement and Regional Capacity](https://docs.fly.io/machines/guides-examples/machine-placement.md): Avoid failed scaling when a Fly.io region is out of capacity: give fly machine clone a prioritized region list or aliases like us, eu, and apac. - [Machine restart policy](https://docs.fly.io/machines/guides-examples/machine-restart-policy.md): Compare no, always, and on-fail Machine restart policies, check one with fly m status -d, and change it via fly m update, the API, or fly.toml. - [Machine Sizing](https://docs.fly.io/machines/guides-examples/machine-sizing.md): Size Fly Machines on Fly.io with CPU and memory presets or custom values via the Machines API or fly machine run, see the memory limits, and resize later. - [Multi-container Machines](https://docs.fly.io/machines/guides-examples/multi-container-machines.md): Run sidecars in one Fly.io Machine with Pilot and the containers array, set dependencies and health checks, and deploy with Docker Compose, the API, or flyctl. - [Network Policies](https://docs.fly.io/machines/guides-examples/network-policies.md): Restrict Fly Machine ingress and egress with network policies in the Machines API, selecting by app, Machine ID, or metadata with port allow rules. - [Run User Code on Fly Machines](https://docs.fly.io/machines/guides-examples/functions-with-machines.md): Build functions-as-a-service on Fly Machines: create an isolated app, launch user-code Machines in any region via the API, then stop or delete them. - [One App Per Customer - Why?](https://docs.fly.io/machines/guides-examples/one-app-per-user-why.md): Why Fly.io recommends one app per customer: per-app secrets, load balancing, and scaling, plus isolated networks that can still talk via Flycast. #### Reference - [Machine states and lifecycle](https://docs.fly.io/machines/machine-states.md): Fly Machine lifecycle states, from created, started, and suspended to replaced and migrated, plus version behavior and how to spot stuck Machines. - [The Machine Runtime Environment](https://docs.fly.io/machines/runtime-environment.md): See the environment variables Fly.io sets in a Machine, like FLY_APP_NAME, FLY_REGION, FLY_MACHINE_ID, FLY_PRIVATE_IP, and FLY_IMAGE_REF, and what each holds. - [CPU Performance](https://docs.fly.io/machines/cpu-performance.md): Compare shared and performance vCPUs on Fly.io Machines, how CPU quotas and throttling are enforced, how shared CPUs burst, and which metrics show throttling. ### Managed Postgres - [Managed Postgres](https://docs.fly.io/postgres/index.md): Get an overview of Fly.io Managed Postgres: backups, high availability, pgvector and PostGIS, storage, regions, features in development, and plan pricing. #### Getting Started - [Create and Connect to a Managed Postgres Cluster](https://docs.fly.io/postgres/create-and-connect.md): Create a Managed Postgres cluster with fly mpg create or the dashboard, attach an app with fly mpg attach, and connect locally via mpg proxy or WireGuard. - [Connect Your Client](https://docs.fly.io/postgres/client-configuration.md): Tune clients for Fly.io Managed Postgres: pooled vs direct URLs, 600s connection lifetime, PgBouncer transaction mode, and pool settings per language. - [Cluster configuration options](https://docs.fly.io/postgres/cluster-configuration.md): Set PgBouncer to Session or Transaction pool mode, change your MPG plan, and add databases and users with Schema Admin, Writer, or Reader roles. #### Guides and Examples - [Phoenix with Managed Postgres](https://docs.fly.io/postgres/guides-examples/phoenix-guide.md): Run Phoenix on Fly.io Managed Postgres: PgBouncer Transaction mode with prepare: :unnamed, Ecto migrations on the direct URL, and Oban notifier options. #### Management - [Monitoring and Metrics](https://docs.fly.io/postgres/metrics.md): The Managed Postgres Metrics tab: connection and pooler tiles, CPU and memory charts, cache hit ratio, deadlocks, replication lag, and v2 Overview tiles. - [Maintenance windows](https://docs.fly.io/postgres/maintenance-windows.md): Choose when Fly.io runs routine maintenance on your Managed Postgres cluster, and what to expect when it does. - [Import data from another postgres cluster](https://docs.fly.io/postgres/import.md): Import data into Fly.io Managed Postgres from Fly Postgres or another provider using pg_dump and psql over fly mpg proxy, plus size limits and pgloader. - [Supported Postgres Extensions](https://docs.fly.io/postgres/extensions.md): Fly.io Managed Postgres runs Postgres 16 and 17. Enable extensions per database, including pgvector and PostGIS, and check the bundled extension list. ### Databases & Storage - [Databases and storage](https://docs.fly.io/database-storage-guides.md): Pick a data option on Fly.io: Managed Postgres, Upstash for Redis, Fly Volumes for persistent NVMe disk, Tigris object storage, or an external provider. - [Fly Postgres (Unmanaged)](https://docs.fly.io/unmanaged-postgres/index.md) - [Tigris Global Object Storage](https://docs.fly.io/tigris/index.md): Create S3-compatible Tigris object storage buckets on Fly.io with fly storage create, connect via the endpoint, CLI or SDKs, and migrate from another provider. - [Upstash for RedisĀ®*](https://docs.fly.io/upstash/redis.md): Create and manage Upstash Redis databases on Fly.io with flyctl redis, add read replicas, configure eviction, and compare pay-as-you-go and fixed price plans. - [Upstash Vector](https://docs.fly.io/upstash/vector.md): Upstash Vector on Fly.io, in public beta in iad and fra: create, list, check, and destroy indexes with flyctl ext vector, reachable over private IPv6. ### Fly Volumes - [Fly Volumes](https://docs.fly.io/volumes/index.md): Fly Volumes docs index: how NVMe volumes work, adding them to Fly Launch apps, managing them with flyctl, snapshots, states, and the Volumes API. - [Fly Volumes overview](https://docs.fly.io/volumes/overview.md): Understand Fly Volumes, local NVMe storage for Fly.io Machines: one per Machine, placement, encryption, sizing, IOPS limits, forks, snapshots and redundancy. - [Create and manage volumes](https://docs.fly.io/volumes/volume-manage.md): Create, extend, fork, and destroy Fly Volumes with fly volumes on Fly.io, attach volumes by cloning Machines, and restore deleted volumes from snapshots. - [Manage volume snapshots](https://docs.fly.io/volumes/snapshots.md): Manage Fly Volume snapshots: set 1 to 60 day retention, create one with fly volumes snapshots create, restore to a new volume, or disable them. - [Volume states](https://docs.fly.io/volumes/volume-states.md): Every Fly Volume state, from creating and hydrating to pending_destroy, the transitions for each action, and how long soft-deleted volumes last. ### Networking - [Networking](https://docs.fly.io/networking/index.md): Fly.io networking docs: Anycast public services, 6PN private networking, Flycast, egress IPs, fly-replay routing, custom domains, UDP, and TLS. - [Connect to an App Service](https://docs.fly.io/networking/app-services.md): Reach a process on a Fly Machine via Fly Proxy or 6PN: which address to bind, when services and IPs are needed, and curl checks for each path. - [Public Network Services](https://docs.fly.io/networking/services.md): Set up public networking for a Fly.io app: Anycast IPv6, shared and dedicated IPv4, HTTP, TLS and PROXY protocol handlers, HTTPS redirects and outbound IPs. - [Private Networking](https://docs.fly.io/networking/private-networking.md): Connect apps over the private 6PN network on Fly.io using .internal DNS, and link your laptop or outside services to it with a WireGuard VPN from flyctl. - [Custom private networks](https://docs.fly.io/networking/custom-private-networks.md): Isolate tenants on custom 6PNs with fly apps create --network, connect them via Flycast or fly-replay, and read network IDs from IPv6 addresses. - [Flycast - Private Fly Proxy services](https://docs.fly.io/networking/flycast.md): Route private app traffic through Fly Proxy with Flycast on Fly.io: launch with fly launch --flycast, allocate a private IPv6, and reach apps from other orgs. - [Egress IP addresses](https://docs.fly.io/networking/egress-ips.md): Allocate static egress IPs on Fly.io for third-party allowlists, with per-region app-scoped IPv4 and IPv6 pairs and their caveats. - [Dynamic Request Routing with fly-replay](https://docs.fly.io/networking/dynamic-request-routing.md): Route requests on Fly.io between regions, Machines, or apps with the fly-replay response header, including JSON replays, replay caching, and fly-force-region. - [Custom domains](https://docs.fly.io/networking/custom-domain.md): Point your own domain at a Fly.io app with fly certs add, set A, AAAA or CNAME records, validate the TLS certificate, and fix Cloudflare certificate issues. - [Understanding Cloudflare](https://docs.fly.io/networking/understanding-cloudflare.md): Use Cloudflare with Fly.io in DNS-only or orange cloud proxy mode, get certs via a _fly-ownership TXT record or Origin Certificate, and fix common issues. - [Request headers](https://docs.fly.io/networking/request-headers.md): Read the request headers your app gets on Fly.io, like Fly-Client-IP, Fly-Region, X-Forwarded-For, X-Forwarded-Proto, and Via, with spoofing cautions. - [WebSockets](https://docs.fly.io/networking/websockets.md): Run WebSocket apps on Fly.io. Fly Proxy keeps idle connections open, and closes them cleanly with code 1012 when it restarts or when autostop stops a Machine. - [Running apps on UDP and TCP](https://docs.fly.io/networking/udp-and-tcp.md): Run UDP and TCP apps on Fly.io: get a dedicated IPv4, bind UDP to fly-global-services on the same external port, don't assume a fixed MTU or per-flow load balancing, note QUIC isn't supported, and try a Go echo app. - [TLS Support](https://docs.fly.io/networking/tls.md): Fly Proxy accepts only TLSv1.2 and TLSv1.3. See the AES-GCM and ChaCha20-Poly1305 cipher suites it supports for each, plus SSL Labs results. ### Monitoring - [Monitoring on Fly.io](https://docs.fly.io/monitoring/index.md): Fly.io monitoring docs: managed Prometheus and Grafana metrics, Sentry error tracking, and guides to live tail, log search, the logs API, and export. - [Logging overview](https://docs.fly.io/monitoring/logging-overview.md): See how Fly.io app logs flow from stdout through Vector and NATS, then live tail with fly logs, use the Logs API, search logs in Grafana, or export them. - [Metrics on Fly.io](https://docs.fly.io/monitoring/metrics.md): Monitor apps with managed Prometheus and Grafana on Fly.io: query built-in proxy, instance, volume and Postgres metrics, add alerts, and expose custom metrics. - [Application Monitoring by Sentry](https://docs.fly.io/monitoring/sentry.md): Access existing Sentry projects provisioned through Fly.io, open the dashboard with fly ext sentry, and see what happens when the one-year Team plan ends. #### Logging - [Live tail logs](https://docs.fly.io/monitoring/live-tail-logs.md): Tail Fly App logs live with fly logs, filter by Machine with --instance, turn on LOG_LEVEL=debug for flyctl, or use the dashboard Live Logs page. - [Logs API options for programmatic access](https://docs.fly.io/monitoring/logs-api-options.md): Fetch Fly.io app logs in code through the HTTP API behind fly logs, a NATS subscription for real-time streams, or the Fly Log Shipper to an external sink. - [Search logs](https://docs.fly.io/monitoring/search-logs.md): Search Fly App logs in Grafana, backed by VictoriaLogs with 7-day retention and LogsQL queries. Log search is in beta and free during the beta. - [Export logs](https://docs.fly.io/monitoring/exporting-logs.md): Export logs from Fly.io apps to Datadog, S3, Logtail and other services with the Fly Log Shipper, a Vector-based app you can filter by app or region. - [Error codes and troubleshooting](https://docs.fly.io/monitoring/error-codes.md): Look up Fly Proxy error codes like PC01, PT05, PM03, PR01, and PA03 from your app logs, grouped by connection, TLS, Machine, and routing. ### Security - [Security](https://docs.fly.io/security/index.md): Fly.io security docs: org roles, SSO, member offboarding, TLS termination, Arcjet, access tokens, OpenID Connect, and shared responsibility. - [Organization Roles and Permissions](https://docs.fly.io/security/org-roles-permissions.md): Member vs Admin roles in a Fly.io organization, and how to limit risk by splitting dev and prod into separate orgs and using read-only tokens. - [Single sign-on for organizations](https://docs.fly.io/security/sso.md): Require Google Workspace or GitHub single sign-on for a Fly.io organization from the dashboard, and how org SSO differs from user login. - [Remove a member from your organization](https://docs.fly.io/security/remove-org-member.md): Offboard a user from a Fly.io org: remove them in the dashboard, delete WireGuard peers, revoke tokens, unset secrets, and rotate passwords. - [TLS termination by Fly Proxy](https://docs.fly.io/security/tls-termination.md): Fly Proxy terminates TLS on port 443 using Let's Encrypt or imported certificates. Remove the tls handler to terminate TLS in your own app. - [Application Security by Arcjet](https://docs.fly.io/security/arcjet.md): Add Arcjet rate limiting, bot protection, and email validation to a Fly.io app with fly ext arcjet create, then the Node.js or Python FastAPI SDK. - [Access tokens](https://docs.fly.io/security/tokens.md): Create Fly.io access tokens scoped to one app or org, including SSH, machine-exec and read-only tokens, then set expiry, list and revoke them with fly tokens. - [OpenID Connect](https://docs.fly.io/security/openid-connect.md): Use OpenID Connect on Fly.io to give Machines short-lived tokens for AWS, Azure, or GCP, customize the aud claim, and write an AWS trust policy to read S3. - [Shared responsibility model](https://docs.fly.io/security/shared-responsibility.md): Fly.io's shared responsibility model: what Fly secures, like workers, edges, and Fly Proxy, versus what you own in your image, tokens, and SSO. - [Fly.io security practices and compliance](https://docs.fly.io/security/security-at-fly-io.md): See how Fly.io handles corporate, infrastructure, and application security, its vulnerability remediation timeframes, SOC2 Type 2, and how to report issues. ### About - [About Fly.io](https://docs.fly.io/about/index.md): The About section of the Fly.io docs: pricing, billing, cost management, the free trial, support, healthcare controls, open source, brand, and legal terms. - [Discontinued Plans](https://docs.fly.io/about/discontinued-plans.md): Fly.io stopped selling Hobby, Launch, and Scale plans on October 7, 2024. See the legacy allowances still honored, pro-rated billing, and Pay As You Go. - [Fly.io Resource Pricing](https://docs.fly.io/about/pricing.md): See what Fly.io bills for, from Machines and volumes to Managed Postgres, data transfer, IPs, SSL, support plans and extensions, with sample app costs. - [Fly.io Billing](https://docs.fly.io/about/billing.md): Understand how Fly.io bills each organization monthly: Machine, volume and snapshot charges, invoices, unified billing, payment options, and account deletion. - [Cost Management on Fly.io](https://docs.fly.io/about/cost-management.md): Predict your Fly.io bill: budget for always-on Machines, watch bandwidth, volumes, IPv4 and leftover managed services, and know free allowances don't cap it. - [Fly.io Free Trial](https://docs.fly.io/about/free-trial.md): Check what the Fly.io free trial includes, the $1 credit and its limits, how to track your balance, and what happens when the credit runs out. - [Free Waiver for Bills Under $5](https://docs.fly.io/about/free-waiver.md): Learn how Fly.io waives monthly bills under $5, who qualifies, what usage counts toward it, and how it works with the $1 free trial. - [Support](https://docs.fly.io/about/support.md): Get help with Fly.io through the community forum, billing email, paid email support and Support Portal, and see what to include in a ticket and what's in scope. - [Healthcare apps on Fly](https://docs.fly.io/about/healthcare.md): See how Fly.io supports healthcare apps: SOC2 Type 2 audits, BAA signing, WireGuard encryption in transit, encrypted volumes at rest, 6PN private networking. - [Fly.io Extensions Program](https://docs.fly.io/about/extensions.md): Partner with Fly.io as an extension provider: requirements for account and resource provisioning, SSO via flyctl ext, usage billing APIs, and hosting. - [Provisioning Fly.io Extensions](https://docs.fly.io/reference/extensions_api.md): Spec for Fly.io extension partners: signed provisioning requests, Flycast private access, OAuth SSO, resource webhooks, and billing. - [Fly.io Merchandise](https://docs.fly.io/about/merch.md): Where to buy Fly.io merch: T-shirts, hoodies, stickers, and mugs with Frankie the balloon, sold through the Redbubble shop, and who to email for help. - [Fly.io and Open Source](https://docs.fly.io/about/open-source.md): How Fly.io supports the open source it depends on: equity grants to authors of projects like isolated-vm and acme-client, plus recurring sponsorships. - [Using Our Brand](https://docs.fly.io/about/brand.md): Download Fly.io logos in color and monochrome landscape, portrait, and brandmark formats, and review the trademark usage agreement for using them. #### Jobs - [Join Our Team](https://docs.fly.io/hiring/index.md): Work at Fly.io: the Go, Rust, Elixir, and Ruby stack, open roles, challenge-based hiring, and the countries where we hire. - [Our Hiring Process](https://docs.fly.io/hiring/hiring.md): No interviews, no resumes: Fly.io hires engineers through untimed at-home work-sample challenges and a typed Slack chat. Covers start dates and pay. - [How To Ask Us Questions](https://docs.fly.io/hiring/questions.md): Questions count in Fly.io hiring. Examples of yes/no, decision-offloading, and spec-assuming questions, and how to rewrite each to get useful answers. - [Working at Fly.io](https://docs.fly.io/hiring/working.md): What working at Fly.io is like: where we hire, visa sponsorship, small teams with bottom-up decisions, a shared on-call rotation, and open source work. - [Our Levels](https://docs.fly.io/hiring/levels.md): Fly.io's company-wide career levels, IC1 to IC6 and M1 to Senior Director: what each level owns and how leveling, performance and promotion work. ### LiteFS #### Get Started with LiteFS - [LiteFS - Distributed SQLite](https://docs.fly.io/litefs/index.md): Replicate SQLite across nodes with LiteFS, a distributed file system, on Fly.io or with Docker. Find the getting started guides and the no-support warning. - [Speedrun: Add LiteFS to your app](https://docs.fly.io/litefs/speedrun.md): Add LiteFS to a Dockerized app on Fly.io fast: copy the sample litefs.yml, install fuse3, create a volume, run fly consul attach, deploy, clone regions. - [Getting Started with LiteFS on Fly.io](https://docs.fly.io/litefs/getting-started-fly.md): Set up a LiteFS cluster on Fly.io: install litefs, configure litefs.yml with a volume, Consul lease, and proxy, then run litefs mount and import a database. - [Getting Started with LiteFS in Docker](https://docs.fly.io/litefs/getting-started-docker.md): Run a LiteFS cluster in Docker: install fuse3, copy the flyio/litefs binary, set a static lease in litefs.yml, use --privileged, route writes via nginx. - [How LiteFS Works](https://docs.fly.io/litefs/how-it-works.md): LiteFS intercepts SQLite journal and WAL writes over FUSE, packs page sets into LTX files, tracks TXID positions, and elects a primary with Consul leases. - [LiteFS FAQ](https://docs.fly.io/litefs/faq.md): LiteFS answers on database size limits, FUSE write throughput near 100 tx/sec, async replication, write downtime on deploys, and LiteFS vs Litestream. #### Using LiteFS - [LiteFS Releases](https://docs.fly.io/litefs/releases.md): Download prebuilt LiteFS binaries for amd64 or arm64 from GitHub releases when running on a Linux VPS without Docker or skipping the LiteFS Docker image. - [Built-in HTTP Proxy](https://docs.fly.io/litefs/proxy.md): The LiteFS HTTP proxy on Fly.io forwards writes to the primary via fly-replay and holds replica reads until a TXID cookie catches up. No WebSocket support. - [Running database migrations](https://docs.fly.io/litefs/migrations.md): Run migrations on LiteFS with lease.promote auto-promotion and if-candidate exec commands, or forward writes from any node with -with-halt-lock-on. - [Backing up your LiteFS cluster](https://docs.fly.io/litefs/backup.md): Back up a LiteFS cluster with litefs export, gzip, and rolling S3 copies, or stream continuously to Tigris with Litestream for point-in-time restore. - [Determining the LiteFS primary](https://docs.fly.io/litefs/primary.md): Read the .primary file in the LiteFS mount to get the primary's hostname, decide when to forward writes, and see why replicas return SQLITE_READONLY. - [Tracking LiteFS replication position](https://docs.fly.io/litefs/position.md): Read a database's -pos file for its LiteFS replication position, a hex TXID plus rolling checksum, and use it or a delay for read-your-writes consistency. - [Reading the LiteFS event stream](https://docs.fly.io/litefs/events.md): Stream real-time LiteFS events from GET /events on port 20202 as newline-delimited JSON, including the init, tx, and primaryChange types and their fields. - [Using LiteFS Cloud for Backups](https://docs.fly.io/litefs/cloud-backups.md): LiteFS Cloud was retired in October 2024, so this is kept for reference. Covers creating a cluster, upgrading to v0.5.0, and setting LITEFS_CLOUD_TOKEN. - [Restoring from a LiteFS Cloud Backup](https://docs.fly.io/litefs/cloud-restore.md): Archived: LiteFS Cloud was retired in 2024. Restoring a database to any point in the past 30 days at 5-minute granularity, and why a write was needed. - [Disaster Recovery from LiteFS Cloud](https://docs.fly.io/litefs/disaster-recovery.md): Deprecated LiteFS Cloud guide to rebuilding a lost cluster: run only the primary, fix the clusterid file, clear the Consul key conflict, re-clone replicas. #### LiteFS Reference - [LiteFS Export Command](https://docs.fly.io/litefs/export.md): The litefs export command downloads a SQLite database from a local or remote LiteFS node with the -name and -url flags. It is safe on a live database. - [LiteFS Import Command](https://docs.fly.io/litefs/import.md): Upload a SQLite file to a LiteFS cluster with litefs import -name, creating or replacing it on a local or remote node. Run PRAGMA integrity_check first. - [LiteFS Mount Command](https://docs.fly.io/litefs/mount.md): litefs mount starts the FUSE mount and joins the cluster. Covers the -config and -no-expand-env flags plus -fuse.debug and -tracing for verbose debug logs. - [LiteFS Run Command](https://docs.fly.io/litefs/run.md): litefs run executes the command after the double dash, with -promote to make the node primary, -if-candidate, and -with-halt-lock-on for write forwarding. - [LiteFS Config Reference](https://docs.fly.io/litefs/config.md): Reference for each litefs.yml section: fuse and data dirs, exec, HTTP API port 20202, proxy, Consul or static leases, env var expansion, and trace logging.