Expert guidance for deploying FeatBit with Docker Compose across three tiers - Standalone (PostgreSQL only), Standard (PostgreSQL/MongoDB + Redis), and Professional (+ ClickHouse + Kafka). Use when user mentions "docker-compose", "deploy with Docker", "standalone vs standard vs pro", works with docker-compose.yml files, or asks about container configuration, environment variables, or production Docker setup.
Expert guidance for deploying FeatBit with Docker Compose across three tiers - Standalone (PostgreSQL only), Standard (PostgreSQL/MongoDB + Redis), and Professional (+ ClickHouse + Kafka). Use when user mentions "docker-compose", "deploy with Docker", "standalone vs standard vs pro", works with docker-compose.yml files, or asks about container configuration, environment variables, or production Docker setup.
Expert guidance for deploying FeatBit with Docker Compose. This skill provides deployment instructions for all three tiers with links to detailed configuration files.
Core Concepts
FeatBit offers three deployment architectures optimized for different scales:
Tier
Database
Cache
Message Queue
Analytics
Best For
Standalone
PostgreSQL
None
PostgreSQL
PostgreSQL
Low to moderate concurrent connections, moderate API calls, limited event volume
Standard
PostgreSQL/MongoDB
Redis
Redis
MongoDB
Moderate to high concurrent connections & API calls, moderate event volume
Professional
PostgreSQL/MongoDB
Redis
Kafka
ClickHouse
Moderate to high concurrent connections & API calls, high event volume
Quick Selection Guide:
Standalone: Minimal setup, single server, handles low to moderate concurrent WebSocket connections
Standard: Production-ready with caching, handles high concurrent connections with moderate event volume
Professional: Maximum scale for high connections AND high event volume, requires DevOps expertise
Note: Traffic includes both concurrent WebSocket connections from frontend clients and API calls to clients - these have different scales.
# Clone repository (if not already done)
git clone https://github.com/featbit/featbit.git
cd featbit
# Start services using the included docker-compose.yml
docker compose up -d
# Clone repository (if not already done)
git clone https://github.com/featbit/featbit.git
cd featbit
# Start services with PostgreSQL Standard configuration
docker compose -f docker-compose-standard.yml up -d
Option B: MongoDB + Redis
Better for document-oriented workloads
Includes initialization script
# Clone repository (if not already done)
git clone https://github.com/featbit/featbit.git
cd featbit
# Start services with MongoDB configuration
docker compose -f docker-compose-mongodb.yml up -d
Full configurations for both PostgreSQL and MongoDB options
Production setup with managed services
Resource requirements
When to choose Standard vs Professional
Professional Deployment
Enterprise-Scale Architecture:
Kafka for high-throughput messaging
ClickHouse for advanced analytics
Horizontal scalability
Handles millions of events per day
# Clone repository (if not already done)
git clone https://github.com/featbit/featbit.git
cd featbit
# Start all services (Docker Compose handles startup order via depends_on)
docker compose -f docker-compose-pro.yml up -d
# Start all services (Standalone)
docker compose up -d
# Start all services (Standard PostgreSQL)
docker compose -f docker-compose-standard.yml up -d
# Start all services (Standard MongoDB)
docker compose -f docker-compose-mongodb.yml up -d
# Start all services (Professional)
docker compose -f docker-compose-pro.yml up -d
# Stop all services (use same -f flag as used for starting)
docker compose down
# or for non-default configs:
docker compose -f docker-compose-standard.yml down
# View status
docker compose ps
# View logs
docker compose logs -f
# View specific service logs
docker compose logs -f api-server
# Restart service
docker compose restart api-server
# Scale service (Professional tier)
docker compose up -d --scale evaluation-server=3
Maintenance
# Update to latest images
docker compose pull
docker compose up -d
# Clean up
docker system prune -a --volumes
# Backup PostgreSQL
docker compose exec postgresql pg_dump -U postgres featbit > backup.sql
# Backup MongoDB
docker compose exec mongodb mongodump --out /backup --db featbit
When to Choose Each Tier
Choose Standalone If:
✅ Production or non-production with low to moderate traffic:
Low to moderate concurrent WebSocket connections from frontend clients
Moderate API call volume to clients
✅ Low event volume (feature flag usage events & custom events)
✅ Simple single-server deployment preferred
✅ Cost-effective solution for small-scale production use
✅ Quick evaluation of FeatBit
❌ Not Recommended For:
Very high concurrent WebSocket connections
High event volume requiring event streaming
Need for caching layer to improve performance
Choose Standard If:
✅ Very high concurrent WebSocket connections & API calls
✅ Need caching layer (Redis) for improved performance
✅ Moderate event volume (feature flag usage events & custom events)
✅ Production environment requiring reliability
✅ Good balance of complexity vs features
❌ Consider Professional If:
Very high event volume requiring Kafka event streaming
Require real-time analytics at scale with ClickHouse
Need horizontal scalability for data analytics
Choose Professional If:
✅ Very high concurrent WebSocket connections & API calls
✅ Very high event volume (feature flag usage events & custom events)
✅ Need Kafka for high-throughput event streaming
✅ Need ClickHouse for real-time analytics at scale
✅ Have dedicated DevOps resources
✅ Budget for infrastructure
❌ Consider Standard If:
Limited DevOps expertise
Moderate event volume (Redis sufficient for message queue)
