Documentation
Ship the app. Keep everything it needs beside it.
A Fortly project is your app with its own PostgreSQL database, files, domains and schedules. Run it from the console or the HTTP API, and give an AI agent read-only access through MCP.
Start here
QuickstartCreate a project, deploy your code, and open it at its own address in a few minutes.Core conceptsProjects, releases, the database, files and domains — what each one is and how they fit.
Build with Fortly
DeployUpload an archive or link a GitHub branch. Fortly builds it and puts each release live.DatabaseEvery project has its own PostgreSQL, with an API for your server and one for your frontend.FilesUploads served from your project's own address, straight from storage.DomainsPoint your own domain at a project, prove it is yours, and serve it over HTTPS.SchedulesCall a path on your project on a cron timer, in UTC.SecretsEnvironment values, encrypted at rest, for your build, your running app, or both.
Drive it from anywhere
Everything the console does, it does over the same HTTP API you can call — there is nothing it can do that you cannot. Pick whichever fits the moment.
Terminal
export FORTLY_TOKEN=fly_...
curl https://api.fortly.com/projects \
-H "Authorization: Bearer $FORTLY_TOKEN"Terminal
# Claude Code: add Fortly, then run /mcp and sign in
claude mcp add --transport http fortly https://api.fortly.com/mcpOpen console.fortly.com, choose New project, and follow its first release. Every screen there is a view over the API above.
API referenceEvery route, its parameters and what it returns.Connect an AI agentGive Claude Code, Cursor or any MCP client read-only access to your projects, releases and logs.