Plans and prices

Every request our edge passes to an app in your workspace, whoever sent it. That means signed-in people, bypass tokens, anonymous visitors to a public path and webhook deliveries. Requests to the dashboard and the API don't count. We also rate-limit anonymous requests to a public path, per client.

On Team and Business the count starts again each billing month. That month starts on the day you subscribe, and it's the month each invoice covers. On Free the count starts again each calendar month, in UTC. The Billing tab shows this month's count, and it's the same count your invoice uses.

CPU time is the time your Worker apps' own code spends running, as Cloudflare records it for each request. Public paths and webhooks count too. Time spent waiting on a fetch or a database doesn't. Container apps and static sites aren't charged for CPU time. The code in front of them is ours, and your plan covers a container's computing.

Each billing month includes 100,000,000 ms on Team and 400,000,000 ms on Business, then $0.041 per million ms. Free stops for the month at 50,000,000 ms, and its apps then answer 402 until the month ends or you upgrade.

Each plan also limits the CPU time of a single request to a Worker app: 50 ms on Free, 100 ms on Team and 150 ms on Business. Cloudflare enforces it loosely: a request may run past it, even to a few seconds, or be stopped there, so keep requests under it. The limits page says what happens to a request that's stopped. A request that runs over is still counted in full, and on Team and Business charged like any other.

Anonymous requests to a public path count like any other, so a flood of them would cost you something. Three things keep it small. Each client is rate-limited on each public path. Your usage limit stops your apps once usage charges reach it. By default the limit is $0, so nothing beyond the plan's price is charged unless an owner sets another amount, or none, on the Billing tab. Usage is measured a little after it happens, so some can run past the limit before the apps stop, and that usage is on us. And we email the owners along the way: at 80% and 100% of each allowance, as usage charges pass $10, the plan's price and each multiple of it, and at 80% and 100% of the usage limit.

Its apps keep running up to twice the allowance, 200,000 requests in a calendar month. After that they answer 402 until the month ends or you upgrade. An upgrade takes effect straight away. We email the owners when the workspace passes the allowance, and again if its apps stop.

Only requests served on Free count. When a workspace moves to Free after a cancellation, a downgrade or a failed payment, it counts from the hour the change takes effect. What it served on the paid plan doesn't count. For a cancellation or a downgrade, the change takes effect when the paid month ends. For a failed payment, it's the end of the two weeks of retries. Starting a checkout and leaving it unfinished changes nothing.

Team and Business don't stop at their request allowance. Requests past it are metered at $3.78 per million and added to that month's invoice, up to the workspace's usage limit.

Any app that isn't a JavaScript Worker or a static site: a Python, Go, Rust or Node server, with or without a Dockerfile. It runs in a container behind the same edge. Team runs one container app, with one container at the lite or basic size. basic has a quarter of a vCPU and 1 GiB of memory.

Business runs four container apps, and gives them 40 container units to share. A container uses 4 units at lite, 10 at basic and 24 at standard-1, which has half a vCPU and 4 GiB of memory. An app can run up to four containers, and each request goes to one of them. So Business runs four basic apps, or one app on four basic containers, or a standard-1 app beside smaller ones. Enterprise contracts run more and bigger, up to standard-4 with 4 vCPUs and 12 GiB of memory. Write to us if you need that.

Free runs JS, TypeScript and static apps only. If a workspace moves to Free, its container apps stop answering until it's on a paid plan again, and so do apps with key-value storage or a queue. Until then the edge returns 402 with a page saying the app needs a paid plan.

The files your sites serve, the files your apps keep, what they keep in key-value storage, and their databases. We measure apps' files every five minutes and each database about once an hour. If a workspace goes over its storage, nothing new deploys until it's back under. Once any app keeps files of its own, every app with a place for files also answers 507 to everyone, owners and admins included, until there's room, since nothing else would stop it writing more. Delete files with forculus files rm, delete rows, or move to a bigger plan. If the workspace stays over because of its apps' files, we delete those files after 7 days on Free and 30 on Team and Business, with an email to the owners a week before. We don't if the workspace would still be over without them.

Cloudflare counts rows for each of your apps' databases. A query counts every row it reads, including rows it scans but doesn't return, and every row and index entry it writes. Queries made while serving public paths count, and so do database exports and forculus db commands.

Free stops for the month at 50,000,000 database rows read or 100,000 written. For that cut-off we use the lowest figure Cloudflare reports, so a Free workspace is never stopped early. If we can't measure a Free workspace's rows for two hours, its apps with a database answer 402 until we can.

Team includes 500,000,000 rows read and 500,000 written each billing month, and Business ten times that. Past those, rows read cost $2.50 per billion and rows written $2.25 per million. Invoices only use Cloudflare's exact figures, never an estimate.

All of a workspace's databases share one limit. It's 1 GB on Free, 2 GB on Team and 10 GB on Business. We measure them every few minutes and email the owners at 80%.

Over the limit, apps with a database answer only the workspace's owners and admins, so they can delete rows through the app. Everyone else gets 507, including bypass tokens, public paths and webhooks, and nothing new deploys. If the databases keep growing, or reach 10% over, those apps answer no one. Apps without a database keep answering throughout.

