Dokku
Self-hosted PaaS
A lightweight self-hosted PaaS that uses Git pushes, Docker/buildpacks, plugins, and a single server to deploy apps.
Starter cost
Paid entry
Card required
No
Always-on
Supported
Billing risk
low
Category
Self-hosted PaaS
Cost range
Free open-source software; pay for the VM, storage, backup, and bandwidth you choose
Free tier details
Dokku does not charge for the platform itself, but it is only as cheap as the server and add-ons you run.
Database fit
Dokku fits Postgres, Redis, MySQL workloads, with the exact storage, compute, and quota story depending on the current plan.
- Best database use
- Heroku-like self-hosting, single-server apps, developers comfortable with SSH
- Check before launch
- Verify backups, storage quotas, connection limits, regions, and whether a separate database provider is needed.
Stress-test Dokku before you pick it
Answer a short provider-specific form, then run the full bill-risk simulator with your scenario prefilled.
Fit summary
Dokku is strongest when you want PaaS-like deploys but still want to control the server and total hosting bill. It is not hands-off: operations quality depends on how well you manage the underlying machine.
Best fit
Heroku-like self-hosting, single-server apps, developers comfortable with SSH
Deployment model
Self-hosted control plane running on your own server or cloud account.
Operations owner
You own server updates, backups, monitoring, incident response, and capacity planning.
Billing model
The platform software can start at $0, but the real bill is the server, storage, backups, domains, and bandwidth; it has a no-card starter path.
Runtime fit
Node.js API, Python FastAPI, Docker app, Static frontend
Data fit
Postgres, Redis, MySQL
Budget fit
Under $5, Under $10, Under $25, Custom
Region strategy
Runs wherever your chosen server or cloud provider is located.
Choose this if
- Heroku-like self-hosting
- Simple PaaS model
- You want a beginner path that can start without adding a card.
Think twice if
- Single-server operations
- Plan for server updates, backups, SSL renewal, plugin maintenance, and capacity limits.
- You need a provider to handle patching, backups, and incidents for you.
Decision checks
Use these notes as a launch checklist, not a final pricing promise. Verify live provider limits before moving real users.
Strengths
- Simple PaaS model
- large plugin ecosystem
- low software cost
Watch outs
- Single-server operations
- manual security and backup work
- Plan for server updates, backups, SSL renewal, plugin maintenance, and capacity limits.
Before launch
- Confirm the no-card starter path still exists before relying on it.
- Confirm the minimum paid plan covers your expected app, database, and bandwidth usage.
- Verify database storage, backups, connection limits, and whether the database is bundled or external.
- Confirm always-on services, workers, and cron jobs are included in the plan you choose.