Plans & pricing

dply bills each organization a monthly plan fee plus its usage. The plan fee covers the plan; usage bills on top of it from the first unit. Starter costs $0 a month: you pay only for usage, with a card on file and a monthly spending cap. There is no trial; Pro and Team bill from the day you choose them. Static sites and uptime monitoring also have a free tier that needs no card. Sites and apps are unlimited on every plan, subject to fair use. This page lists what each plan includes and the rate for every meter, so you can predict a bill before it arrives.

All prices are in US dollars. Plans are billed monthly; there is no annual option.

Free tier#

An organization without a plan can still use these, with no card:

The free sites are your organization's three oldest static sites. Over the monthly bandwidth or request limit, they show a "free limit reached" page until the month ends or you choose a plan; nothing is deleted. Container apps, databases, workers and every other resource need a plan. With a plan, an organization can have 50 URL monitors and any number of status pages.

Plans#

No plan includes usage. Everything you use bills at the rates below, on top of the plan fee. See Usage & metering for how usage is measured and Invoices & taxes for how it appears on your bill.

Sites and apps#

Every plan deploys as many sites and apps as you want — static, hybrid, Worker SSR and container apps all count as apps, and none of them has a per-site or per-app fee. Preview deployments don't count toward anything; their builds and usage still bill like any other deploy.

Fair use#

"Unlimited" is subject to fair use: a hidden limit on non-preview apps, meant to catch abuse rather than normal growth. At the limit, creating another app shows "You've reached the fair-use limit for your plan — contact us to raise it." Nothing is charged, and there's no upgrade prompt — contact support to raise it.

Seats#

Every member of the organization is a seat, and pending invitations count too, except view-only members: someone who can only view the organization's apps, and an invitation for that role, doesn't take a seat and is free. On Starter and Pro the seat count is a hard limit: you can't invite past it, and you can't move down to a plan with fewer seats than you have members. On Team, the first 10 seats are included and each additional member costs $5 a month.

Other limits#

Non-price limits — build concurrency and timeout, custom domains, database and queue counts, worker instances, realtime connections — stay per plan. See Usage & metering for how usage bills and the tables below.

Enterprise's limits are set in your contract; none of the above is a hard ceiling there.

Usage rates#

Usage is billed in arrears, on the invoice after the billing period ends, at the rates below. See Usage & metering for how each meter is measured and Invoices & taxes for how it appears on your bill.

Rates are shown to more precision than a cent where the unit is small. Bandwidth is a flat price dply sets, not a pass-through of a provider charge. Each invoice line is rounded to the nearest cent.

Container apps, queue workers, dply databases (Postgres, MySQL, MongoDB) and Valkey are billed per second while they're awake; asleep is $0 (database storage still bills per GB-month, awake or asleep). See Scaling & sleep.

Included build minutes#

Each plan covers some build time every billing period. Build time past it bills per second at the Build time rate above.

Sizes#

Container apps, dply databases and Valkey share one size ladder. Memory differs by product; the price is per second while the resource is awake.

Container apps also offer 1/16 vCPU below this ladder, for non-PHP apps only. Valkey's 0.25, 0.5 and 1 vCPU sizes sleep when idle; 2 and 4 vCPU stay on. Each Valkey size also has a monthly maximum — see Valkey (Redis). Each container app size has one too: an instance never bills more than 600 hours of its every-vCPU-busy rate in a month — see Containers.

What's never throttled, and what is#

On Pro and Team, usage doesn't stop anything that's metered unless you set a spending cap: sites keep serving, builds keep running, and the usage bills on your next invoice. A few limits are hard caps rather than meters:

• Seats on Starter and Pro.
• Custom domains per organization.
• The number of D1 databases and queues.
• Concurrent builds and the build timeout.
• Realtime connections per app.
• The fair-use limit on apps.

Spending cap on Starter#

Starter always has a spending cap: $25 of usage a billing period by default. Past it, builds and traffic pause until the next billing period or until you raise the cap. To raise it, open your organization's Billing page, choose Limits, enter a higher amount under Spending cap and choose Save. See Starter and spending caps and Spending caps & alerts.

Estimate a bill#

The public pricing page has an estimator for requests, bandwidth, build time and one small container app, at the same rates the invoice uses. It is an estimate: it leaves out storage operations, databases, Valkey, key-value, realtime and other meters. Inside the app, your organization's Billing page shows usage this period and the estimated charge for the current period.

A Pro organization with $32 of usage in a period (build time past its 1,000 included minutes counted in that usage) pays:

Related#

• Starter and spending caps
• Usage & metering
• Spending caps & alerts
• Invoices & taxes