Deno Exit: migration kit for teams stranded by the Cloudflare deal
Audit CLI and codemods that move Deno apps to Node, Bun or self-hosted workerd; teams with Deno in production pay.
Early · Cloudflare buys Deno, sunsets maintenance
Written for: Solo builder
Next step
Ship `deno-exit audit` this week against the 100 most-starred Deno repos, publish the 'most common blockers' list, and post it in the Deno Discord, the HN acquisition thread and r/Deno.
Why now
Every team running Deno or Deno-specific APIs in production now has roughly a year to move. That deadline creates urgency, and the work is mechanical: Deno.serve, Deno KV, jsr imports and the permissions model all need mapping. It fits a two-week CLI build, and Cloudflare's own tooling will push users toward Workers, not toward Node or Bun.
What became possible
Cloudflare acquired Deno to build on celld, Deno's open-source take on Durable Objects, and to make self-hosting workerd a supported option. According to Simon Willison's write-up, Cloudflare will not maintain Deno itself beyond the next year.
Three ways in
- deno-exit audit
Scans a repo for Deno-only APIs, KV usage, jsr/URL imports and permission flags. Outputs a ranked port plan for each target: Node, Bun or workerd.
- Customer
- Small SaaS teams and agencies with Deno services
- Model
- Free CLI; paid automated codemod pack per project
- KV Mover
Exports Deno KV data with consistent snapshots into Postgres, SQLite/D1 or Durable Objects, with a dual-write shim during cutover.
- Customer
- Apps that relied on Deno KV
- Model
- One-off fee per migration plus a monthly fee while dual-writing
- workerd on a VPS
One-command deploy panel for self-hosted workerd plus celld on Hetzner or DigitalOcean.
- Customer
- Developers who liked Deno Deploy but want no lock-in
- Model
- Open-source core; paid managed backups
Competition
The main risks are Cloudflare releasing its own Workers migration tooling and teams simply staying on self-hosted denokv plus the open-source Deno runtime, which a community may keep alive.
Full competition notes (8 competitors)
I confirmed the deal is real. Cloudflare announced on October 9, 2026 that it is acquiring the Deno team. Deno Deploy shuts down in about six months, the runtime gets roughly one more year of security fixes, and Deno's celld is being merged into workerd. The tooling space is close to empty: so far open-source projects are moving to Bun or Node by hand through PRs. I found no app-level audit or codemod that reports Deno-only APIs, KV usage, jsr/URL imports and permission flags, or that plans a port per target. dnt is the nearest piece, but it is built for publishing libraries. There is also no off-the-shelf tool that moves Deno KV into Postgres, SQLite/D1 or Durable Objects. What exists is KV-to-KV copying (kvdex, InnoKV) and denokv for self-hosting. Self-hosted workerd panels are still at the proof-of-concept or early-platform stage (WDL, self-workerd). The celld-into-workerd merge is led by Cloudflare, so a panel would be building on a moving upstream. I'd treat that idea as the weakest of the three. The best opening is the audit CLI plus KV Mover, sold to teams that won't take Cloudflare's free help because they want Node, Bun or no lock-in, or because they aren't paying Deploy customers. This is a time-boxed, one-off migration market with about six months for Deploy and twelve for the runtime. Many shops are small, and LLM coding agents can do much of a port for free, so expect project-sized revenue rather than recurring revenue. Ship quickly and price per migration or per seat for agencies. The main risks are Cloudflare releasing its own Workers migration tooling and teams simply staying on self-hosted denokv plus the open-source Deno runtime, which a community may keep alive.
- Cloudflare / Deno official migration support
Announced October 9, 2026. Deno Deploy shuts down in about six months and paying customers get migration help to Cloudflare Workers. No public tooling, pricing or SLA yet. It points only at Workers and only covers paying Deploy customers, but it is the default path and will compete for the best accounts.
- dnt (Deno to Node Transform)
Deno-team tool that rewrites module specifiers and shims the Deno namespace to produce npm packages. It is built for publishing libraries, not porting apps, and has no KV, permissions or deploy-target planning. Still, it is the closest open-source codemod and a free building block that cuts into a paid audit.
- kvdex migrate
Copies entries from one Deno KV instance to another. It is KV-to-KV only, with no export to Postgres, D1 or Durable Objects and no dual-write cutover.
- InnoKV
Deno KV admin and workspace tool that advertises bulk migration across keyspaces. It does not clearly support export to SQL.
- denokv (self-hosted Deno KV)
Official MIT-licensed self-hosted KV server backed by SQLite, plus a fourplayers fork with FoundationDB, ScyllaDB and RocksDB backends. It lets teams keep KV without Deploy, which competes with a pay-to-move-off-KV story. Because it uses SQLite, people can also export with ordinary SQLite tools.
- WDL (self-hosted multi-tenant Workers platform)
Self-hosted multi-tenant Workers platform built on stock workerd, deployed with Docker Compose, Kubernetes or Terraform. It is the closest existing match to the workerd-on-a-VPS idea.
- self-workerd
Proof-of-concept FaaS built on workerd and hosted on Fly. It is not a VPS panel.
- Manual community migrations (Probitas, Fedify, SilverBullet)
Projects are already moving off Deno to Bun or Node by hand. They are dropping KV, swapping Deno.test for Vitest and replacing deno.json with package.json. This shows real demand and that nobody is using a tool for it yet. Related: https://github.com/fedify-dev/fedify/issues/1281 and https://community.silverbullet.md/t/migration-from-deno-to-node-js/3956
Checked 2026-10-10
Risks
- The Deno community may fork and keep maintaining it, which removes the urgency
- Cloudflare may publish free official migration guides
- The number of paying Deno production users may be small
Strong tech readiness; market pull is the weak point (6).
tech 9 · pull 6 · space 8 · fit 8 · build 8
Exposed
Companies that could benefit or be threatened. News and context, not investment advice.
Momentum of its main topic
Sources
What happened next
- +7d · 17 Oct 2026 nothing yet. No products, funding, or acquisitions matching the three flagged product ideas (deno-exit audit, KV Mover, or workerd VPS deployment) have launched or been announced in the seven days since October 10, 2026. The Cloudflare-Deno acquisition on October 9 created the opportunity, but no new migration tooling startups or products have emerged yet.
Status history
- 2026-10-10 Flagged as buildable