Three stories from this week point the same way: the line between running your own infrastructure and renting someone else's keeps moving. Here is what happened and what it means for your plans.
The Deno team joins Cloudflare
On 9 October, Deno creator Ryan Dahl announced that the whole Deno team is joining Cloudflare. Deno is a JavaScript and TypeScript runtime, a rival to Node.js, with its own hosting service called Deno Deploy.
The practical details matter more than the headline:
- Deno Deploy will run for six more months and then close. Paying customers will get help moving to Cloudflare Workers.
- The Deno runtime will get monthly bug fix and security releases for one more year. After that, active development ends. It stays open source and others are welcome to carry it on.
- JSR, the package registry, keeps running, with its infrastructure moving to Cloudflare.
The team will work on a shared platform built on the Workers programming model and Durable Objects, which Cloudflare wants to become the default way to build servers, on its network or on customers' own machines.
What to do: if any team runs production code on Deno Deploy, you now have a six-month deadline. If you run the Deno runtime itself, you have about a year of security fixes. Either way, put it on the risk register this month. This is also a reminder to check how many small hosting platforms your teams use without central sign-off.
Cloudflare K2 brings event streams to its developer platform
Cloudflare has opened K2 in public beta. It is a serverless service for event streams, the job Apache Kafka usually does: producers write events, they are kept in order, and many consumers can read them, now or much later.
K2 stores everything on Cloudflare's R2 object storage. That keeps long-term storage cheap and removes the need to run brokers. The trade is speed. Cloudflare says it adds about one second to writes at the 99th percentile. An independent tester quoted by InfoQ measured about 7.5 seconds end to end at the 99th percentile. K2 is not Kafka-compatible yet, though Kafka client support is on the roadmap. Usage is free during the beta, with planned pricing of $0.04 per GB written, $0.04 per GB read and $0.02 per GB per month stored.
What to do: K2 is worth a look for high-volume data that does not need fast delivery, such as analytics events, logs and audit trails. It is not a fit yet for anything where seconds matter. Treat the beta as a test, not a migration target.
Oxide raises $445 million
Oxide Computer, which builds complete server racks that work like a private cloud, raised a $445 million Series D led by Eclipse. Chip maker AMD joined as a new strategic investor, alongside Atreides Management. Oxide says its normal operations are profitable and that the money will go into fulfilling a large order backlog and expanding manufacturing.
Why it matters: a profitable hardware company with a backlog is a signal that some buyers, especially in government, finance and AI, want to own their infrastructure again. Cost, data control and GPU supply are all part of that. If your board has asked about cloud exit or repatriation, expect more vendors and more serious options in this space over the next year.
The thread that ties it together
Cloudflare wants its programming model to run anywhere, including on customers' own machines. Google is doing the same with Spanner this week. Oxide is selling the machines. The choice between cloud and on-premises is turning into a choice about which operating model you trust, and who you want to hold the pager.
