Put the binary on a server
We send you one file. Copy it to any Linux box with Docker and start it — it creates its own database, its own network and its own certificates on first boot.
Self-hosted delivery, one binary
MELD deployr turns one ordinary server into a deployment platform. Push a branch and it builds, health-checks and swaps your app into place — with TLS, rollback and zero dropped requests. No cluster. No agents. No YAML sprawl.
One static binary · SQLite · Docker · runs on a 2 GB VPS
From nothing to serving
There is no control plane to stand up and nothing to install on the machine beyond Docker. The binary is the platform: edge proxy, git remote, build runner, scheduler and dashboard, in one file.
We send you one file. Copy it to any Linux box with Docker and start it — it creates its own database, its own network and its own certificates on first boot.
Name it, give it a hostname. deployr requests the certificate the first time somebody asks for that name.
Link the directory once, then push. That runs your pipeline, builds an image, starts the new version beside the old one and swaps traffic when it is healthy.
deployr push
The part everyone gets wrong
Your running version keeps serving while the new one starts, gets probed and proves itself. Traffic moves only when it passes — and moves back just as fast if you change your mind.
Step 01
Two replicas in the blue slot, behind deployr's edge. The certificate is already issued and renewing itself. This is a normal Tuesday.
Step 02
The pipeline runs, the image builds, and the green slot comes up on the same network — with the same volumes, the same environment, and none of your traffic.
Step 03
deployr probes every new replica until it answers correctly. A version that never becomes healthy never gets a single request — the deployment fails, and v41 carries on as though nothing happened.
Step 04
The routing table is swapped atomically. Requests already in flight finish against v41; new ones go to v42. In our own tests, 7,134 requests crossed this moment without a single failure.
Step 05
deployr rollback puts v41 back the same way it arrived — health-gated, drained, atomic. The old image is still on the machine, so it takes seconds, not another build.
Built from real work
deployr was not designed in the abstract. Every capability here exists because a real application needed it on a Tuesday afternoon.
The whole platform
A proxy, a CI runner, a git server, a certificate manager, a scheduler and a dashboard. One process, one file to back up, one thing to upgrade.
Voices
Licensing
MELD deployr is a commercially licensed product, developed and supported by MELD d.o.o. It is not a download you wrestle with alone: tell us what you are running and we will get you licensed, installed and deploying — usually in an afternoon.
Whether that is a dozen client sites, one product with tenants, or the internal tools nobody has had time to host properly, the conversation starts the same way.