Documentation
Everything you need to go from an empty account to a production deploy.
Quickstart
Install the CLI, paste an API key from the console, link your folder and deploy. Your site goes live at <project>.cirrusforge.cloud in seconds.
Core concepts
- Organization — your team, billing and members.
- Project — one site, with its own URL, deployments and variables.
- Deployment — an uploaded version of your site. The active one is what visitors see.
- Resources — PostgreSQL databases and storage buckets shared by your organization.
Deploying
Build your site, then run cirrusforge deploy with the output folder, or drag the folder into the project in the console. The new deployment goes live as soon as the upload finishes.
To roll back, open the project, choose a previous deployment and select Promote.
GitHub & previews
Open your project in the console → GitHub. Save an API key as the CIRRUSFORGE_TOKEN secret in your repository and add the workflow file it gives you. From then on, every push is built by GitHub Actions and deployed: pushes to your production branch (main by default) go live, and every other branch gets a preview at <project>--<branch>.cirrusforge.cloud. Each branch keeps its newest preview, and previews aren’t indexed by search engines.
Variables & secrets
Variables are scoped per environment (Production, Staging, Preview, Development). Mark a value as secret to encrypt it and make it write-only — it can be replaced, never read back. cirrusforge env pull writes the non-secret values to .env.local for your build.
Databases
Open Databases in the console, choose a name and a region, and your PostgreSQL 17 database is ready in seconds. Copy the connection string, or add it to a project as DATABASE_URL with one click. You can restore a database to any moment in the last 6 hours from its page. On the Free plan, databases hold up to 500 MB, pause after 7 days without use (turn them back on with one click) and are deleted after 30 days paused.