Alpina Tech sets up and manages Dokku infrastructure for teams that want the simplest path from Heroku to self-hosted. Dokku runs on a single server, uses Heroku buildpacks natively, and deploys apps with git push β no Docker knowledge required, no web dashboard to learn.
Dokku Installation & Server Hardening
We install Dokku and prepare the server for production workloads:
- Dokku installation on Ubuntu (Hetzner, DigitalOcean, Linode, or any VPS)
- Nginx configuration with automatic Letβs Encrypt SSL via the letsencrypt plugin
- Global domain setup and per-app subdomain routing
- SSH key management for developer access and git-push deployments
- Server hardening β firewall rules, fail2ban, unattended security updates
Application Deployment & Buildpacks
Dokkuβs buildpack system makes deployment familiar for Heroku users:
- Heroku-compatible buildpacks β Node.js, Python, Ruby, Go, PHP, Java deploy without Dockerfiles
- Custom Dockerfile deployments when buildpacks donβt fit your stack
- Environment variable configuration per app via
dokku config:set - Process types via Procfile β web, worker, and cron processes on the same app
- Zero-downtime deploys with health checks and container rollback
Plugin Ecosystem & Service Provisioning
Dokkuβs plugin system replaces Heroku add-ons with self-hosted equivalents:
- dokku-postgres β managed PostgreSQL instances with backup/restore commands
- dokku-redis β Redis for caching, sessions, and job queues
- dokku-mysql / dokku-mongo β additional database options as needed
- dokku-letsencrypt β automatic SSL certificate provisioning and renewal
- dokku-cron-restart / custom cron β scheduled tasks alongside your apps
- Service linking β connect databases to apps with automatic environment variable injection
Migration from Heroku
Dokku is the closest self-hosted Heroku equivalent. We handle the transition:
- Buildpack compatibility verification β most Heroku apps deploy on Dokku without changes
- Heroku add-on mapping to Dokku plugins (Heroku Postgres β dokku-postgres, etc.)
- Environment variable transfer and secrets management
- Database migration with
pg_dump/pg_restoreand data verification - DNS cutover and SSL configuration on the new server
Nginx & Networking Configuration
Dokku uses Nginx as its reverse proxy. We customize it for production needs:
- Custom nginx templates for WebSocket support, request size limits, and timeouts
- Per-app nginx configuration overrides without affecting other apps
- HTTP/2 and gzip compression for static assets
- Rate limiting and IP whitelisting for admin endpoints
- Cloudflare integration for CDN and DDoS protection in front of Dokku
We cover advanced networking and monitoring beyond Dokkuβs built-in capabilities.
How We Approach Dokku Projects
Server Sizing Dokku runs well on modest hardware. We typically recommend starting with 2β4 GB RAM for 3β8 apps. We calculate memory per process type and set swap as a safety net.
Plugin Selection We install only the plugins you need β databases, SSL, cron. Dokkuβs strength is minimalism. Every plugin adds a maintenance surface, so we keep the footprint tight.
Heroku-Compatible Workflow
Your developers keep using git push to deploy. Procfile, buildpacks, and environment variables work identically. The migration from Heroku is often transparent to the dev team.
Backup & Recovery
We configure automated database exports, document restore procedures, and test recovery. For Dokku, this means scripted dokku postgres:export and server snapshot schedules.
Technology Stack with Dokku
Buildpacks & Runtimes
- Heroku buildpacks β Node.js, Python, Ruby, Go, PHP, Java, Scala
- Custom Dockerfiles β for runtimes not covered by buildpacks
- Procfile-based process management β web, worker, release, cron
Databases & Services (via Plugins)
- dokku-postgres β PostgreSQL with backup, restore, and cloning
- dokku-redis β in-memory caching and pub/sub
- dokku-mysql, dokku-mongo β relational and document stores
- dokku-letsencrypt β automated TLS certificates
Hosting Providers
- Hetzner Cloud β EU default, β¬4β7/month for a capable Dokku server
- DigitalOcean β one-click Dokku droplet available
- Linode, Vultr β alternative VPS providers
- Any Ubuntu 22.04+ server β Dokku has no provider lock-in
Business Benefits
- Closest Heroku migration path β Dokku uses Heroku buildpacks natively. Most Heroku apps deploy on Dokku with zero code changes, making migration a server setup task, not a rewrite.
- Single-server simplicity β one VPS runs Dokku, your apps, and your databases. No cluster to manage, no orchestrator to configure. Ideal for teams running 3β15 services.
- CLI-driven, scriptable β every Dokku operation is a shell command. Automation, backups, and provisioning integrate into any CI/CD pipeline or cron job without APIs or dashboards.
- Minimal resource overhead β Dokku itself uses negligible RAM. Almost all server resources go to your applications, unlike heavier PaaS tools that consume significant memory for their own processes.
- Battle-tested stability β Dokku has been in active development since 2013. The codebase is mature, well-documented, and trusted by thousands of production deployments.
- No learning curve for Heroku teams β
git push dokku main,dokku config:set,dokku ps:scaleβ the commands mirror Herokuβs CLI. Developers are productive from day one.
Page Updated: 2026-03-10






