Overview
Conduit Platform modules overview.
Eight stable v0.17 modules plus opt-in embeddings. Embeddings is not included in standalone. Legacy email, sms, and push-notifications are consolidated into communications; the forms module is removed — use database schemas, custom endpoints, or the functions module instead.
For a visual module catalog with use cases, see the marketing modules page. For upgrade steps from v0.16, see Migration v0.16 → v0.17.
Official modules
Authentication
Users, local/OAuth login, tokens, teams, 2FA, and magic links
Authorization
ReBAC resources, relations, permissions, and scoped creates
Database
MongoDB or PostgreSQL, schemas, CRUD, custom endpoints, GraphQL
Embeddings
Opt-in text-to-vector generation, backfills, and text-in semantic search
Storage
Local, S3, Azure, GCS, and Alibaba Cloud file storage
Communications
Unified email, SMS, push, orchestration, and multi-channel templates
Chat
Rooms, messages, read status, and Socket.io realtime
Router
Client API gateway — REST, GraphQL, and WebSockets
Functions
Admin-defined server-side JS — webhooks, events, cron, middleware
v0.17 highlights
| Area | What changed |
|---|---|
| Communications | One module replaces email, SMS, and push; unified templates and fallback orchestration |
| Admin API tokens | cdt_ tokens replace authentication service accounts for MCP and automation |
| Readiness | Core deep GET /ready on the Admin port for Kubernetes probes |
| Functions | vm2 removed; constrained VM context; cron function type for scheduled handlers |
| Removed | forms module; router proxy routes; legacy channel module containers |
Module dependencies
Some modules require others at runtime:
| Module | Required | Optional |
|---|---|---|
| Authentication | Database | Communications (verification email, SMS 2FA) |
| Authorization | — | — |
| Database | MongoDB or PostgreSQL | — |
| Embeddings | Database (Vector fields, indexes, raw-vector search). HTTPS provider required for generation/search, not process startup. | — |
| Storage | Database | — |
| Communications | — | — |
| Chat | Database, Authentication | — |
| Router | Database | Other modules (routes they register) |
| Functions | — | Any module accessed via grpcSdk in handlers |
Modules communicate over gRPC. The router exposes application routes on the Client API (CLIENT_HTTP_PORT, default 3000). Operators provision schemas and config via the Admin API or MCP server.
Custom modules
Build additional modules in any gRPC-compatible language. TypeScript teams use @conduitplatform/grpc-sdk for typed clients and lifecycle hooks.