The Managed Control-Plane Tax: Coolify $5 vs Dokploy $4.50/Server vs Deploynix $12 — and the Server Count Where the Meter Comes Back

Dokploy's managed panel is the cheapest per-server deal in self-hosting until you add a second server — at which point Coolify undercuts it, and from the third server on it is the most expensive row in the table all the way to server ten. That single crossover is the most useful number in Deploynix's June 2026 self-hosted-PaaS showdown, and the showdown never computes it. Below is the full fee curve for all three managed control planes, the server count where each one costs more than the box it manages, and the break-even math against the $0 self-hosted panel.

The short version first. Monthly panel fee by server count, entry tiers, September 2026 pricing:

Read the cheapest paid cell in each row: Dokploy at one server by fifty cents, Coolify at two through four, Deploynix at five — for Laravel and PHP teams only — and Coolify again from six on, where Deploynix's Starter cap ends. The rest of this post shows how each vendor's price shape produces that row, where the fee quietly becomes a second infrastructure bill, and when paying it still beats free.

Three vendors, three price shapes​

The three fees look similar — five, four-fifty, twelve — but they are three different pricing geometries, and the geometry is what decides the table above.

Coolify Cloud charges $5 a month for the first two connected servers, then $3 a month per extra server. That is a base-plus-slope shape: the average cost per server falls as you grow, from $5 at one server to $2.50 at two, $2.80 at five, and $2.90 at ten. Founder Andras Bacsai runs the project full-time and has publicly declined venture funding, sustaining it through sponsors and the optional Cloud tier — so the Cloud fee is the project's revenue, not a loss leader, and its shape is deliberate. Note what the fee covers: Coolify hosts and updates the dashboard and its backups, while you still own OS patches, SSH, firewalls, DNS, workload security, and recovery on every connected server.

Dokploy Cloud's Hobby tier charges $4.50 per server per month, and its Startup bundle charges $15 a month for three servers. Do the division before admiring the bundle: $15 over three servers is $5 per server, which is more than three Hobby seats at $4.50. Startup buys you seats, environments, and headroom — not a cheaper unit rate — so the cheapest-fee curve for Dokploy is a straight line, $4.50 times N, at every server count. (One comparison reports $3.50 for additional servers past the first; even at that rate Dokploy loses every row past N=1, so the ordering in the table above doesn't depend on which figure your checkout shows.) Two further facts belong in any Dokploy row: the project is still pre-1.0 (v0.29.x at mid-2026), and since January 2026 its core stays Apache-2.0 while future paid features ship under a separate source-available license.

Deploynix inverts the model. The control plane is the product — a managed, Forge-style Laravel and PHP platform — with a genuinely free tier for a single server and a $12-a-month Starter plan that Deploynix's own writeups scope to up to five servers. Past five servers you need a higher tier, which is why the table above refuses to print a number there: no honest curve extends a flat fee past its cap. The important scope note is that Deploynix provisions native Nginx and PHP-FPM servers, not Docker containers, so its $12 row simply doesn't apply to a polyglot team shipping Go, Rust, or arbitrary images.

Put the three shapes together and the crossover findings fall out. Dokploy's straight per-server line starts ten percent below Coolify's $5 base and then loses $1.50 of ground per added server — the gap is $4 at two servers, $8.50 at five, $16 at ten. Deploynix's flat $12 sits above Coolify's curve from N=2 through N=4, dips below it exactly at N=5 ($12 versus $14), and then exits the entry-tier comparison entirely. There is no single cheapest managed panel; there is a cheapest panel per server count, and it changes three times on the way to ten.

The server count where the meter comes back​

Fees in isolation mislead. Anchor them to the box they manage: a Hetzner CX23-class VPS — 2 vCPU, 4 GB RAM, 40 GB NVMe, 20 TB of transfer — which lists at €5.49 a month (about $6.40) after Hetzner's June 2026 adjustment. Call it $6 a box and ask the question the TODO framing demands: at what server count does the monthly panel fee cost more than adding another box to the fleet?

For Dokploy, the answer is server two: two Hobby seats cost $9, which already exceeds a $6 box. For Coolify, it is server three: $8 of panel fee against a $6 box. For Deploynix's paid tier, the meter is back immediately — $12 is two boxes' worth from the first paid month, though the free tier means a one-server Laravel side project never pays it at all.

The same anchor expressed as a share of the box bill is harsher. Dokploy's fee is 75 percent of the box bill at every server count — $4.50 of panel on every $6 of compute, whether you run one server or ten. That is the per-server meter at its purest: a dashboard surcharge of three-quarters on infrastructure. Coolify's share starts at 42 percent for a two-server fleet ($5 on $12 of boxes) and drifts toward a 50 percent ceiling it never crosses ($29 on $60 at ten servers). Deploynix's $12 equals the entire box bill of a minimal two-box fleet and falls to 40 percent by five boxes ($12 on $30).

