Skip to main content

Plans & credits

Berrybell combines a subscription plan with usage. The plan refills your balances each month; usage draws them down as you build and as your published apps run.

Plan names, prices and the exact amounts included are on the pricing page and on your workspace's Plans & usage page (open it from the workspace menu or from workspace settings) — this page explains the mechanics behind them, so you can read a bill and know what happened.

Two balances, not one pool​

A workspace holds two separate balances:

  • AI credits — spent by anything the AI does: a build in the Studio chat, a scoped AI edit in the live preview, an AI-generated image (including ones the AI makes during a build), reading an image you attach, an AI-written SEO suggestion. Reading an attached PDF or text file is free. AI credits also pay for the Advanced SEO checks, which buy search data rather than AI: a site crawl, keyword research, a competitor gap, a rank check.
  • Hosting budget — held in dollars, not credits, and spent by the cloud resources your apps actually use: published apps, the automatic preview deploys Berrybell makes while you build, and a project's database and file storage, published or not. See Usage & costs.

Your plan refills both each month, and on the plan side they do not fund each other: an unused AI allotment cannot pay a hosting bill, and spare hosting budget cannot pay for a build. Credit you buy is different: it sits in a separate Credit balance that can pay for either once the matching allotment runs out — see Topping up.

Same thing, two names

Pricing material sometimes calls the hosting side "hosting credits". In the product it is shown as your hosting budget and displayed in dollars. It's the same balance — see Usage & costs for what draws on it.

What an AI credit is worth​

One AI credit buys $0.25 of AI usage. So a 100-credit allotment is $25 of AI usage. Credits are charged in fractions, not whole numbers — a small change can cost a fraction of a credit.

How a run is priced​

A build is not priced per token, and not at a flat price per message. Berrybell takes the true provider cost of that run, applies its margin, and converts the result into credits. What follows from that:

  • Bigger requests cost more. A long, multi-step build costs more than a one-line copy change.
  • The coding-effort level you choose in the composer changes the cost, because it changes which model does the work.
  • A run that fails is not charged. The charge is worked out when a run completes. Two things are charged the moment they happen instead: images the AI generates during a run, and the description made of an image you attach. Those are paid even if the run fails.
  • Every completed run has a small minimum charge, so no run is free.
  • You can see where it went. The chat shows the running total of AI credits used in that conversation, and Plans & usage → Usage breaks the month down by request type and by agent.

The free allowance​

If your workspace has no subscription:

  • A one-time welcome grant. The first workspace you create gets a starting amount of AI credits plus a starting hosting budget, credited once per person. It lands in your Credit balance, which carries over, so it doesn't disappear at a cycle boundary.
  • A daily AI allowance that resets. It is set back to the same amount after each midnight UTC — it does not accumulate. Yesterday's unused credits are gone.
  • It lands on one workspace per person. The daily allowance applies to a single workspace without a paid plan, so creating extra workspaces does not multiply it.
  • No monthly hosting budget. Beyond the one-time welcome grant, a free workspace gets no hosting refill each cycle.

The daily amount is shown on the Free plan card in Plans & usage; the welcome grant shows up in your Credit balance.

Monthly or annual​

Pro and Business can also be billed annually where it's offered. If Plans & usage shows a Monthly / Annual toggle above the plan cards, you can choose either; if not, plans are billed monthly only. The Annual tab carries its discount badge, and the term you're on is marked · current.

  • 12 months for the price of 10, charged in one payment. Each card's headline stays a per-month figure so the two terms compare directly, and the line under it gives the amount billed yearly.
  • Your allotment still refills monthly. An annual plan buys twelve monthly allotments, not one yearly lump, so unused plan credits still reset each month.
  • Expert Assist requires an annual plan. Annual Pro includes 1 expert build a year and annual Business 3.

Switching between monthly and annual is a plan change — see Billing for how each change is charged and when it takes effect.

Topping up​

On Pro and Business you can buy extra credit at any time. A few things are worth knowing:

  • Top-ups carry over. Unlike the plan allotment, which resets each month, a top-up stays until you spend it. It never expires.
  • It's spent after the allotment. Usage draws on your plan allotment first; the credit you bought is used once the matching allotment runs out.
  • Every top-up you can buy is sold at face value — $10 buys $10 of usage. There is no bonus-credit pack and no volume-discount pack.

Open Plans & usage → Plans & top-ups. The first two cards are your plan's allotment: Plan AI credits ("of N · resets monthly", or daily on a free workspace) and Plan hosting ("of $X · resets monthly"). Below them, Credit balance is the credit that carries over — what you've bought, plus any welcome grant: it "spends on AI builds or hosting once the plan allotment above runs out, and carries over between billing periods." Its figure is labelled Remaining balance.

To add to it:

  1. Press Buy credits. The Add credits dialog opens with one tile per amount — $10, $25, $50 or $100, with $10 selected. There is no custom amount.
  2. Check Total due; no tax is added on top. Payment method reads Chosen at checkout.
  3. Press the button, which repeats the amount (for example Buy $25 of credits), and pay on Stripe's checkout page.

Credits are added once Stripe confirms the payment. When you come back to Berrybell you'll see Payment received — updating your balances… while the new balance loads.

Only owners and admins can buy credits; other members see Only owners and admins can purchase credits. A free workspace sees Top-ups are part of Pro and Business. Upgrade to buy credits whenever you need them. in place of the button.

Seeing separate top-up balances?

Some workspaces keep bought credit per kind rather than in one shared balance. There the cards read AI credits and Hosting budget, each with a line such as "80 monthly + 20 top-up", and the credit balance reads "N AI credits · $X hosting", labelled Remaining top-up balance. Buy credits opens the same dialog, but with two tiles: $25 for 100 AI credits (selected first) and $10 for $10 hosting budget. The dialog says "Each amount buys one kind of credit". Bought AI credits cannot pay a hosting bill or lift a hosting pause, and auto-reload watches only the kind its amount buys.

