Plans and usage

The plans

Every plan has unlimited members and apps, a development environment per app, hosted Next.js pages, the Shopify sync and webhooks, models, actions and vector fields, the API, the MCP server and ib-apps. A team without a plan is on Free.

What is metered

Only production is counted. The Usage page shows development too, so you can see what an app will use before it ships.

• Embeddings for vector fields aren't part of the plan. They are ordinary embedding requests, in both environments, at the gateway's price: billed to the caller's key, or to the team's Apps key.
• Development servers are included within fair use, about 100 awake hours per app a month. They aren't billed; the Usage and Plan and usage pages show the hours against that figure.
• Not billed: development environments, builds and deploys, file syncs on their own, and installed stores.

Usage is rolled up every hour, so the pages run up to an hour behind.

Free's limits

• One production app. The first app to deploy holds it; deploying that app again is always allowed. Deploying a second app is refused until the first is archived or the team upgrades.
• Five stores in production. Production apps can be installed on five stores in all. A sixth store's install is refused before Shopify shows its approval page. Reinstalls, new scopes on a store already counted, and development installs are never refused. Uninstalling the app from a store frees its place.
• Allowances pause, they don't charge. Past any of Free's allowances, the team's apps pause: production shows a paused page, and actions and app proxy requests are refused. They resume when the next month starts, or as soon as the team upgrades.

How it is charged

Billing periods are UTC calendar months. Everything comes out of the team's balance, like gateway requests, and counts toward the team's monthly budget.

• The plan's fee is charged on the first of each month.
• Overage is charged once a day for the day before: the month so far past the allowances, less what has already been charged for it. Usage that arrives late lands in the next day's charge.
• Each charge is a line on the team's Billing page under Apps, with each app's share. An app's share of the fee and overage follows its share of the team's runs and requests, plus its own embeddings.

Changing plans

Change the plan on Apps → Plans. Owners, admins and billing admins can change it; other members see the comparison only.

• An upgrade starts at once. It charges the new fee for the rest of the month, less what the current fee already paid for it. A Free team paused at its allowances resumes with it. If the balance can't pay, the plan stays as it was.
• A downgrade starts on the first of next month; until then the team keeps its current plan and allowances. Choosing the current plan again cancels it.
• Moving to Free is refused while the team has more than one production app or production installs on more than five stores. Archive apps or uninstall them from stores first.

Budget and grace period

Apps has no budget of its own: the cap is the team's monthly budget in Directives, shared with gateway and Auditor spend. On Pro and Scale, the team's apps enter a 72-hour grace period when the team goes over that budget (whichever product takes it there), or when the balance can't pay an Apps charge.

During the grace period the balance may go below zero for Apps charges only, down to a floor of about what the grace period will use (the last week's daily Apps charges for 72 hours, plus anything that couldn't be paid, and at least $5). The next top-up settles it first. Gateway requests are still refused once the available balance is zero.

Raise the budget, add credit or change the plan and the apps return to normal within a minute. The team's owners, admins and billing members get an email when the grace period starts, when less than a day of it is left, when the apps pause (on Free too, at its allowance) and when they run again. Plan and usage and the team's Billing page show when the grace period ends and what to do.

Log retention

Each environment's event log keeps events for the plan's days (1, 14 or 30) and older ones are deleted every hour. Export in Logs to keep events for longer.

Record history, what lets an environment's records be restored, is kept for the plan's restore window (1, 7 or 30 days) and pruned every hour; after a downgrade the shorter window applies at once. It counts toward storage as Record history.

In the dashboard

Under Apps in the team sidebar:

What a limit looks like