To get back under, delete rows through the app or with forculus db exec, export and remove data, or upgrade. On Team and Business, storage over the limit costs $1.55 per GB-month, charged by the hour for as long as it lasts. On Free, a workspace still over after 7 days is suspended. 30 days later we delete its largest databases until it's under, and we email 7 days and 1 day before we do.

No. You pay per workspace, and each plan includes a set number of members. One person can be in several workspaces on different plans.

On the workspace's Billing tab. The dialog tells you exactly what will happen before you confirm.

An upgrade takes effect as soon as it's paid for, and starts a new billing month. The next answer explains how it's charged.

A downgrade takes effect at your renewal, when the month you've paid for ends. Until then you keep the higher plan, the Billing tab shows the day it moves, such as "Team from 28 October", and you can undo it. The renewal invoice is at the new price. You can't downgrade while the workspace uses more than the lower plan allows in container apps, their sizes, containers or units, or database data. The message tells you what to delete first.

If the new plan keeps less of the audit log, older events are deleted 30 days after the change, so export first.

You start a new billing month on the new plan straight away, at its full price, and every allowance starts again. You get a credit for the unused time on the old plan, unless you've used the old plan's allowances much faster than the month has gone by. The dialog tells you which before you confirm. The old plan's usage so far is invoiced with the upgrade, at the old plan's prices. CPU time from about the last two hours before the upgrade, and database storage over the limit in the current hour, count in the new month, because we measure them later.

In Stripe's customer portal, which you open from the Billing tab. You also update cards and find invoices there. A cancellation takes effect when the month you've paid for ends. The workspace then goes back to Free: container apps and apps with key-value storage or a queue stop, Postgres connections and log drains turn off, and everything else keeps running within Free's limits. Free keeps 3 months of the audit log, and older events are deleted 30 days after the change, so export first. The refund policy covers the rest of a month you've paid for.

If a payment fails, we retry for up to two weeks, and Stripe emails you each time. After that the workspace moves to Free: container apps and apps with key-value storage or a queue stop, Postgres connections and log drains turn off, and everything else keeps running within Free's limits. We email the owners three days before the move, and again when it happens. Pay the invoice and the plan comes back.

Each container image push counts against two daily budgets, one for the workspace and one for the person pushing. A workspace can push 20 GB a day on Team and 100 GB on Business. On any plan, each person can push 20 GB a day. Both are rolling, so a push counts for 24 hours. If a push would go over either budget, it's refused until older pushes age out. The image you already deployed keeps running.

You can't create anything that would take you over a limit, like a new app, member or token. The message says which limit and which plan lifts it, for example "Team allows 25 apps". Everything you already have keeps running. Storage, the database limit and Free's monthly CPU time and database rows are different: past them, apps can stop answering, as the answers above say.

A few limits affect running apps. If a workspace's databases hold more than its plan allows, its apps with a database answer 507 to everyone except owners and admins. If a workspace stores more than its plan allows and any of its apps keeps files, every app with a place for files answers 507 to everyone until there's room. A Free workspace that uses 50,000,000 ms of CPU time, reads 50,000,000 database rows or writes 100,000 in a month has its apps paused until the next month.

No plan allows more than 10 public paths per app. The edge keeps each app's public paths in memory between requests, and more wouldn't fit.

Yes, on every plan. A workspace owner can export the workspace from its Settings page. You get one JSON file with its configuration, members, sharing, the audit log your plan keeps, and the names of its tokens, secrets and environment variables. It never includes a value. An owner can also export an app's database as SQL from the app's page in the dashboard, or with forculus db export. A static site is the files you uploaded.

A deleted app or workspace is kept for 30 days, with its data, and an owner can restore it until then. It isn't billed and doesn't count toward your plan while it's kept. After the 30 days, or when you delete it for good, deletion is immediate and permanent, so export first. Nothing is kept while anyone who owns what you delete has yet to accept our terms: see when deletion is immediate. An app's scripts, databases and containers are removed from Cloudflare right away, along with its configuration, versions, sharing, tokens, secrets and environment variables. Its files go right away too, up to 5,000 of them. An app with more has the rest deleted over the following minutes, and in any case within two days. Its entries in the workspace's audit log stay for your plan's audit retention, like every other entry.

Deleting a workspace deletes its apps the same way. Once it's deleted for good, we keep our own records of the workspace for 30 days for accounting, but you can't restore anything. Deleting a workspace on a paid plan cancels its subscription at once, with no refund for the rest of the month, and a restored one comes back on Free. The confirmation dialog says so.

While the law requires us to keep a workspace's data, you can't delete the workspace or its apps. See section 10 of the terms.

On Team and Business, in Stripe's customer portal, which you open from the Billing tab. Stripe issues and keeps every invoice and receipt. On Enterprise, the Billing tab lists the invoices Stripe sent for your contract, each with a link to read, download and pay it.

On Enterprise. We set up a contract with you, invoiced monthly or yearly, with up to 120 days to pay each invoice. Team and Business are monthly, paid by card through Stripe. Email sales@forculuslabs.tech.

Tell us about the project at support@forculuslabs.tech.