Dora NodaVenture capitalists have a type in the deploy-platform market, and it is not subtle. They will write a $100 million check to a hosted cloud that owns the whole stack, a $22 million check to a platform that manages your cloud for you — and nothing at all to the software that lets you own everything yourself. That pattern is the real story behind Northflank's $22.3 million raise, and it tells a team choosing infrastructure in 2026 exactly where each model sits.
This post maps the money across hosted, bring-your-own-cloud, and fully self-hosted models with verified numbers, works out what Northflank's BYOC middle position concretely costs and controls, and names what you still rent when you buy it.
The $22.3M headline, with one date correction
First, the record, because several roundups get it wrong: Northflank announced the $22.3 million in November 2024, not 2026 — a $16 million Series A led by Bain Capital Ventures plus a $6.3 million seed led by Vertex Ventures US, with Kindred Ventures, Tapestry VC, Pebblebed, and Uncorrelated Ventures participating, which together with its $2.6 million 2020 seed brings the company's total to roughly $25 million.
The date matters less than the thesis, which has only sharpened since. Northflank's pitch is bring-your-own-cloud: workloads deploy into the customer's own AWS, GCP, Azure, or bare-metal account instead of a shared multi-tenant one, while Northflank operates the control plane that provisions, scales, and observes them. At the time, the company said the money would expand cloud-provider support, add regions, build 24/7 enterprise coverage — and develop a self-deployable control plane for enterprise customers who need maximum control. That last item is worth bookmarking; we will come back to it.
The funding map: follow the money across three models
Line up the verified venture rounds behind each deployment model and the shape is unmistakable:
| Model | Company | Verified raise | Total disclosed |
|---|---|---|---|
| Fully hosted | Railway | $100M Series B, Jan 2026 (TQ Ventures) | ~$124M |
| Fully hosted | Render | $50M Series B, Jun 2023 (Bessemer) | ~$77M |
| BYOC middle | Northflank | $16M Series A + $6.3M seed, Nov 2024 | ~$25M |
| BYOC enabler | Nuon | $16.5M seed + Series A, Dec 2024 (M12, Uncork, Redpoint) | $16.5M |
| Fully self-hosted | Coolify and peers | None — revenue- and sponsor-funded | $0 VC |
Two caveats before the conclusion. One is vintage: a 2023 Series B, a late-2024 Series A, and a 2026 Series B were raised in different rate environments, so read the shape, not the precision. The other is that Nuon is adjacent rather than identical — it lets SaaS vendors offer BYOC to their own customers, while Northflank is the BYOC platform itself. Both still bet that "your cloud account, our control plane" is where enterprise infrastructure budgets are heading.
The shape is the point: on the order of $200 million into platforms whose control plane you rent by the month, around $40 million into the BYOC middle, and zero venture dollars into the own-everything end, where Coolify funds development from Coolify Cloud subscriptions and sponsors. Venture money follows recurring control-plane revenue. Software you run yourself, on machines you own, has no meter to invest in — which is exactly why that end of the spectrum is built as open source.
What BYOC concretely buys — and bills
Northflank has run production BYOC since 2019, so the model is well-defined by now. You connect your own cloud accounts; workloads land in your VPCs across a claimed 600 BYOC regions spanning AWS, GCP, Azure, Oracle, CoreWeave, Civo, and assorted neoclouds; teams with existing clusters can attach them via bring-your-own-Kubernetes, including on-premises and bare metal. Runtime and workload data stay in your account, while Northflank hosts the control-plane metadata and serves the developer surface — builds, deploys, preview environments, databases, autoscaling — on top.
The bill splits the same way the architecture does. Your cloud provider invoices the underlying infrastructure at its standard rates, and Northflank meters a platform fee on top: $0.01389 per vCPU-hour and $0.00139 per GB-hour. Run that across a full 730-hour month for three representative footprints:
| Footprint | Platform fee math | ≈ Monthly fee |
|---|---|---|
| Small: 2 vCPU / 4 GB | (2 × $0.01389 + 4 × $0.00139) × 730 | ~$24 |
| Typical team: 4 vCPU / 16 GB | (4 × $0.01389 + 16 × $0.00139) × 730 | ~$57 |
| Larger: 8 vCPU / 32 GB | (8 × $0.01389 + 32 × $0.00139) × 730 | ~$114 |
Two things to notice. First, the fee is the surcharge, not the total: the VMs underneath still bill at your provider's standard rates, which for a small cluster commonly make up the larger half of the combined spend. BYOC saves you nothing on compute — it converts the control plane from a build-it-yourself project into a metered line item.
Second, the contrast with the own-everything end is stark: Coolify Cloud starts at $5 per month for two servers, because there is no per-vCPU meter running at all. The $24–$114 range above is the price of renting the plane instead of running it.
For teams with cloud commits or credits to burn, the split billing is genuinely the feature: BYOC lets you spend down an enterprise discount or startup credits on the infrastructure half while paying list price only on the platform half. That is a real audience — and a real venture thesis.
What you still rent in the middle
Owning the account is not owning the platform. In Northflank's standard BYOC configuration, the control plane is theirs: they host its metadata, ship its upgrades, set its roadmap, and retain ongoing operational access to clusters it manages. Your workloads keep running on your VMs if that tether degrades, but deploys, scaling decisions, and every dashboard click flow through infrastructure you neither run nor can fork. That is a rational trade for most teams — it is also, structurally, a subscription to someone else's uptime and priorities.
The most honest evidence for this reading comes from Northflank itself. The company's enterprise tier offers a forward-deployed control plane for, in its own words, requirements that cannot use Northflank's managed control plane — and as far back as the 2024 funding announcement, part of the raise was earmarked for a self-deployable control plane for enterprise customers. When the BYOC vendor's own roadmap treats "the customer runs the control plane" as the top-end offering, the middle position is defined by its absence: standard BYOC rents you the plane and calls the account ownership the win.
So the three models are really three answers to one question — which half of the stack do you own?
- Hosted (Railway, Render): own neither half; rent both, optimized for shipping speed.
- BYOC (Northflank): own the infrastructure account and data plane; rent the control plane.
- Self-hosted (Coolify, Dokploy, CapRover, bex): own both halves; pay in operations instead of subscription.
Nothing about that ladder is new. What the funding map adds is the price signal: investors pay the largest premiums to own the whole ladder, a medium premium to meter its middle rung, and nothing for the bottom — because the bottom is a cost you eliminate, not a bill you collect.
Which seat to take in 2026
The right answer depends on which constraint binds your team hardest:
| If your binding constraint is… | Take this seat | Why |
|---|---|---|
| Data sovereignty or compliance | BYOC | Workloads and data never leave your account; auditors get a clean boundary |
| Committed cloud spend to use up | BYOC | Burns credits and enterprise discounts on the infra half |
| Shipping speed above all | Hosted | No accounts, no clusters, no control plane to think about |
| Unit cost on owned hardware | Self-hosted | No per-vCPU meter; a Hetzner box idles for free |
| Roadmap independence | Self-hosted | Nobody else's pivot can strand your deploy path |
Two of those rows deserve emphasis because they are the ones teams misjudge. Sovereignty buyers should confirm exactly which metadata the managed control plane retains — "workloads in your account" and "nothing leaves your account" are different claims, and only the first is standard BYOC. And cost buyers should do the idle math honestly: metered platforms charge for every second, while owned hardware amortizes whether it idles or not — the sharper the idle-to-burst ratio, the stronger the self-hosting case.
The meter is the message
Step back and the 2024–2026 funding record reads as a single sentence: venture capital believes teams will pay forever to rent the control plane, whether bundled with the infrastructure (Railway, Render) or layered over infrastructure they own (Northflank, Nuon). The $22.3 million was never a bet on self-hosting. It was a bet that most teams want the feeling of owning their cloud with the convenience of someone else operating it — "your own cloud, managed for you," exactly as the headline says.
That leaves the own-everything end precisely where open source thrives: no meter to invest in, no roadmap to monetize, just software that turns machines you already pay for into a platform you fully control. The VCs are not wrong about where the recurring revenue is. They are just not the customer for the thing that has none.
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.
