Your apps on your own server.
Push to GitHub. Dokkr builds it, ships it with zero downtime and serves it over HTTPS, on your own server. Many small apps share one box.
- git push deploys
- Zero-downtime swaps
- HTTPS by default
- Postgres per app
- Locked nightly backups
How it works
Dokkr uses your Dockerfile. Without one, it detects Node, PHP, Python, Go and static sites and builds them for you.
- 1
Connect GitHub
Install the Dokkr GitHub App on a repository. Your code stays as it is.
github.com/you/combobulator - 2
Push
Every push to your branch starts a deploy. Or call the deploy hook from your own CI.
git push origin main - 3
Live with HTTPS
Dokkr builds on your server and moves traffic to the new version. Earlier versions stay for rollback.
https://combobulator.app
10 apps, one €7 server
Small apps don't need a server each. Dokkr runs every app in its own container with a memory and CPU limit, behind one shared web server that handles HTTPS. Each app gets its own Postgres database on the same server, and a folder that survives deploys.
- combobulator212 MB
- invoice-bot236 MB
- quiz-night182 MB
- recipe-box148 MB
- field-notes131 MB
- plant-water96 MB
- tally88 MB
- habit-log74 MB
- guestbook64 MB
- link-shrink58 MB
The apps use 1.3 GB of the server's 4.0 GB. The rest is room to grow.
Example price, small server with backups: €7.07/mo, excluding VAT.
What's included
The parts you would otherwise set up by hand, on every server.
- Automatic HTTPS
- Certificates for every domain, renewed for you.
- Security patches
- Every server installs security updates on its own.
- Firewall and SSH keys
- A default firewall and your SSH keys. No root passwords.
- Locked database copies
- Every night, each database goes encrypted to a locked bucket. Nobody can delete a copy for 30 days.
- Live logs and rollback
- Watch builds and app logs as they happen. Roll back to any earlier deploy.
- Per-app limits
- Memory and CPU limits per app, so one app cannot slow down the rest.
- Env vars and a release command
- Paste a .env file. Run migrations before traffic moves to the new version.
Questions
Short answers to the usual ones.
Where do my servers run?
In data centers in Germany, Finland, the US and Singapore. You pick the location and the size when you launch a server, and you see the monthly price before it starts.
What can I deploy?
Anything with a Dockerfile. Without one, Dokkr detects Node, PHP, Python, Go and static sites and builds them. Web apps, APIs, bots and background workers all fit.
Can I SSH in?
Yes. Every server is a normal Ubuntu server with your SSH key on it, and the default firewall allows SSH. Dokkr never sets a root password.
What if I stop using Dokkr?
Nothing is locked in. Your code stays in your Git repository, apps run as standard Docker containers, and your databases are plain Postgres that you can copy out with pg_dump at any time.
What about my domains?
They stay at your registrar. Point an A record at your server and add the domain to an app. Dokkr gets the HTTPS certificate and renews it.
How do backups work?
Every night Dokkr dumps each app database, encrypts it and uploads it to an Object Storage bucket with Object Lock. For 30 days nobody can delete or change a copy, not even with your own keys. You can also turn on daily backups of the whole server.