Plans and limits

Every organization on the hosted app is on a plan, and the plan decides three things: how many catalog entities the organization can hold, how many members it can have, and which features are switched on. The plans on offer and what each includes are listed at componecat.ai/pricing.

A self-hosted instance has no plans: nothing is capped, and every feature is on.

Seeing your plan

Plans are managed by organization admins. Select the Organization settings button in the top right, and pick the Pricing tab. The top of the tab shows the limits and features that apply to your organization right now, and below that are the plans you can move to.

What the limits cover

Catalog entities. How many entities the catalog can hold at once, across every kind. Entities in the trash don’t count.
Members. How many people can belong to the organization. Inviting someone past that number is blocked, with a prompt to upgrade.

Reaching a limit

At your catalog entity limit, nothing can add another entity, whichever way it arrives:

New Entity is disabled, and creating one through the REST API or an AI agent over MCP is refused with the same answer, so a script reaches the limit exactly as the app does.
Restoring from the trash is refused, since a restored entity counts again.
An import that would add more entities than your limit allows is canceled as a whole, and nothing from it is applied. Re-importing entities you already have doesn’t count against the limit.
A new descriptor from Git isn’t added. Entities already synced from Git keep updating, and a later repository scan picks up the new one once you’re back under the limit.
A new vendor from Vendorian isn’t added, and the sync records an error for it. Vendors already synced keep updating.

Move an entity to the trash and you can create one again.

Going over a limit

You can end up above a limit without adding anything: moving to a plan with a smaller limit is enough. When that happens:

Everything you have stays. Nothing is deleted, hidden, or made read-only when a plan changes.
You can’t add more of what you’re over on until you’re back under the limit.
A notice appears at the top of the Catalog page, naming the limit and how far over you are.

The notice reflects where you are right now. Delete back under the limit and it clears, and creating works again. There’s nothing to wait for.

Members work the same way: moving to a plan with fewer members never removes anyone, but you can’t invite more until you’re under the new number.

Features that depend on your plan

Some capabilities are switched on by your plan rather than counted:

Integrations. Connecting GitHub, GitLab, Bitbucket, Atlassian, Microsoft 365, and Vendorian. Pro and Enterprise include every provider; Free and Basic include none. A provider your plan doesn’t include stays on the Add integration page as a locked card that names the plans that do. See Integrations.
Outgoing webhooks. Notifying your own systems when the catalog changes. See Outgoing webhooks.
Import and export. Moving your organization’s catalog in and out as a file.
Service accounts. Non-human identities for automation.
REST API. See APIs.
Search by meaning. Searching the catalog by what a component does, similar entities, and the matching tools for AI agents. Pro and Enterprise include it; Free and Basic don’t. It also needs an embedding model — see Turning on search by meaning.
Catalog Intake. Creating components from the repositories in your Git organizations. See Catalog Intake.

Where your plan doesn’t include one of the first four, its tab in Organization settings says which plans do and points you at the Pricing tab. Without the REST API, the option to connect to it isn’t offered, and REST requests are refused. Without search by meaning, none of it appears anywhere in the app, and the AI Models page tells admins which plan includes it. Without Catalog Intake, its page says which plan includes it and doesn’t offer a new intake.

If your plan stops including a feature you’ve already used, what you set up is kept, but it stops working until the feature is available again. Integration capabilities stop running, webhooks stop delivering, service accounts can no longer authenticate, and none of them can be changed. Their tabs stay visible, so you can still see what you have and delete what you no longer need.

The same holds for a single integration provider: if your plan includes integrations but not one particular provider, an existing connection to it stays visible, its capabilities stop running and it can’t be reconfigured. You can still test or delete it.

Changing plan

Choose a plan on the Pricing tab and you’re taken to Billing to complete the change. An upgrade applies as soon as it’s paid, so the new limits and features are live immediately. A downgrade takes effect at the end of the period you’ve already paid for, and until then nothing about your organization changes.

If the published plans don’t cover what you need, contact us. Limits and features can be set for an organization individually, and the Pricing tab then shows your organization’s own values.

Getting started: signing in and setting up an organization.
Integrations: what happens to connections when a plan change removes integrations.
APIs: the REST and MCP surfaces.