Skip to main content

Usage & costs

Two different things cost money in Berrybell, and they are measured in different ways:

  • Building spends AI credits, charged per run, immediately. So do the paid tools in the Studio, such as image generation and Advanced SEO checks.
  • Running your app spends your hosting budget, measured from the cloud resources it actually used. That covers your published app and the automatic preview deploys Berrybell makes while you build.

Plans & credits explains the balances. This page explains where the numbers come from.

If you've read the pricing page

What pricing material calls "hosting credits" is the same thing the product calls your hosting budget. The product shows it in dollars rather than credits, because hosting is metered in cents.

Where to look​

Open Plans & usage from the workspace menu or workspace settings, and go to the Usage tab. It covers the whole workspace and shows:

  • Remaining balance, in credits. Where your workspace has a shared credit balance, a line under it reads "Credit balance $X — spends on AI usage and hosting alike, and carries over." On a workspace that has never subscribed, a line reads "Spend from your welcome or top-up balance. Subscribe for a monthly allotment."
  • Consumption for Today, This week and the month. Today and this week are plain totals. On any paid plan, monthly or annual, the third bar is Plan allotment (this month), drawn against your plan's monthly allotment; on a workspace that has never subscribed it's a plain This month total.
  • By type (this month) — Planner, Claude Code, Summarizer, RAG embed, RAG query, Chat, Attachment ingest, SEO, Image generation, Other. SEO covers both AI-written SEO fixes and Advanced SEO checks.
  • By agent (this month) — which of the agents that worked on your builds spent what.
  • Cloud usage (this cycle) — the deployed-app side, covered below.

One project's cloud usage is on that project's Cloud overview instead, split by environment when it has more than one — see Usage per environment.

Why the two numbers behave differently​

AI usage is charged when a run finishes. The debit lands as soon as the build completes, and the chat shows the running total of AI credits used in that conversation. Advanced SEO checks are charged the same way, once they've run; a site crawl is charged when it finishes. While a check other than a crawl is running, one AI credit is set aside for it. That hold isn't a charge and isn't taken off Remaining balance, which is why a new check or crawl can be refused while others are running even though the balance looks high enough — see Several checks at once.

Cloud usage is collected hourly and rolled up. The figures trail real usage by roughly one to three hours, and the panel carries an as of timestamp so you can see how fresh they are. If your app got traffic an hour ago and the number hasn't moved yet, that's the lag, not a bug.

What draws on the hosting budget​

The Cloud usage panel lists only the resources your workspace actually used this cycle, so a workspace running one simple app sees a shorter list:

  • Database compute — time your project's database spends awake. It sleeps when idle and wakes on the next query, so a quiet app costs very little here. The first request after a quiet spell waits a moment while it wakes, typically a few hundred milliseconds. Each environment has its own database compute and storage.
  • Database storage — how much data you're keeping.
  • Database transfer — data moving in and out of the database.
  • App requests — requests served by your published app, and by its automatic preview deploys.
  • App CPU time — processing time those requests use.
  • App file storage — files saved in your app's storage, billed on the largest amount stored in each hour (GB·mo). It accrues whether or not anyone visits. Reads and writes aren't charged separately; the requests that handle them count as App requests and App CPU time.
  • Preview storage — the stored pre-rendered builds the preview pane can show, measured per workspace in GB·mo. It appears only while such builds are stored.

How it's priced​

Berrybell is billed by the cloud providers that run your app, and passes that through with a margin. There is no per-request price list to memorise: what you pay tracks what your app actually consumed. The per-unit rates are configuration and change as provider pricing does — the panel always shows the resulting dollar amounts for the current cycle.

Usage per environment​

Each environment is metered the same way as production — its database, its published app's requests and CPU time, its file storage — and draws on the same workspace hosting budget. To see one environment's share, open the project's Cloud overview. Its Usage this billing cycle card shows usage for the environment selected in the top bar, in up to two groups:

  • Used by staging — the selected environment's own usage, with its name in place of staging.
  • Automatic preview — the preview deploys that update while you build (see below).

Every cost is on exactly one environment's card. A database keeps your data while it sleeps, so its storage counts every hour, awake or not, and always under the environment it belongs to. Anything that can't be tied to a specific environment counts as production's. In the occasional hour when several environments have all been asleep for a long time, their combined database storage is divided evenly between them.

On a project with only production, the same card reads Used by your app. Like the Usage tab, it's collected hourly and can be a few hours behind. Billing itself stays per workspace: there is no separate budget for each environment.

The build machine isn't on your hosting bill; preview deploys are​

The machine the AI and the dev server run on while you build doesn't appear in your cloud usage and doesn't draw on your hosting budget. What a build costs is charged in AI credits, per run; see How a run is priced.

The live lane of the live preview runs on that machine too. The one exception is the database it reads and writes, which is the selected environment's, so that use is metered as database usage.

The automatic preview deploys Berrybell builds after each change are different: they are real deploys, and they draw on the hosting budget like any other.

  • Their requests and CPU time show on the project's Cloud overview as Automatic preview. In the workspace Usage tab they're part of App requests and App CPU time.
  • Files your app saves while you test in the preview go to the selected environment's storage — production's, on a project with only production — and count as App file storage. The database the preview works on is the selected environment's too, and its use is metered there.
  • Their stored builds show as Preview storage, while any are kept.

A published app keeps costing​

Once an app is published it keeps consuming while it is deployed and receiving traffic, whether or not you ever open the Studio again. Stored files cost money for as long as they're kept, even when nobody visits.

If a project is finished with, deleting it stops the charges for its app's requests, but not every charge straight away. Files in its other environments are scheduled for deletion after a grace period (7 days by default). Production's files wait for Berrybell to remove them, because deleting a project doesn't take its published site down. Either way, stored files count toward App file storage until they're removed. See When files are deleted.

Running low​

Owners and admins are emailed when the hosting budget's monthly allotment is 80% used, and again when it runs out. On a paid plan they can also set a figure of their own with Email me before it runs out, and are emailed when available credit falls below it — see Low-balance email. Both are checked when the hourly hosting charge is taken, so a workspace that's only spending AI credits isn't emailed by them.

On a paid plan you can top up from Plans & usage, or turn on auto-reload so it happens without you. Buying a top-up needs a paid plan — a free workspace's route to more AI credits is the next daily reset or an upgrade, and to more hosting budget only an upgrade.

If the hosting budget is exhausted​

Published apps in the workspace are paused:

  • Visitors get a "paused" page instead of your app — your app's own code never runs.
  • The project database stops accepting connections, so a copy of the connection string doesn't keep the spend going.
  • Owners and admins are emailed when it happens, and again when it lifts.

A workspace on a paid plan gets a small overdraft buffer first, so a mid-cycle blip doesn't pause production; a workspace with no paid plan pauses at the first window it cannot pay for. Recovery is automatic — a top-up, an auto-reload charge, an upgrade or the next cycle's refill brings your apps back as soon as the balance is positive again. Nothing is deleted while an app is paused, and stored files keep counting toward App file storage. A free workspace gets no hosting refill — its hosting budget is the one-time welcome grant — and can't buy top-ups, so upgrading is the only way back.

Avoiding a pause

On a paid plan, turn on auto-reload or keep a credit balance on any workspace running an app you care about. With a shared credit balance, auto-reload watches hosting as well as AI credits. With separate top-up balances, only hosting budget relieves hosting: bought AI credits don't, and neither does an auto-reload amount that buys AI credits. See Plans & credits.

Next steps​