---
title: "Deploy Apache Superset Self-Hosted (Docker)"
description: "Step-by-step guide to self-hosting Apache Superset with Docker Compose. "
---
# Deploy Apache Superset
Enterprise-ready business intelligence web application.
⭐ 59.0k stars
📜 Apache 2.0
🔴 Advanced
⏱ ~20 minutes
## What You'll Get
A fully working Apache Superset instance running on your server. Your data stays on your hardware — no third-party access, no usage limits, no surprise invoices.
## Prerequisites
- A server with Docker and Docker Compose installed ([setup guide](/quick-start/choosing-a-server))
- A domain name pointed to your server (optional but recommended)
- Basic terminal access (SSH)
## The Config
Create a directory for Apache Superset and add this `docker-compose.yml`:
```yaml
# -------------------------------------------------------------------------
# 🚀 Created and distributed by The AltStack
# 🌍 https://thealtstack.com
# -------------------------------------------------------------------------
# Docker Compose for Apache Superset
version: '3.8'
services:
superset:
build:
context: .
dockerfile: Dockerfile
container_name: superset
ports:
- "8088:8088"
environment:
- DATABASE_URL=postgresql://superset:superset@db:5432/superset
- REDIS_URL=redis://redis:6379
depends_on:
db:
condition: service_healthy
redis:
condition: service_healthy
networks:
- superset_net
healthcheck:
test: [ "CMD", "curl", "-f", "http://localhost:8088/health" ]
interval: 30s
timeout: 10s
retries: 3
db:
image: postgres:15-alpine
container_name: superset-db
environment:
POSTGRES_USER: superset
POSTGRES_PASSWORD: superset
POSTGRES_DB: superset
volumes:
- superset_db_data:/var/lib/postgresql/data
networks:
- superset_net
healthcheck:
test: [ "CMD-SHELL", "pg_isready -U superset" ]
interval: 5s
timeout: 5s
retries: 5
redis:
image: redis:7-alpine
container_name: superset-redis
networks:
- superset_net
healthcheck:
test: [ "CMD", "redis-cli", "ping" ]
interval: 5s
timeout: 5s
retries: 5
networks:
superset_net:
driver: bridge
volumes:
superset_db_data:
name: superset_db_data
```
## Let's Ship It
```bash
# Create a directory
mkdir -p /opt/superset && cd /opt/superset
# Create the docker-compose.yml (paste the config above)
nano docker-compose.yml
# Pull images and start
docker compose up -d
# Watch the logs
docker compose logs -f
```
## Environment Variables
| Variable | Default | Required |
|---|---|---|
| `DATABASE_URL` | `postgresql://superset:superset@db:5432/superset` | No |
| `REDIS_URL` | `redis://redis:6379` | No |
## Post-Deployment Checklist
- [ ] Service is accessible on the configured port
- [ ] Admin account created (if applicable)
- [ ] Reverse proxy configured ([Caddy guide](/concepts/reverse-proxies))
- [ ] SSL/HTTPS working
- [ ] Backup script set up ([backup guide](/concepts/backups))
- [ ] Uptime monitor added ([Uptime Kuma](/deploy/uptime-kuma))
## The "I Broke It" Section
**Container won't start?**
```bash
docker compose logs superset | tail -50
```
**Port already in use?**
```bash
# Find what's using the port
lsof -i :PORT_NUMBER
```
**Need to start fresh?**
```bash
docker compose down -v # ⚠️ This deletes volumes/data!
docker compose up -d
```
## Going Further
- [Apache Superset on AltStack Directory](https://thealtstack.com/alternative-to/superset)
- [Apache Superset Self-Hosted Guide](https://thealtstack.com/self-hosted/superset)
- [Official Documentation](https://superset.apache.org)
- [GitHub Repository](https://github.com/apache/superset)