Bundles are about provisioning, not pricing. Installing a bundle makes the feature available in your project; what each plan allows (quotas, AI access, etc.) is a separate concern. See Semantic Search & AI for an example of a feature that needs both its bundle and a paid plan.
The core bundle
Every project always has thecore bundle. It’s installed automatically when the project is created and cannot be removed. Core provides the foundation that every other feature builds on:
- Users, authentication & identity — email/password accounts, OAuth identities, and OAuth provider configuration. See Authentication.
Available bundles
On top of core, you choose which of these to install. Most are independent — install only what you need — but a few depend on another bundle (see below).Bundle dependencies
A couple of bundles build directly on another and can’t be installed on their own:commentsandcollectionsrequireentities. Comments attach to an entity and collections save entities, so both need theentitiesbundle installed first. The dashboard pre-checksentitiesfor you when you select either; installing them via the API withoutentitiesreturns409 database/bundle-prerequisite-missing. For the same reason,entitiescan’t be removed whilecommentsorcollectionsare still installed — remove those first.interest-matchingrequiresai-search. Interest matching builds on the content embeddings thatai-searchprovides, soai-searchmust be installed first and can’t be removed whileinterest-matchingis present.
Choosing bundles when you create a project
When you create a project in the dashboard, you pick the bundles you want.core is always included — you can’t deselect it — and you can start with core only and add the rest later. Nothing is locked in at creation time.
Adding and removing bundles later
Installed bundles are managed from the Database page of your project in the dashboard (https://dash.sublay.io/<projectId>/database). From there you can install a bundle you skipped, or remove one you no longer need.
Installing a bundle is an asynchronous operation — the dashboard shows it as provisioning while the tables are created, then installed once it’s ready. This usually takes a moment.
What happens if a bundle isn’t installed
Feature endpoints and SDK hooks only work when their bundle is installed. If your app calls a feature whose bundle is missing, the API responds with a clear error instead of a generic failure:
If you hit one of these while building, the fix is almost always to install the bundle for the feature you’re using. Open the Database page in the dashboard and add it.
This is why a feature can be fully documented and supported but still return
database/tables-not-available on your project — the docs describe the whole platform, while your project only runs the bundles you’ve installed.
