Conduit
Conduit
Docsllms.txtHostingGitHubIntroduction

Getting Started

OverviewInstall ConduitMCP SetupYour First AppStart with AI

Learn

ArchitectureClient vs Admin APIConfiguration

Modules

OverviewAuthenticationAuthorizationDatabaseStorageCommunicationsChatRouterFunctions

Guides

Next.js IntegrationReBAC Team ScopingGitOps State Export

Deployment

Deployment OverviewDocker ComposeKubernetes and HelmLocal from SourceContainer Images

Reference

CLI ReferenceClient APIAdmin APIEnvironment VariablesMCP Tools

Resources

Migration v0.16 → v0.17Legacy DocumentationChangelogFAQGlossaryContributing

Overview

Conduit Platform modules overview.

Eight first-party modules ship on Conduit v0.17. 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

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

AreaWhat changed
CommunicationsOne module replaces email, SMS, and push; unified templates and fallback orchestration
Admin API tokenscdt_ tokens replace authentication service accounts for MCP and automation
ReadinessCore deep GET /ready on the Admin port for Kubernetes probes
Functionsvm2 removed; constrained VM context; cron function type for scheduled handlers
Removedforms module; router proxy routes; legacy channel module containers

Module dependencies

Some modules require others at runtime:

ModuleRequiredOptional
AuthenticationDatabaseCommunications (verification email, SMS 2FA)
Authorization——
DatabaseMongoDB or PostgreSQL—
StorageDatabase—
Communications——
ChatDatabase, Authentication—
RouterDatabaseOther 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.

Next steps

  • Authentication
  • Communications
  • Database
  • Migration v0.16 → v0.17
  • All modules (visual catalog)

Configuration

Module config via Admin API, config bus, and environment variables.

Authentication

Users, local/OAuth login, tokens, teams, and 2FA.

On this page

Official modulesv0.17 highlightsModule dependenciesCustom modules