Your venture-backed runtime has a six-month exit clause and you never signed it

On 9 October 2026 every paying Deno Deploy customer found out how long their notice period was: six months. Nobody negotiated that number. Ryan Dahl announced that the entire Deno team is joining Cloudflare. Deploy keeps running for half a year and then shuts. Paying customers get migration support onto Cloudflare Workers. The Deno runtime gets one more year of monthly bug-fix and security releases, and then official development stops.

I expected the usual acquisition script, where the brand survives for a while and the price list gets rewritten a year later. What arrived was quicker. For anyone with production traffic on Deploy, I think it is also costlier than a price rise would have been.

Start with the money, because it explains the timing. Deno raised $21m in 2022 in a round led by Sequoia Capital, with Nat Friedman, Insight Partners, Automattic, Netlify and others alongside. Investors who write cheques like that need an outcome. A hosting business that started in 25 regions, grew to 35 and was down to 6 by May 2025 does not look like one. Dahl himself said at the time that "reduction was driven by cost, yes - but also by usage." The developer David Bushell had already pointed out the drop from 35 regions to 12 by January 2024. A Deno employee publicly insisted the cuts had nothing to do with decline and claimed roughly 2x adoption since Deno 2. In the same May 2025 post, Dahl promised Deploy would gain subprocesses, background tasks, OpenTelemetry, build pipelines, caching and self-hosted regions.

I don't think customers were foolish to believe the founder. Founders believe their own roadmaps. The mistake was letting a blog post stand in for a contract clause. Every signal a procurement team needed was public for at least two years, and none of it changed what customers could legally demand when the end came.

Cloudflare's defenders will say nobody repriced anything, and they have a case. The runtime stays open source. Dahl and Bert Belder plan to fold celld into workerd, Cloudflare's open-source runtime, with the stated aim of letting developers run it on their own servers. JSR, the package registry, keeps operating on Cloudflare infrastructure. None of the coverage I have seen discloses deal terms or any change to Cloudflare's pricing.

I accept all of that and still think customers have been repriced. If your team has to rewrite deployment pipelines, retest on a different execution model and re-learn a vendor's limits, the platform just cost you an engineering quarter you had not budgeted. The destination is the new owner's own product, on its standard terms, at the precise moment your switching leverage is zero. An open-source runtime whose original maintainers stop after a year is a fork you fund yourself, or a second migration you schedule for next year.

Some customers get hit twice. On announcement day Deno's own migration guide, last modified on 18 June 2026, was still telling Deploy Classic users to move to the new Deno Deploy platform, the one now shutting down. Anyone who followed that guide this summer did a migration in good faith and has just been told to do another. Rivals noticed instantly: Appwrite had an alternatives post up quoting Dahl's announcement date. When a competitor is writing your customers' migration plan within days, the vendor's customers had no protection worth the name.

The fix belongs in the paper, and the only time to get it is before a change of control, while the vendor still wants your signature. I would ask any venture-backed infrastructure vendor for at least a year's written notice before discontinuing a service you pay for. I would ask for a price lock of two years after any acquisition, and for the right to terminate without penalty if ownership changes. Add documented export of your data and configuration, and service credits sized to cover the engineering time a forced move costs. Small vendors hungry for logos will often agree, because they do not expect to be bought or shut. Large acquirers inherit those obligations and have to honour them.

This applies well beyond Deno. Any newer runtime, edge host or serverless database whose funding came from a priced round, and whose hosting revenue is smaller than its reputation on developer forums, sits in the same position Deno Deploy did in 2024.

Deploy's six months run out next April. Before then, pull every contract you hold with a venture-backed infrastructure vendor and search it for the words "change of control". Where they are missing, put them on the agenda for the next renewal call.

Prompted by Deno is joining Cloudflare | Deno, Deno.