components-guide
Self-contained mini-backends that bundle schema, functions, and data with clear API boundaries.
- Components encapsulate features like storage, payments, and notifications as reusable backend modules, reducing monolithic code and improving maintainability
- Sibling components pattern allows multiple components to work together at the same level, with the main app orchestrating calls across them
- Official component library includes authentication, storage, payments, AI, and utility components like rate limiting, migrations, and workflow orchestration
- Create custom components for self-contained, reusable features; components cannot directly access parent app tables or call each other, maintaining isolation
Convex Components Guide
Use components to encapsulate features and build maintainable, reusable backends.
What Are Convex Components?
Components are self-contained mini-backends that bundle:
- Their own database schema
- Their own functions (queries, mutations, actions)
- Their own data (isolated tables)
- Clear API boundaries
Think of them as: npm packages for your backend, or microservices without the deployment complexity.
Why Use Components?
Traditional Approach (Monolithic)
convex/
More from get-convex/agent-skills
convex-quickstart
Creates or adds Convex to an app. Use for new Convex projects, npm create
45.0Kconvex-performance-audit
Audits Convex performance for reads, subscriptions, write contention, and
44.5Kconvex-setup-auth
Sets up Convex auth, identity mapping, and access control. Use for login, auth
44.4Kconvex-migration-helper
Plans Convex schema and data migrations with widen-migrate-narrow and
44.3Kconvex-create-component
Builds reusable Convex components with isolated tables and app-facing APIs.
44.3Kconvex
Routes general Convex requests to the right project skill. Use when the user
20.8K