Skip to main content
Deploy Proliferate in your own infrastructure for complete control over your data and security.

​
What You Get

Self-hosted Proliferate includes:
  • Web App - Next.js frontend and API
  • Gateway - WebSocket server for real-time streaming
  • Worker - Background job processor
  • PostgreSQL - Database for metadata
  • Redis - Job queue and caching
  • LLM Proxy (optional) - Secure API key routing for sandboxes

Local setup

Run Proliferate locally with Docker Compose.

Environment variables

Minimal required config, plus optional features.

​
Policy: What We Self-Host vs. External

Proliferate is fully self-hostable for the core application, but sandbox execution and model inference remain external services by default. For enterprise deployments, we can run these inside your VPC/BYOC environment.

​
Minimal Setup (Self‑Host)

For a fast local setup, you only need:
  • ANTHROPIC_API_KEY
  • Modal sandbox credentials (default provider)
For local dev, .env.example provides reasonable defaults for database, Redis, URLs, and feature flags.
Before production deployment, replace all defaults with secure values and set your public URLs. See Self‑hosting → Environment Variables for the full checklist.

​
Default Provider: Modal

Use Modal by default. You can switch to E2B if preferred.

​
Optional Features (Self‑Host)

If you enable these, additional configuration is required:
  • Integrations (Nango)
  • Email verification
  • OAuth providers (GitHub/Google)
  • Slack
  • GitHub App (required for private repo access)
  • LLM proxy
Details and required variables are listed in Self‑hosting → Environment Variables.
LLM proxy is optional. If LLM_PROXY_URL is unset, sandboxes call Anthropic directly using ANTHROPIC_API_KEY. If you enable the proxy, it must be publicly reachable by your sandbox provider.
For a full, authoritative list (including cloud‑only variables), see ENVIRONMENT.md or Self‑hosting → Environment Variables.

​
External Dependencies

Self-hosted Proliferate relies on these external services:
ServicePurposeRequired
Sandbox provider (Modal or E2B)Sandbox execution environmentYes
AnthropicClaude AI modelsYes
GitHub AppPrivate repo accessRequired
OAuth ProviderUser authenticationOptional
Sandbox providers (Modal/E2B) run outside your Proliferate cluster by default. For enterprise customers, we can deploy the sandbox layer inside your VPC/BYOC environment.

​
Deployment Options

AWS EC2

Single instance deployment with Docker Compose

Azure

Deploy on Azure VMs or Container Apps

GCP

Deploy on Google Cloud Compute Engine

Local

Run locally for development and testing
Docker Compose is the primary supported deployment path today. Pulumi templates for AWS/GCP/Azure are in progress for one‑command infrastructure setup.

​
Quick Start

The fastest way to get started: 
# Clone the repository
git clone https://github.com/proliferate-ai/proliferate.git
cd proliferate

# Configure environment
cp .env.example .env
# Edit .env with your API keys

See `/ENVIRONMENT.md` for required vs optional variables by deployment mode.

# Start with pre-built images
docker-compose -f docker-compose.prod.yml up -d

​
Architecture

┌─────────────┐     ┌─────────────┐     ┌─────────────┐
│   Browser   │────▶│   Web App   │────▶│  PostgreSQL │
└─────────────┘     └─────────────┘     └─────────────┘
       │                   │
       │            ┌──────┴──────┐
       │            ▼             ▼
       │     ┌─────────────┐ ┌─────────────┐
       └────▶│   Gateway   │ │   Worker    │
             └─────────────┘ └─────────────┘
                   │               │
                   ▼               ▼
             ┌─────────────┐ ┌─────────────┐
             │    Redis    │ │  E2B Cloud  │
             └─────────────┘ └─────────────┘

​
Requirements

​
Minimum Hardware

  • 2 vCPUs
  • 4 GB RAM
  • 50 GB storage
  • 4 vCPUs
  • 16 GB RAM
  • 100 GB SSD storage

​
Software

  • Docker 20.10+
  • Docker Compose 2.0+

​
Next Steps

Authentication

Configure OAuth providers or local auth

Slackbot

Set up Slack integration