The developer cloud

Ship it.
We’ll run it.

Sites, databases, storage and secrets in one calm console. Push a branch — get a live URL in seconds.

console.cirrusforge.cloud / projects
WorkspaceOverviewProjectsStorageDatabases Developer toolsAPI KeysVariablesLogsMonitoring
ProjectsNew project
EnglishAIenglishai.cirrusforge.cloud2 min agoLive
Payments docspayments-docs.cirrusforge.cloud1 h agoLive
Portfoliodaniel.cirrusforge.cloudyesterdayLive
Landing v2landing-v2.cirrusforge.cloudjust nowDeploying
Event inviteboda-ana.cirrusforge.cloud3 days agoLive

Everything your app needs.
Nothing it doesn’t.

Four building blocks that work together from the first deploy.

Sites

A live URL in seconds.

  • Push to GitHub: your main branch goes live, every other branch gets a preview URL
  • Served from Cloudflare’s global network — scales with your traffic on its own
  • Or deploy from the CLI or the console — rolling back is one click
EnglishAILive
URLenglishai.cirrusforge.cloud
Deploymente48d2f6 conversational AI tutor
Files148 files · 3.2 MB
Deployed2 min ago by Daniel
Previewenglishai--feat-ai-tutor.cirrusforge.cloud

From commit to customers
in three steps.

1

Connect GitHub

Copy one workflow file into your repo. It builds with GitHub Actions — free for most projects.

.github/workflows/cirrusforge.yml
2

Push a branch

Every branch gets its own preview URL your team can open right away.

git push origin feat/ai-tutor
3

Merge to ship

Merging to main makes it live. Every deploy is kept, so rollback is one click.

✓ Live at englishai.cirrusforge.cloud

Security

Private by default.
Not as an upgrade.

The protections teams usually bolt on later are on from your first deploy.

Write-only secrets

Encrypted at rest. Once saved, a secret can be replaced — never read back.

STRIPE_SECRET_KEY••••••••

Two-step sign-in

Codes from an authenticator app, recovery codes, and sign-in with Google or GitHub.

Two-step verificationon

Roles and activity log

Owner, Admin, Developer and Viewer roles, and a log of every change your team makes.

Viewerread only

Simple pricing.
Start free.

Every plan includes HTTPS, GitHub deploys, branch previews, logs, monitoring and the CLI.

Free

For side projects and learning.
$0
  • 3 projects and 3 members
  • 1 GB of storage
  • 1 PostgreSQL database (500 MB)
Start for free
Currently not available

Pro

For freelancers and growing sites.
$10per month
  • 20 projects and 10 members
  • 10 GB of storage
  • 3 PostgreSQL databases
Currently not available
Currently not available

Team

For teams shipping every day.
$25per month
  • Unlimited projects and members
  • 50 GB of storage
  • 10 PostgreSQL databases
Currently not available

Paid plans are currently not available. Start free today, or talk to us ›

Your next deploy
could be your first.

No credit card required.

CirrusForge›Documentation

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.

# 1. Install (Node.js 18 or newer) npm install -g https://cirrusforge.cloud/cli.tgz # 2. Sign in with an API key (Console → API Keys) cirrusforge login # 3. Link this folder and deploy cirrusforge link my-site cirrusforge deploy dist

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.

cirrusforge env set OPENAI_API_KEY=sk-... --secret cirrusforge env ls

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.

CirrusForge CLI

Deploy sites, manage variables and tail logs without leaving your terminal. No dependencies — just Node.js 18+.

Install

npm install -g https://cirrusforge.cloud/cli.tgz cirrusforge --version

Sign in

Create a key in Console → API Keys, then run cirrusforge login and paste it. The key is saved in ~/.cirrusforge.json. In CI, set CIRRUSFORGE_TOKEN instead.

Commands

CommandWhat it does
cirrusforge loginSave an API key on this computer.
cirrusforge whoamiShow the account and organization the key belongs to.
cirrusforge projectsList projects and their URLs. projects create <name> makes a new one.
cirrusforge link <project>Connect the current folder to a project.
cirrusforge deploy [dir]Upload a folder with an index.html and make it live (--branch makes a preview). Finds dist/, build/, out/ or public/ on its own. -m adds a message.
cirrusforge env ls / set / rm / pullManage variables. set KEY=value --secret encrypts it; pull writes non-secret values to .env.local.
cirrusforge logs [-f]Recent requests to your site; -f keeps streaming. --status 4xx filters.
cirrusforge openOpen the linked site in your browser.

Deploy from GitHub Actions