Auto-reload​

Auto-reload keeps a workspace from stopping mid-build, or its published apps from pausing, by buying credit for you when it runs low. It is prepaid, not postpaid metered billing — nothing is billed after the fact.

The status link next to Remaining balance — Auto-reload on, Auto-reload off, Auto-reload paused or Auto-reload needs attention — opens Adjust auto-reload. It has three fields:

  • When available credit falls below — the trigger, from $0.01 to $1,000.
  • Top up with — one of the amounts on sale.
  • Auto-reload at most this much per month — a limit above $0 and up to $10,000. It must be at least the amount you top up with; otherwise you'll see Must be at least $X — the amount above — or nothing would ever be charged. Under the field, $X auto-reloaded this month. shows what has been charged so far.

A new rule starts with a $5 trigger, a $25 top-up and a $100 monthly limit. Below the fields is the card it charges — Charged to Visa •••• 1234, or No card saved — nothing can be charged — with Add card or Update card to save one on Stripe. A card already saved for your subscription counts. While auto-reload is off, press Turn on to save the rule armed, or Cancel to close without changing anything. Once it's on, the buttons read Update (save your changes) and Turn off (disarm it).

How it behaves:

  • It needs a card. Turning it on with no card saved is refused. If the balance is already below the trigger when you turn it on, it charges straight away.
  • The trigger watches whichever of AI or hosting is nearest the edge, with your credit balance counted on top. Your plan's monthly allotment limits how high the trigger can effectively go: set above the smaller of your two monthly allotments (counting each AI credit as $0.25), it behaves as if it were set at that figure.
  • At most one attempt every 10 minutes, so it cannot double-charge.
  • The monthly limit counts per UTC calendar month. Once a charge would take you past it, auto-reload stops charging until the next month. No email is sent when that happens.
  • Every charge and every failed charge is emailed to the workspace's owners and admins.
  • It pauses itself after 3 failed charges in a row (Auto-reload is paused after repeated payment failures. Update your card, then turn it back on.), or immediately if there is no card to charge (Auto-reload is paused — no saved card. Add a card to resume.). Saving a card, or pressing Turn on / Update, re-arms it.
  • If the amount it's set to stops being offered, it can't charge. The status reads Auto-reload needs attention (or Auto-reload paused, once it has tried to charge), and the notice asks you to pick a new one.
  • Owners and admins only. Other members see the status. While auto-reload is on they also see the trigger, with Only owners and admins can change auto-reload.
  • Paid plans only. If a workspace drops to Free with auto-reload still on, it stops charging, and you can still open the dialog to turn it off.

With separate top-up balances (see above), the trigger is measured against the kind the chosen amount buys, and a charge relieves only that kind.

Low-balance email​

The same dialog can warn you before credit runs out, whether or not auto-reload is on. It's a separate setting, saved with its own Save button:

  1. Tick Email me before it runs out.
  2. Set Send an email when available credit falls below — anywhere from $0.01 to $10,000.
  3. Press Save.

The email goes to owners and admins once each time available credit drops below your figure, measured against whichever of AI or hosting is nearest the edge, with your credit balance counted on top. It re-arms when the balance is back above the figure, or when you edit it. For a workspace named Acme with a $50 figure, the subject reads "[BerryBell] Acme: credit below $50.00". Once it's set, the panel shows Emails owners and admins below $X. under the balance. Paid plans only.

It can arrive late, or not at all

Berrybell checks your figure when your published apps' hosting usage is billed, about once an hour. The email can arrive a few hours after credit drops below it, and a workspace with nothing published may not get it at all — spending AI credits doesn't run the check. Don't rely on it alone to catch AI spending.

The emails at 80% and 100% of your plan's hosting budget still arrive. Your own figure replaces only the generic emails Berrybell otherwise sends when the credit balance itself runs low or runs out.

When you run out​

AI credits. A build, an image generation or an Advanced SEO check is refused before it starts when the balance is too low, so nothing is half-run and nothing is charged. In the chat, a Not enough AI credits dialog opens with Cancel and View plans, and your message stays in the composer. Image generation needs about 2 AI credits available to start — a minimum balance, not the price (see Images & attachments); below that, the panel says Not enough credits. Top up to generate images. An Advanced SEO check can also be refused while other checks are running and holding credits, and a workspace runs at most three keyword, competitor or ranking checks at once (site crawls don't count) — see Advanced SEO tools. If auto-reload is on, a refused build or check also triggers it.

Hosting budget. Running out here has a bigger consequence: published apps in the workspace are paused until funds arrive. Paid workspaces get a small buffer first, so a mid-cycle blip never pauses production; a workspace with no paid plan pauses at the first window it cannot pay for. On a paid plan, adding funds — a top-up, an auto-reload charge, or the next month's refill — lifts the pause automatically. A free workspace can't buy top-ups and gets no hosting refill, so upgrading is the only way back; the panel says Upgrade to a paid plan to keep going. Usage & costs covers this in full.

Using credits efficiently​

A few habits stretch your credits:

  • Prompt clearly. Specific requests get you there in fewer rounds — see the Prompting guide.
  • Start from a template instead of building common apps from scratch.
  • Work in focused steps so you're not regenerating large areas repeatedly.
  • Drop the effort level for small changes. Reserve the highest setting for work that genuinely needs it.
  • Edit text directly in the preview. Changing a word by hand in the live preview costs nothing; asking the AI to do it costs a run.

Next steps​