components-guide

Convex components are self-contained mini-backends with their own schema, functions, data, and API boundaries. They encapsulate features into isolated modules, enabling reuse, cleaner architecture, and scalable backend coordination for multi-feature apps.

To create a reusable backend component in Convex, create a new component under the convex/components directory, wire it into your convex.config.ts file, and call it directly from your application code to start using the encapsulated features.

Yes, you can coordinate multiple decoupled modules within a Convex project using the sibling components pattern. This allows multiple isolated backends to operate side-by-side, facilitating multi-team collaboration and modular feature deployment.

Yes, the Convex component pattern works for multi-tenant SaaS applications. Components encapsulate features into isolated backends with their own data boundaries, providing the necessary data isolation and scalable architecture required for multi-tenant environments.

You should use isolated components instead of a monolithic backend when you need to encapsulate features for reuse, require strict API boundaries between modules, or are managing multi-team collaboration where decoupled mini-backends prevent architectural conflicts.