The console (project → GitHub) gives you the full workflow. In GitHub Actions the CLI detects the branch on its own: the production branch goes live, other branches become previews. Use --branch or --prod to choose yourself.

- run: npm ci && npm run build - run: npx -y https://cirrusforge.cloud/cli.tgz deploy dist --project my-site env: CIRRUSFORGE_TOKEN: ${{ secrets.CIRRUSFORGE_TOKEN }}
CirrusForge›Docs›API reference

API reference

A REST API over HTTPS with JSON responses. Authenticate with an API key from the console.

Authentication

Send your key in the Authorization header. Base URL: https://console.cirrusforge.cloud/api. A key only works for the organization it was created in, and a read-only key can't change anything.

curl https://console.cirrusforge.cloud/api/me \ -H "Authorization: Bearer $CIRRUSFORGE_TOKEN"

Errors come back as {"error": "message"} with a 4xx or 5xx status.

Endpoints

MethodPathDescription
GET/meThe account and organization the key belongs to.
GET/orgs/{org}/projectsList projects.
POST/orgs/{org}/projectsCreate a project. Body: {"name"}.
GET/projects/{id}Project details and deployments.
POST/projects/{id}/deploymentsDeploy. Multipart form: path:N + file:N for each file, optional message.
GET/projects/{id}/variablesList variables (secret values are never returned).
POST/projects/{id}/variablesCreate a variable. Body: {"key","value","secret","envs"}.
PATCH/variables/{id}Update a variable.
DELETE/variables/{id}Delete a variable.
GET/projects/{id}/logsRequests to the site. Query: status=4xx, q, after, before, limit.
GET/projects/{id}/metricsTraffic, errors and response times. range=24h|7d.
GET/orgs/{org}/bucketsList storage buckets.
POST/buckets/{id}/objectsUpload files (multipart, same format as deployments).
GET/buckets/{id}/objects/{key}Download a file.
CirrusForge›Status

System status

Checking our systems…

Every 5 minutes we check the website and console, the API, the database and site hosting. Each bar is one day; hover it to see that day’s uptime.

CirrusForge›About

Infrastructure should get out of the way.

CirrusForge is a developer cloud for people and teams who would rather ship than maintain servers.

What we believe

Every project deserves a live URL, every secret deserves encryption, and every team deserves to know what its cloud costs.

What we build

One console for sites, PostgreSQL, storage and secrets — with a CLI and an API.

Our story

CirrusForge started with a simple frustration: putting a website online shouldn’t take a credit card from another country, three dashboards and a weekend of YAML. We wanted the calm of the big platforms without the complexity, built for people who just want to ship. So we built it — one console for sites, databases, storage and secrets, running on a global network. Every feature has to earn its place.

Get in touch

Questions, ideas or partnerships — we read every message.

Contact us ›
CirrusForge›Careers

Careers

We’re a small team, and we’re not looking for new people at the moment.

We’re not hiring right now. If you’d like to hear when that changes, write to us ›

CirrusForge›Contact

Talk to us.

Questions about Enterprise, migrations or pricing — tell us what you’re building.

CirrusForge›Security

Security at CirrusForge

How we protect your code, your data and your customers’ data.

Encryption

All traffic uses TLS. Data at rest — databases, storage and secrets — is encrypted. Secret variables are write-only.

Accounts

Passwords are stored as salted hashes. Members can turn on two-step verification with an authenticator app and sign in with Google or GitHub. Sign-in attempts are rate-limited and protected by a check against bots.

Access control

Role-based access (Owner, Admin, Developer, Viewer), API keys that can be read-only, and an activity log of every change.

Infrastructure

CirrusForge runs on Cloudflare’s global network, which maintains independent security certifications for its infrastructure. CirrusForge itself has not completed an independent audit yet.

Reporting a vulnerability

Write to security@cirrusforge.cloud with the details. Please give us reasonable time to fix the issue before sharing it publicly. We will not take legal action against good-faith research that respects our users’ privacy and data.

CirrusForge›Privacy

Privacy Policy

Effective November 16, 2026

This policy explains what information CirrusForge (“we”, “us”) collects when you use cirrusforge.cloud, console.cirrusforge.cloud and the sites we host, how we use it, and the choices you have. We keep it short because we collect very little.

1. Information we collect

  • Account information: your name, email address and organization name. Your password is never stored — only a salted PBKDF2-SHA-256 hash of it.
  • Content you provide: projects, the files you deploy, and environment variables. Variables are encrypted with AES-256-GCM before they are stored; values marked as sensitive can never be read back, not even by you.
  • Team information: the email addresses you invite and the roles you assign.
  • Security data: to stop abuse we keep short-lived, one-way hashed records of failed sign-in attempts (by email and IP address) for up to 15 minutes, and single-use verification challenges for up to 5 minutes.
  • Activity log: actions inside your organization (for example “deployed”, “invited”) with the member who did them and the time.

