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

Deployment Overview

Choose how to run Conduit — local dev, Docker Compose, Kubernetes, or from source.

Choose how to run Conduit based on your environment and operational needs.

Decision matrix

ModeBest forComplexity
Local from sourceContributing to Conduit core or modulesHigh
Docker ComposeLocal dev and small self-hosted stacksLow
Kubernetes / HelmProduction clusters, GitOpsMedium
Container imagesCI/CD, pinning versions, multi-arch pullsReference

Prerequisites (all modes)

  • MongoDB or PostgreSQL for the database module
  • Redis for core bus and realtime
  • Node.js 24+ only when building from source or running the CLI locally

After deployment

  1. Enable modules you need via Admin API or MCP
  2. Provision schemas and config at dev time — not from app runtime
  3. Point applications at the Client API (default port 3000)

Next steps

  • Docker Compose

    Fastest path to a full stack

  • Kubernetes / Helm

    Production clusters

  • Environment variables

    Core and module config

  • Migration from v0.16

    Upgrading an existing deploy

GitOps State Export

Export and import Conduit configs and module resources for config-as-code workflows.

Docker Compose

Run Conduit microservices or standalone with Docker Compose.

On this page

Decision matrixPrerequisites (all modes)After deployment