Introduction
What Conduit is and how the modular BaaS architecture works.
Conduit is a self-hosted, modular Backend-as-a-Service (BaaS). Common backend capabilities — authentication, database, storage, authorization, communications, chat, and more — ship as pluggable modules you deploy as microservices or as a single standalone image.
Application teams consume Conduit through the Client API with user bearer tokens. Operators and AI agents provision schemas, config, and admin tasks through the Admin API or the Conduit MCP server. Trusted server processes use the gRPC service API via @conduitplatform/grpc-sdk.
For AI agents
Fetch the full doc index at llms.txt. For Cursor, also install the Conduit plugin.
Default ports
| Surface | Env var | Default |
|---|---|---|
| Client API (REST/GraphQL) | CLIENT_HTTP_PORT | 3000 |
| Client WebSockets | CLIENT_SOCKET_PORT | 3001 |
| Admin API | ADMIN_HTTP_PORT | 3030 |
Use CLIENT_BASE_URL and ADMIN_BASE_URL in your project — never hard-code deployment URLs.
Module map
Authentication
Users, OAuth, tokens, teams, 2FA
Authorization
ReBAC resources, relations, permissions
Database
Schemas, CRUD, custom endpoints
Storage
S3, Azure, GCS, local files
Communications
Email, SMS, push (unified module)
Chat
Rooms, messages, Socket.io
Router
Client API gateway
Functions
Admin-defined server-side JS
Next steps
- Getting started
Install and run your first stack
- Client vs Admin API
Critical boundary for app code
- MCP setup
Provision schemas with AI agents