Total cash per month for a five-box fleet of $6 boxes makes the ranking tangible: $44 on Coolify Cloud, $52.50 on Dokploy, $42 on Deploynix for a Laravel team, $30 self-hosted. The spread between the cheapest and priciest managed option is only about $10 — but the spread between any of them and $0 is the section below, and it is measured in time, not dollars.

One sensitivity check before moving on: bigger boxes shrink every fee share. Deploynix's own Laravel writeups typically assume $12–$24 boxes rather than $6 ones; on five $24 boxes ($120 of compute), the $12 Starter fee is a 10 percent surcharge, not 40. Conversely, Hetzner's sticker prices exclude VAT and the IPv4 add-on, which add roughly $1–2 per box in practice. Neither adjustment changes the ordering — but if your fleet runs large boxes, the whole debate matters less, and if it runs small ones, the fee is a bigger fraction of every row.

When paying beats $0​

The self-hosted column reads $0 at every server count, which is true in cash and false in total cost. Running the panel yourself means applying panel updates, keeping Traefik and Let's Encrypt healthy, verifying container-database backups actually restore, and debugging the Docker layer when a deploy wedges — call it one to three hours a month for a quiet fleet, consistent with what teams report for Coolify v4's fast-moving releases. The managed fee buys back those hours. The break-even question is what an hour is worth to you:

Any team paying loaded labor rates of $50–150 an hour clears every row of this table several times over: a $5 fee is four minutes of a $75-an-hour engineer's month, and even the $45 ten-server Dokploy row is thirty-six minutes. For teams, the managed panel is not a tax; it is the cheapest on-call rotation in the industry, and the fee-curve debate above is about which bargain to take.

The $0 column wins exactly one audience: the solo founder who prices midnight hours at zero. If your ops time is genuinely free — a side project, a learning box, a pre-revenue weekend — no fee curve beats self-hosting, and the cheapest paid cell in each row is irrelevant. That is also the audience most likely to outgrow it: the day the side project has users, the pager math flips, and the fee that looked like a tax starts looking like four minutes.

What the fee doesn't buy​

Three scope limits keep the fee math honest, because each one is a bill the table above doesn't show.

First, every vendor manages the panel — none manages your account with the VPS provider. The servers live in your Hetzner, DigitalOcean, or AWS account, the provider bill is yours, and when the provider has a bad day, the outage is an outage on your boxes no matter whose dashboard shows it red. Coolify's own docs-adjacent coverage is explicit that Cloud customers still handle OS updates, SSH, firewalls, DNS, application data, workload security, and recovery on connected servers. Price the fee as dashboard insurance, not infrastructure insurance.

Second, the substrates differ in ways the fee hides. Dokploy's multi-server story is Docker Swarm-native — smooth for stateless replicas, but Swarm has been in maintenance mode for years, so a ten-node Dokploy future rests on a frozen orchestrator. Coolify's multi-server model is SSH-attached remotes with per-server deploys and no cluster scheduler, which is simple until placement decisions outgrow one human's head. Deploynix sidesteps containers entirely, which is a feature for Laravel teams and a disqualifier for everyone else. None of these appears in a price table; all of them appear in year two.

Third, the comparison itself has a ceiling. Past roughly ten servers, the question stops being which per-server dashboard fee is cheapest and starts being whether a single-box-panel architecture is the right control plane at all — fleet provisioning, declarative machine lifecycle, and scheduled drift reconciliation are a different product category from a panel that SSHes into boxes you created by hand. The fee curves in this post are the right tool for fleets of one to ten; past that, they are measuring the wrong thing precisely.

The decision in three lines​

For a solo polyglot hacker, self-host Coolify or Dokploy free and revisit the fee the day someone pages you. For a team running two to ten polyglot servers, Coolify Cloud's base-plus-slope curve is the cheapest paid panel at nearly every count — Dokploy's per-server line only wins the first row. For a Laravel or PHP team at three to five servers, Deploynix's flat $12 is the cheapest cash answer in the comparison, provided you never need it to ship a container. And for every shape: compute the fee as a share of your box bill before you sign, because a dashboard that costs 75 percent of the compute it manages has quietly become the meter you self-hosted to escape.

Bex.co is the open-source, AI-native Render alternative — push a git repo, get a running HTTPS service on machines you own. Star the repo on GitHub or deploy your first app today.