We do not use advertising trackers or third-party analytics, and we do not sell personal information.

2. How we use information

  • To create and secure your account and keep you signed in.
  • To store, publish and serve the sites you deploy.
  • To let the members of your organization collaborate.
  • To protect the service against fraud, spam and attacks.
  • To contact you about your account or important changes to the service.

3. Service providers

CirrusForge runs on Cloudflare (Workers, D1 and KV), which processes data on our behalf to host the service and deliver your sites through its global network. We also use Resend to send emails and Neon to run the databases you create. Fonts are served from our own servers. These providers only receive what they need to perform their service.

4. Retention

We keep your account data while your account exists. Deleting a project removes its deployments and variables. Sessions expire after 12 hours, or after 30 days if you choose “Keep me signed in”. Health-check records for the status page are kept for 90 days.

5. Your rights

You can access and update your name and password in the console at any time. To request a copy of your data, its correction or the deletion of your account, email privacy@cirrusforge.cloud from the address on your account. We answer within 30 days.

6. Security

All traffic uses HTTPS. Session cookies are HttpOnly, Secure and limited to console.cirrusforge.cloud, so the sites people publish on CirrusForge cannot read them. No method of storage or transmission is 100% secure, but we work to protect your information.

7. Children

CirrusForge is not directed to children under 16, and we do not knowingly collect their information.

8. Changes

If we change this policy we will update the date above, and notify account owners by email for significant changes.

9. Contact

Questions: privacy@cirrusforge.cloud

CirrusForge›Terms

Terms of Service

Effective November 16, 2026

These terms govern your use of CirrusForge, including cirrusforge.cloud, console.cirrusforge.cloud, our API and the sites we host for you. By creating an account you agree to them.

1. Your account

You must give accurate information, keep your password safe and be at least 16 years old. You are responsible for activity in your account and in the organizations you manage. Tell us right away at security@cirrusforge.cloud if you believe your account was compromised.

2. Your content

You keep all rights to the files, projects and data you upload. You give us permission to store, copy and serve that content only as needed to run the service — for example, to publish your site at its URL. You are responsible for having the rights to everything you publish.

3. Acceptable use

You may not use CirrusForge to:

  • publish illegal content, malware, or phishing pages, or impersonate other people or organizations;
  • infringe intellectual property or privacy rights;
  • send spam, attack other systems, or try to break, overload or get around the security of the service;
  • resell the service or create accounts automatically to avoid limits.

We may remove content or suspend accounts that break these rules, and will tell you why when we reasonably can.

4. Plans and limits

The Free plan is free and has usage limits. Paid plans, when available, will be billed in advance for the period you choose and are not refundable except where required by law. We will announce price changes at least 30 days before they apply.

5. Availability

We work to keep CirrusForge available and publish its health at status, but the service is provided “as is” and may occasionally be interrupted for maintenance or reasons outside our control. Keep your own copies of anything important.

6. Ending your use

You can stop using CirrusForge and delete your projects at any time. We may suspend or close accounts that break these terms or put the service or other users at risk.

7. Liability

To the maximum extent permitted by law, CirrusForge is not liable for indirect or consequential damages or lost profits, and our total liability for any claim is limited to the amount you paid us in the 12 months before it.

8. Changes

We may update these terms. If a change is significant we will notify account owners by email before it takes effect. Continuing to use the service means you accept the updated terms.

9. Contact

Questions about these terms: legal@cirrusforge.cloud

CirrusForge›Cookies

Cookie Policy

Effective November 16, 2026

CirrusForge uses as little browser storage as possible, and none of it is used for advertising or tracking.

Essential cookie

  • __Host-cf_session (console.cirrusforge.cloud) — keeps you signed in. It is HttpOnly and Secure. It lasts until you close the browser, or 30 days if you choose “Keep me signed in”.

Local storage

  • cf_org — remembers which organization you last opened in the console.

Third parties

Our fonts (Inter and JetBrains Mono) are served from our own servers, so no third party receives your IP address when you visit us. Cloudflare, which protects our network, may set a short-lived security cookie (__cf_bm) to tell people apart from bots; it is strictly necessary and contains no personal profile. We do not use analytics or advertising cookies, so there is nothing to opt out of. You can delete cookies at any time in your browser settings; you will just need to sign in again.