Develop
Compose on the canvas, then deploy. A service is the unit of work — Git, Docker, cron, or a database.
On the canvas
Section titled “On the canvas”ServicesGit repos, Docker images, templates, cron, and databases as tiles.
VariablesService config, secrets, and database-linked values.
EnvironmentsProduction, custom environments, and pull-request previews.
Staged changesReview canvas edits, then deploy.
Deploy from GitHubConnect a repo and auto-deploy on push.
DockerBuild from a Dockerfile or run a registry image.
ImportCompose, render.yaml, and fly.toml onto the canvas.
Cron jobsScheduled runs on standard cron syntax.
Public HTTPGive a service a public URL and TLS.
Private servicesAlways-on processes with no public domain.
Static sitesBuild assets and serve them as a service.
Deployments
Section titled “Deployments”Auto deploy on pushEvery push to the deploy branch triggers a build.
PR previewsA live environment for every pull request.
Deploy hooksTrigger a redeploy from CI or an external system.
RollbacksRevert to a previous successful deployment.
MonorepoRoot directories for multiple services in one repo.
Scaling
Section titled “Scaling”Horizontal scalingReplica counts across instances.
AutoscalingScale from CPU or memory thresholds.
Memory & CPU limitsInstance sizes and what happens at the cap.
Zero-downtime deploysRolling updates that wait for health checks.
Health checksReadiness probes so traffic only hits healthy instances.