Dokku vs Firebase
Dokku vs Firebase compared for European indie developers and small startups. Pricing, EU jurisdiction, GDPR posture, and why Runsite (an EU-registered PaaS in Frankfurt) is worth a look.
Dokku vs Firebase: quick answer
Dokku and Firebase both offer Git-push deploy workflows, but they differ where it counts. Firebase starts around pay-as-you-gometered. Dokku (self-hosted) and Firebase (a US Google service) sit on different sides of the data-residency question. For European teams that need GDPR-compliant hosting in Frankfurt with predictable EUR billing and a permanent free tier, Runsite is the EU-native alternative to both.
// dokku problems → runsite solutions
Common Dokku frustrations. Sound familiar?
Every Dokku frustration, solved.
Dokku problem
"My Dokku server rebooted and everything went down"
Dokku is single-node. One VPS failure takes all your apps, databases, and SSL certificates offline.
Runsite solution
Managed multi-node infrastructure
Your apps run on redundant infrastructure with auto-failover. No single machine can take everything down.
Dokku problem
"I spend weekends patching the OS"
Self-hosting means you're responsible for security patches, kernel updates, and disk space monitoring.
Runsite solution
Fully managed: we handle the ops
Push code, get a URL. OS updates, security patches, and monitoring are our problem, not yours.
Dokku problem
"Database backups? I forgot to set those up"
Dokku databases are plugins running on the same host. Backups require manual cron setup.
Runsite solution
Auto-backups on managed PostgreSQL
Automated daily backups with point-in-time recovery. Your data is safe without any setup on your part.
// comparison
Runsite vs Dokku
Side-by-side. No marketing fluff, just facts.
| Feature | Runsite | Dokku |
|---|---|---|
| Infrastructure | ✓ Fully managed, multi-node | Single VPS, you manage |
| High Availability | ✓ Multi-node, auto-failover | ✗ Single node = single point of failure |
| Managed PostgreSQL | ✓ From €5/mo, auto-backups | ✗ Runs on same host, manual backups |
| SSL Certificates | ✓ Automatic | Via plugin (dokku-letsencrypt) |
| Spending Limits | ✓ Hard cap + Telegram alerts | ✗ VPS bill can spike |
| Deploy from Git | ✓ | ✓ (Buildpacks) |
| Docker Support | ✓ | ✓ |
| Total Cost (small app) | €5/mo | $5-10/mo VPS + your time |
// the other side
What about Firebase?
Firebase locks you into Google's ecosystem. Runsite gives you open-source tools, EU hosting, and full data ownership.
// firebase problems → runsite solutions
Common Firebase frustrations. Sound familiar?
Every Firebase frustration, solved.
Firebase problem
"Firebase locks me into Google"
Firestore, Cloud Functions, Firebase Auth: proprietary services that don't work outside Google Cloud.
Runsite solution
Open standards everywhere
PostgreSQL, Docker, S3. Standard tools that work on any platform.
Firebase problem
"GDPR compliance is complicated"
Firebase requires a Google Cloud DPA, data residency configuration, and careful SDK setup for EU compliance.
Runsite solution
GDPR by default
EU entity. EU servers. No configuration needed. Compliant from day one.
Firebase problem
"Costs spike with traffic"
Firebase charges per document read/write. A viral moment can mean a massive surprise bill.
Runsite solution
Fixed pricing + spending caps
Predictable monthly bills with hard limits. Traffic spikes don't break the bank.
// comparison
Runsite vs Firebase
Side-by-side. No marketing fluff, just facts.
| Feature | Runsite | Firebase |
|---|---|---|
| Vendor Lock-in | ✓ Open standards, Docker | ✗ Proprietary SDKs |
| EU Data Centers | ✓ Frankfurt (eu-central) | ✓ europe-west regions |
| GDPR Compliance | ✓ EU entity, full compliance | Complex DPA required |
| Backend Hosting | ✓ Full containers | Cloud Functions only |
| Database | ✓ Standard PostgreSQL | Firestore (proprietary) |
| Pricing Transparency | ✓ Fixed plans | Pay-per-read/write |
// pricing, side by side
Dokku vs Firebase: what each actually costs
Spark plan is free with fixed quotas. Exceeding any quota forces an upgrade to the metered, uncapped Blaze plan.
Firebase's free Spark tier is great for prototypes, but the jump to uncapped Blaze billing and per-operation Firestore pricing make it one of the riskiest platforms for unexpected bills, there is no hard spending cap, only after-the-fact alerts.
Pricing verified June 2026. Check the official pricing page of each provider for current rates.
// in-depth comparison
How Dokku and Firebase each compare to Runsite
Dokku vs Runsite
For over a decade, one tool has been the default answer for developers who wanted Heroku ergonomics on their own hardware: Dokku. It was the original open-source Heroku alternative, running on a single VPS with buildpack and Dockerfile support and the familiar git-push deployment workflow, no PaaS bill attached.
Here is the catch. Dokku is single-node. Your apps, databases, SSL certificates, and routing all live on one machine. Reboot that VPS and everything goes offline at once. Backups mean hand-writing cron jobs. Every OS patch and security update is on you.
Runsite keeps the same git-push workflow but moves it onto managed multi-node infrastructure with automatic failover, isolated managed PostgreSQL with daily backups, and automatic SSL, all in EU data centers. Developers who have felt the stress of a single-node failure, or who are done spending weekends on server maintenance, get that deployment simplicity back with managed reliability and a permanent free tier.
Firebase vs Runsite
Ship a prototype over a weekend, and Firebase feels like magic. Google's all-in-one backend was built for exactly that speed.
Firestore, Firebase Auth, Cloud Messaging, and Hosting form a tightly integrated ecosystem, and the free Spark plan covers small projects comfortably. The real-time capabilities are genuinely useful for mobile and web apps. The catch shows up later. Everything that made the fast start possible becomes vendor lock-in: Firestore's proprietary query model, Firebase-specific auth SDKs, and Cloud Functions tied to Google Cloud mean your code cannot run elsewhere without substantial rewrites. GDPR compliance adds its own tax, requiring a Google Cloud DPA, careful region configuration, and ongoing vigilance about which services process data where.
Runsite uses standard PostgreSQL, Docker containers, and S3-compatible storage, all portable to any other provider. Teams that have outgrown Firebase's proprietary model, or that need straightforward EU compliance without navigating Google's data processing agreements, get a cleaner foundation. You bring your own auth and realtime layer, but you own every piece of your stack.
// why consider runsite
Beyond Dokku and Firebase
EU PaaS for indie developers and small European startups. One region: Frankfurt.
EU-First Infrastructure
While Dokku and Firebase default to US markets, Runsite is built exclusively for European developers. Frankfurt (eu-central) region, EU entity, EU jurisdiction, with no transatlantic transfers.
Real GDPR Compliance
EU-registered entity. Your data is governed by European law. No US jurisdiction, no CLOUD Act.
Predictable Pricing
No per-invocation charges, no surprise bills. Fixed plans with hard spending caps and Telegram alerts.
Common Questions
FAQ
Which is better for EU hosting, Dokku or Firebase?
Dokku (self-hosted) has the stronger EU-residency story here, while Firebase is a US Google service and stays subject to the US CLOUD Act even in its European regions. If jurisdiction is your deciding factor, that gap matters. Runsite is EU-native as well, running exclusively in Frankfurt (eu-central) under an EU entity, and adds fully managed deploys, predictable EUR billing, and a permanent free tier — so you get European residency without giving up developer experience.
Which has the better free tier, Dokku or Firebase?
Free tiers on both Dokku and Firebase change frequently and tend to share the same catch: compute that sleeps after inactivity, bandwidth or build-minute caps, or trial credits that expire after a fixed window. They are fine for quick experiments but rarely sustainable for an always-on hobby project. If a permanent free tier matters, read the current terms carefully. Limits are often buried in the pricing footnotes. Runsite takes the opposite approach: a free tier with no credit card and no expiry, designed to keep small projects online indefinitely rather than nudging you onto a paid plan.
Is Dokku or Firebase GDPR-compliant?
Dokku (self-hosted) can keep data under European jurisdiction, whereas Firebase, as a US-incorporated provider, remains subject to the US CLOUD Act regardless of the region you pick — a common sticking point in DPO review. For workloads where EU jurisdiction is a hard requirement, an EU-registered provider removes the ambiguity. Runsite keeps data in Frankfurt under an EU entity, so GDPR posture is the default rather than a per-region configuration exercise.
What is the cheapest way to deploy a side project, Dokku or Firebase?
For a single small service, both Dokku and Firebase can look inexpensive on paper. The headline price rarely matches the real bill. Per-service billing, metered bandwidth, build minutes, and add-ons for databases or key-value stores stack up quickly, and neither platform offers a hard spending cap to stop a surprise invoice. The cheapest predictable option is one with fixed monthly pricing and an enforced ceiling. Runsite bills in EUR from €5/month with hard spending caps and Telegram alerts, plus a permanent free tier, so a side project stays cheap by design, not by careful monitoring.
// explore alternatives
Try the European Alternative
Skip the Dokku vs Firebase debate. Deploy on Runsite.
Start Free on Runsite →