Skip to main content

Glossary

Key terms used throughout Berrybell and this documentation.

Project​

A single app you build in Berrybell — its code, chat history, and settings. See Projects & workspaces.

Workspace​

The container for your projects and teammates, and the level at which billing and credits apply.

Studio​

The build interface — the chat plus the live preview — where you create and refine your app.

Chat​

The conversation where you describe what you want. Each message is a request the AI turns into changes to your app.

Conversation​

One chat thread inside a project. A project can hold several, so separate lines of work stay apart. See Studio & chat.

Coding effort​

The Low / Medium / High setting in the composer. It controls how much work the AI puts into a request — and so how much that request costs. See Studio & chat.

Live preview​

A real, running version of your app that updates as you build, before you publish. See Live preview.

Visual edit (select mode)​

Clicking an element in the live preview to edit its text directly, or to describe a change that applies to just that block. See Visual editing.

Version​

A saved snapshot of your project, committed each time the AI changes it. You can restore an earlier one. See Version history & undo.

Plan (build plan)​

The set of steps the AI proposes for a larger request, shown before it makes changes. Not to be confused with a subscription plan.

Approval​

A pause where the AI asks for your go-ahead before a higher-impact step, such as changing data or using an integration.

Publish​

Deploying the current version of your app to a live URL so others can use it. See Publishing your app.

Custom domain​

Your own web address (e.g. yourbrand.com) pointed at your published app, with HTTPS set up automatically. See Custom domains.

Template​

A ready-made, working app you can start from and customize instead of building from a blank page. See Templates.

Integration (app connector)​

A connection to an external service — a database, Stripe, Slack — for the AI to use while it builds your app. Only Berrybell's own database and payments, and any key you choose to publish, reach the running app; other connections stay with the AI. As well as the curated services, you can connect one with your own API key, your own OAuth app, or by registering a remote MCP server. See Integrations overview.

Berrybell Cloud​

The managed backend Berrybell can set up for your app — the database, private file storage for uploads, and the user accounts built on the database. Pressing Enable Berrybell Cloud turns on the database and storage together; user accounts are turned on separately. See Your project database and File storage.

Migration (migration file)​

A numbered SQL file under migrations/ in your project's code that records one change to the database's structure. The AI writes one for every schema change and applies it to the environment it's working on; publishing never applies it. See Your project database.

Backup​

A snapshot of your production database — taken with Back up now, or automatically before a restore or before sign-in for your app's users is turned on — that you can restore from Cloud → Database → Tables → Backups. Other environments have no backups of their own. See Your project database.

File storage​

Private storage for the files people upload to your app, one per environment. Your published app reaches it; you can't browse it from the Studio yet. See File storage.

Environment​

A separate copy of your app, with its own database, variables, file storage and address, that runs once you publish to it; every environment is published from the same project code. Every project has production, your live app; on a Business plan you can create others, such as staging. For a variable, it's the scope a value applies to: All environments, Agent sandbox, Preview deploy, Published app, or one environment you created. See Environments and Variables & secrets.

Production​

The environment your users reach. It can't be reset or deleted, and on a project with other environments, changes to it ask first.

Selected environment​

The one environment the preview, the dev server, the AI and the Cloud pages work on, chosen in the top bar beside the project name. One per project, shared by everyone in it. Publishing doesn't follow it: Publish asks where to publish each time. See Environments.

Variable / Secret​

Configuration your app reads while it runs. Variables are plain values you can read back; secrets are encrypted and can only be replaced, never re-read. See Variables & secrets.

Credits​

Two separate balances, both refilled by your subscription: AI credits pay for build runs and the Studio's other paid tools, such as Advanced SEO checks — one credit is a fixed dollar unit of usage, $0.25 — and your hosting budget pays for the cloud resources your apps use.

Hosting budget​

The dollar-denominated part of your plan that your apps' cloud resources draw on: published apps, the automatic preview deploys, and each project's database and file storage. It's kept separate from your AI credits. See Usage & costs.

Credit balance / Top-up​

Credit you buy with Buy credits on top of your plan's allotment. It pays for AI builds or hosting once the matching allotment runs out. It never expires and, unlike the allotment, carries over past the cycle reset. See Plans & credits.

Auto-reload​

Automatic top-ups: when your available credit falls below a trigger you set, a saved card is charged a chosen amount, which is added to your credit balance, up to a monthly limit you set. Paid plans only. See Plans & credits.

Sending domain​

A domain you own that your app's sign-in emails are sent from — normally a subdomain such as notify.yourbrand.com, though the domain itself is allowed — so the mail is signed as your domain. One per project, shared by all its environments. See Custom email domain.

DKIM / DMARC​

The DNS records that let a receiving mail server verify your app's mail really came from your domain, and decide what to do when it can't. See Custom email domain.

Expert Assist​

Having a Berrybell engineer build the project for you instead of building it yourself. See Expert Assist.

GEO​

Checks for whether AI answer engines can read and quote your pages — the counterpart to SEO checks for search engines. See SEO.

Test / sandbox mode​

A safe mode (for example in Stripe) that behaves like production but doesn't affect real money or data. In Stripe payments, everything except your production app — the live preview, the automatic preview deploys and every environment you create — always runs in sandbox, whatever the store's Stripe mode. See Stripe payments.

Subscription (plan)​

What you pay Berrybell for access and included credits. Managed in Billing.

Annual plan​

Pro or Business billed yearly — 12 months for the price of 10, in one payment. It's offered where Plans & usage shows a Monthly / Annual toggle. Your allotment still refills monthly. Required for Expert Assist. See Plans & credits.

Single sign-on (SSO)​

Signing in to Berrybell through your company's identity provider (OIDC or SAML), set up per workspace on the Business plan — not sign-in for your app's users, which is a separate feature. See SSO.