Live data from Hacker News

Cloudflare OS: an open platform for agents, apps, and work

blog.cloudflare.com

71–80 of 365 posts

Re: Cloudflare OS: an open platform for agents, apps, and work

#72
post #41
post #31

Earlier quoted context omitted.

> the sandbox is so secure that you can pretty much go wild -- the AI cannot introduce a significant security bug. This can only be correct when the application can’t affect anything outside the sandbox. Which would significantly restrict useful applications.

See my next tweet in the chain: https://x.com/KentonVarda/status/2084990302784307363 ------------- Of course, personal apps are more useful if they can connect to external services. Cloudflare OS introduces a "connector" system we call Gatekeepers. This is sort of like MCP (and MCP is supported as a kind of Gatekeeper), but with a lot more: * Instead of exposing tools, a Gatekeeper exposes a Cap'n Web RPC API. That m…

Interesting, so how does this work with regards to purposeful but naive changes? If, for example, we have a Notion integration, and a non-technical user can add a feature to it via prompt, would it be possible for them to accidentally add something that sends a bunch of internal-only proprietary data to Notion? Would this system prevent or flag that in some way?

Re: Cloudflare OS: an open platform for agents, apps, and work

#73
post #39
post #25

Earlier quoted context omitted.

Sandstorm without self hosting has no interest though. (Edit: see below, where the creator states it _can_ be run locally) Buzz looks like a more reasonable direction than this does.

What do you mean? This is 100% open source and self-hostable! https://github.com/cloudflare/cloudflare-os It runs on the open source Workers Runtime: https://github.com/cloudflare/workerd You can run it at home if you want. There's even a Home Assistant Gatekeeper.

Do you have a store/list of public blueprints like sandstorm?

Re: Cloudflare OS: an open platform for agents, apps, and work

#74
post #57
post #32

Earlier quoted context omitted.

That should have been the announcement. The article posted buries the lead. Cloudflare OS reads like almost any other AI knowledge base until midway when apps are introduced and then becomes overly technical with a code snippet.

We really struggled with how to present this to multiple audiences at once. My tweet thread, and the GitHub readme, is really the presentation intended for the HN crowd. The blog post is for a different audience. https://github.com/cloudflare/cloudflare-os

> The blog post is for a different audience.

No one? Like literally, I don't understand a thing of what the blog post is saying. It's vague to the point of meaning nothing. Every piece of text I've seen that explains CloudflareOS is clear except the blog post.

Re: Cloudflare OS: an open platform for agents, apps, and work

#75
post #24

"OS for work" - like, what does it mean? OS is operating system, it runs on a hardware and provides you to operate the system. I hate when companies destroy the English language with vibe invented terms.

An operating system manages access to shared hardware (disk, CPU, memory, networking, display, etc. on a single machine OS). MS-DOS mainly handled shared access to disk via a file system abstraction, hence the name. The naming of Cloudflare OS makes sense to me.

Re: Cloudflare OS: an open platform for agents, apps, and work

#76
post #4

I liked Kenton's take on this: https://x.com/KentonVarda/status/2084990137180590572?s=20 Text from tweet: Today we are releasing Cloudflare OS, a chatbot with connectors, just like every other tech company is doing. Except actually, it's different. This is a remake of Sandstorm[.]io, my startup from 10 years ago, except this time built on Cloudflare Workers (the platform I've spent the last 9 years building) and deep…

This is really interesting. I built a similar product (not released yet), but it uses Kubernetes as the infrastructure layer instead of Cloudflare OS. I guess all these years later I am left with the same existential question that plagued Sandstorm. What is its relevance in the context of Linux containers? This is not a rhetorical question, is there a real benefit for a Sandstorm grain over a docker style Linux container? Does a containerized process not have all the same benefits of a Sandstorm grain, with the added benefit of not requiring any modifications of the containerized software?

One argument I could bring is that despite all its claims, OpenAI still had to switch from containers to MicroVMs because its agents under test still managed to break out from their containers. Is the security model of a Sandstorm grain so much better that agents wouldn't figure out how to break out of it?

Re: Cloudflare OS: an open platform for agents, apps, and work

#77
post #39

Earlier quoted context omitted.

What do you mean? This is 100% open source and self-hostable! https://github.com/cloudflare/cloudflare-os It runs on the open source Workers Runtime: https://github.com/cloudflare/workerd You can run it at home if you want. There's even a Home Assistant Gatekeeper.

Do you have a store/list of public blueprints like sandstorm?

Not yet, but that's an obvious direction to take things. :)

I'm really excited by the idea that this platform makes it safe to use blueprints that someone else vibe coded, without worrying about whether they checked it for security bugs, etc. Basically if the app works, it works. So yeah, there absolutely should be a marketplace so everyone can try everyone else's stuff.

BTW there are three blueprints installed automatically (docs, slides, sheets).

Re: Cloudflare OS: an open platform for agents, apps, and work

#79
post #76
post #4

I liked Kenton's take on this: https://x.com/KentonVarda/status/2084990137180590572?s=20 Text from tweet: Today we are releasing Cloudflare OS, a chatbot with connectors, just like every other tech company is doing. Except actually, it's different. This is a remake of Sandstorm[.]io, my startup from 10 years ago, except this time built on Cloudflare Workers (the platform I've spent the last 9 years building) and deep…

This is really interesting. I built a similar product (not released yet), but it uses Kubernetes as the infrastructure layer instead of Cloudflare OS. I guess all these years later I am left with the same existential question that plagued Sandstorm. What is its relevance in the context of Linux containers? This is not a rhetorical question, is there a real benefit for a Sandstorm grain over a docker style Linux conta…

Sandstorm's use of containers was just a means to an end. The real innovation was the fine-grained instances -- each document in its own container. No other container platform did that.

But honestly, it didn't work well, because of cold start times and memory usage. It's bad enough when a server takes seconds to start, but if every document you open has a long startup time and uses hundreds of MB of RAM, it's really painful.

Cloudflare OS doesn't use containers. It uses Dynamic Workers, which are 100x more efficient: https://blog.cloudflare.com/dynamic-workers/

So the stuff I have been building in Workers for the past 9 years turns out to be the thing that Sandstorm needed all along. What a coincidence. :)

Re: Cloudflare OS: an open platform for agents, apps, and work

#80
post #4

I liked Kenton's take on this: https://x.com/KentonVarda/status/2084990137180590572?s=20 Text from tweet: Today we are releasing Cloudflare OS, a chatbot with connectors, just like every other tech company is doing. Except actually, it's different. This is a remake of Sandstorm[.]io, my startup from 10 years ago, except this time built on Cloudflare Workers (the platform I've spent the last 9 years building) and deep…

https://xcancel.com/KentonVarda/status/2084990137180590572
Post reply on HN