Three plans. One door.

Every request the edge admits to an app in your workspace for a signed-in person or a bypass token. Requests to the dashboard and the API don't count, and public-path traffic isn't counted either: anonymous requests to a public path are rate-limited per client instead of counted against you.

On Team and Business the allowance is per billing period: the month that starts on the day you subscribe and renews on the same day each month, which is the period each invoice covers. The count starts again with each period. On Free it is the calendar month, in UTC. The workspace's Billing tab shows the count for the current period: the same requests the invoice is worked out from.

Its apps keep running until the workspace reaches twice the allowance: 200,000 requests in a calendar month. After that the edge answers 402 for the workspace's apps until the month ends, or until you upgrade, which takes effect immediately. The platform emails the workspace's owners when it passes the allowance, and again if its apps stop. The count is of requests served while the workspace was on Free, so a workspace that has just come onto Free (after a cancellation, a downgrade or a failed payment) counts from the hour the change takes effect, whatever it served on the plan before. For a cancellation or a downgrade that is the end of the paid period; for a failed payment, the end of the two weeks of retries. Starting a checkout and leaving it unfinished changes nothing. Team and Business workspaces are never cut off; requests past the allowance are metered at $3.50 per million and added to the invoice for that billing period.

Anything 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 and Business four, each at the lite or basic size (up to a quarter of a vCPU and 1 GB of memory); write to us for more. Container apps need Team or Business: a Free workspace can deploy JS, TypeScript and static apps only, and a container app in a workspace that has moved to Free stops answering (the edge returns 402 with a page saying the app needs a paid plan) until the workspace is on a paid plan again.

The files your sites and apps serve and your Worker apps' databases, together. Each database is measured about once an hour. Once a workspace is past its storage, nothing new deploys until it's back under: delete rows or files, or move to a bigger plan. What's running keeps running.

From 1 November 2026, Free stops for the month at 50,000,000 database rows read or 100,000 written. Cloudflare counts them for each of your apps' databases: a query counts every row it reads, including rows it scans and doesn't return, and every row and index entry it writes. That includes queries made while serving public-path requests, and the reads and writes of database exports and jiayang db commands. We take the lowest figure Cloudflare's analytics give, so the count never runs ahead of what was used. If we can't measure a Free workspace's rows for two hours, its apps that have a database answer 402 until we can.

From 1 November 2026, each plan limits its databases together: 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%. Once they are over, apps with a database answer only the workspace's owners and admins, so they can delete rows through the app; everyone else, bypass tokens, public paths and webhooks get 507, and nothing new deploys. If the databases grow further, or reach 10% over, those apps answer no one. To get back under, delete rows with jiayang db exec or through the app, export and remove data, or upgrade. On Free, a workspace still over after 7 days is suspended, and 30 days after that its largest databases are deleted until it is under, after emails 7 days and 1 day before. Apps without a database keep answering throughout.

No. A plan is per workspace and includes the members it lists. Someone can belong to several workspaces on different plans.

From the workspace's Billing tab. An upgrade takes effect at once, and the difference for the rest of the current period is charged now, pro rata. The new plan's allowance starts from the moment the upgrade takes effect, and the requests served before it are billed at the old plan's price, so an upgrade never reprices what you have already served. A downgrade applies at your renewal, when the paid period ends: until then the workspace keeps the higher plan, the Billing tab shows "Team from date", and you can undo it. The renewal invoice is at the new price. Either way the dialog says exactly what will happen before you confirm. Audit events older than the new plan's retention are deleted 30 days after the change; export first.

Cancelling, along with cards and invoices, is in Stripe's customer portal, which the Billing tab opens. A cancellation takes effect at the end of the paid period, and the workspace then goes back to Free: container apps stop, and everything else keeps running within Free's limits. Audit events older than Free's retention are deleted 30 days after the change; export first. See the refund policy for what happens to a partial period.

If a payment fails we retry for up to two weeks, and Stripe emails you each time; then the workspace moves to Free, container apps stop, and everything else keeps running within Free's limits. The platform emails the workspace's owners three days before the move, and again when it happens. Paying again brings the plan back.

Pushing a container image counts against two daily budgets: the workspace's, which the plan sets, and the person's, 20 GB a day on any plan. So Team is 20 GB per workspace per day, and Business is 100 GB per workspace per day, 20 GB per person. Both are rolling: a push counts for 24 hours. A push that would go over either is refused until enough has aged out, and the image already deployed keeps running.

Creating the thing that would go over (an app, a member, a token) is refused with a message saying which limit and which plan lifts it, for example "Team allows 25 apps". Nothing already running is affected.

On every plan. The workspace export, from the workspace's Settings, is one JSON document: the workspace's configuration, its members, its sharing grants, the names of its tokens, secrets and environment variables (never a value), and the audit log the plan retains. An app's database is exported on its own, as SQL, from the app's page in the dashboard or with jiayang db export. A static site is the files you uploaded.

Deletion is immediate and permanent. The app's scripts, databases, containers and files are removed from Cloudflare right away, and its configuration, versions, sharing grants, tokens, secrets and environment variables go with them. Its entries in the workspace's audit log stay for your plan's audit retention, like every other entry. Deleting a workspace removes its apps the same way; the control plane's own records of the workspace linger for 30 days, for accounting, and nothing is ever restorable. Export first. Deleting a workspace on a paid plan cancels its subscription at once, with no refund for the rest of the period; the confirmation dialog says so.

In Stripe's customer portal, which the Billing tab opens. Stripe issues every invoice and receipt; we store no amounts.

Not yet. Every plan is monthly, paid by card through Stripe. If you need annual invoicing for a Business workspace, write to us.

Ask. Tell us about the project at support@jiayang.cloud.