---
title: "Plans and Quotas"
description: "How ComStack controls what a project can do: modules switch capabilities on, and a single plan document holds the limits. Limits are set per project during the closed beta."
url: "https://comstack.ai/docs/concepts/plans-and-quotas/"
---
## What this is

Every ComStack project has a set of capabilities — which features are active, how many languages it supports, whether it can make phone calls, how many people can work in it. This page describes the mechanism behind that.

> **ComStack is in closed beta.** Limits are set per project while we learn what the right ones are, and commercial plans have not been announced. This page describes how the mechanism works, not what anything costs.

## Modules and plans

Two ideas do the work.

A **module** is a capability that can be switched on or off independently — the knowledge base, custom pages, the website, contacts and the CRM around them, the web assistant, phone, WhatsApp, GitHub sync, the Chrome extension, API keys.

A **plan** is a single document that says what a project may do right now: which modules are on, and the limits that apply to them.

**One document decides everything.** Enforcement reads the project's plan and nothing else — never a template, a coupon or a subscription. That keeps the rule simple and the commercial arrangement behind it free to change without touching how anything is enforced.

## Limits

A limit is a number inside the plan. The ones a project meets in practice:

| Limit | What it bounds |
| --- | --- |
| Languages | How many locales a knowledge base or custom-page set can be published in |
| People | How many members a project can have |
| Phone numbers | How many numbers the phone and WhatsApp channels can hold |
| Web assistant sessions | Conversations per day on the website assistant |

When a project reaches a limit, the action is refused with a message naming the limit — nothing is silently dropped or truncated.

## Templates

A project is created from a **template**, which decides the shape a new project starts with: which modules it has, and what its limits are. Changing a template does not disturb projects already created from it — a project's own plan document is what governs it.

## What is not decided yet

Commercial levels, prices and the limits attached to each are still being worked out and will be published when ComStack launches. During the beta, access is invite-based and limits are configured per project.

If you are in the beta and want to know where your project stands, ask in the app or over the MCP server — `get-project-state` reports the modules and limits in effect.