Going to production

This document lists important topics to consider when you set up a production environment on Fly.io. What makes an app production-ready can vary from one framework to another. The following topics and linked resources can help you understand when and why you might need specific features or configuration.

Security

• Set up single sign-on for organizations: Enable SSO on your organization to take advantage of Google or GitHub authentication security. See Single sign-on for organizations.

• Use Arcjet application security for JavaScript apps: Secure your app with rate limiting, bot protection, email validation, and defense against common attacks through our extension partner Arcjet. Currently free in beta, but pricing is subject to change. See Application Security by Arcjet.

• Protect sensitive information: Set secrets to store sensitive data and make them available as environment variables to your app. See Secrets and Fly Apps.

• Make sure private services are not exposed: Check that your private apps with services don’t have public IP addresses. Run fly ips list and use fly ips release to release unnecessary public IPs. See flyctl fly ips commands.

• Isolate staging and production environments: Use organizations to limit access to your production environment. See Blueprint: Staging and production isolation.

Databases

• Run “production-grade” Postgres: For Fly Postgres, our unmanaged database, set up replication clusters of 3+ servers. See High Availability & Global Replication. You can also use an external database provider and configure it for redundancy.

• Set up offsite backups: Consider offsite backups for your database.

• LiteFS with LiteFS Cloud: LiteFS is a distributed file system that transparently replicates SQLite databases. LiteFS Cloud is a Fly.io product which provides backups and recovery for your LiteFS SQLite database. See the LiteFS docs.

Monitoring

• Export your logs: Set up the Fly Log Shipper to aggregate your app’s logs to a service of your choice. See Export logs.

• Use Sentry for Error tracking: An application monitoring platform that helps you identify and fix software problems before they impact your users from our extension partner Sentry.Fly.io organizations get a year’s worth of Team Plan credits. See Application Monitoring by Sentry.

Availability and resiliency

• Use multiple Machines for resiliency: Make your app resilient to single-host failures with multiple Machines that stay stopped until you need them. See Blueprint: Resilient apps use multiple Machines.

• Set up autoscaling by load or metric: Use Fly Proxy autostart/autostop or the metrics-based autoscaler app. See Autoscaling.

CI/CD

• Deploy with GitHub Actions: Set up your app for continuous deployment to Fly.io from the app’s GitHub repository. See Continuous Deployment with Fly.io and GitHub Actions.

• Generate review apps with GitHub Actions: Automatically generate ephemeral review apps on Fly.io for each pull request (PR) using GitHub Actions. See Blueprint: Git Branch Preview Environments on GitHub.

Networking

• Set up a custom domain: Configure a certificate for your domain. See Use a custom domain.

• Consider a dedicated IPv4 address: Completely eliminate the chance of blacklisted spammers causing problems for your app. There is a small added cost for dedicated IPv4 addresses. See Dedicated IPv4.

Fine-tuning your app

• Get Machine sizing right: Most production apps require 2x or performance CPUs. Also make sure you have enough RAM for your app and/or enable swapping to disk to deal with brief spikes in memory use. See Machine sizing.

• Fine-tune and benchmark your app: Learn about optimizing your app on Fly.io. See Tips to fine-tune and (not) benchmark your app on Fly.io.

Support

Check out our community to get help and answers.

Get email support with a Launch, Scale, or Enterprise plan.