You're missing the subtle marketecture trick here they are doing..
Non-technical people don't always think of an OS as the computer OS. To them, sometimes it means more like standard operating procedure or process - a standard way of doing things.
Secondly, for tech products, calling yourself an OS, you are associating yourself with things like Windows, Mac or Linux. You are indirectly trying to grandstand and position yourself as meaningful enough to be an "OS" when clearly, that is far from what an app layer + AI/LLM on top of a real OS is.
The biggest giveaway is this, and I'm exposing it right here -from a technical perspective, what operating system computer technology was built from scratch from first principles around AI/LLM?
Someone wants to be the first company to get huge sums of money/funding to be that startup/project, so that is also a positioning tactic.
The issue is of course, most people are standing on the shoulders of giants at this point... and OS has this conflicted meaning with nontechnical users also about work process vs the software that runs my computer.
People do not use an 'OS' anymore. Anything internet is a hundred pieces of hardware over 1000 kilometers apart providing an interface to an application with a KVM (for now)
Marketing types have started subbing in "Operating System" for "Platform" lately. And, because it feels bold and fresh to them, they often name whole product an "OS" when they do this in order to make anyone who talks about the product re-sell the pitch for them.
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 deeply leveraging AI. This is more or less the culmination of my secret 10-year master plan.
This is a full-on personal app vibe coding platform, in which the sandbox is so secure that you can pretty much go wild -- the AI cannot introduce a significant security bug. We believe a company's security team can feel comfortable giving non-technical users permission to vibe code and then sleep soundly at night.
How is that possible? It's the Sandstorm security model, revisited. A "Gadget" is the same thing as a Sandstorm "Grain": a fine-grained app instance. For example, if you have a document editor app, each document runs as a separate instance of the app, in a separate sandbox (one "Gadget").
This means two things, both of which I think are Big Deals:
1. The platform can manage all access control, by controlling who can access the Gadget at all. There is no way the Gadget can accidentally leak itself to an attacker -- even an attacker who has access to other Gadgets based on the same app.
2. Since everyone is running their own copy of the code, everyone can freely modify their copy of the code.
Think about #2 a bit more.
What if, when you wanted a new feature in the software you are using, you could just prompt your agent to add it?
This doesn't work in the cloud Software-as-a-Service model, because you are not running your own copy of the app.
Sandstorm tried to change that 10 years ago, but the world wasn't ready, because not enough people had the skills or patience to actually modify their software. AI has changed that. Now you just ask the agent -- the same agent that you are using to help you interact with the Gadget can also modify the code of the Gadget.
It is quite foolish to believe that now that we have AI generated code that people will suddenly choose the more secure option rather than the cheapest. My evidence in exhibit A: The success of Wordpress.
This is effectively a Codex/Claude app competitor. Good move from Cloudflare since it helps them sell their core infra offerings. I like the direction they’re going with access control.
> Cloudflare OS is available today and is open source. Check out the cloudflare-os GitHub repository. You can deploy it into your own Cloudflare account and use your own Access policies, AI Gateway configuration, data, and integrations.
Everytime I read about new things from Cloudflare they look really cool but I cannot shake the feeling of not wanting to use them for fear of lock-in, am I too paranoid?
"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.
Seems like an established term now. I read this months back (paraphrase): "Engineer me calls it a fully featured SaaS for X, marketing would call it an OS for X". Yet another company is called WorkOS.
This represents a small part of what IT is worried about. Offer a beer and say the word "SharePoint" if you want the long version of where this could wind up.
The issue isn't letting end-users add features. The issue is twelve end-users customizing something that produces output, saving it, and now nobody can read it.
This can get solved. If it even gets a chance to gain traction (it should, though IT will of course push back). But let's not pretend we're there yet.
Engineers should be wary about being forced into using particular prompts/skills/instructions.
Why would I use a shared LLM-in-the-cloud, instead of my own? The shared one precludes any possibility to customize or differentiate my workflow, prompts, or skills. As an employee that sounds like a death sentence to doing my job effectively.
Setting up your public URLRetrying… (attempt 5 of 6)
Fingers crossed!! The last one gotta be the one...
EDIT: It let me down... (Something unexpected went wrong on our side.)
Please let me now if deploying it on your custom domain worked for you please...
EDIT: Retrying it now worked but I had to subscribe to R2 (which is free for 10GB apparently). However, after that it will tell you that you need to enable the Dynamic Workers which is actually paid...
"Your Cloudflare account is on the Free plan, but the Cloudflare OS backend needs Dynamic Workers, which requires the Workers Paid plan."
I can't help but wonder if these things that are now emerging have a sort of "borrowed time" component tied to them.
I see the examples, and they clearly tackle both organizational inefficiencies and human connection/communication as the core problems.
Sounds like things are converging to "my AI will talk to your AI" and the role of humans will just be a human "router" in the loop switching up nodes in a graph, like the return of Switchboard Operators from the 1950s.
Everyone is building these same looking apps that look like Codex, Claude desktop. We don't need these. Slackbots work more than well enough to collaborate with agents.
114 comments
[ 0.25 ms ] story [ 24.1 ms ] threadNon-technical people don't always think of an OS as the computer OS. To them, sometimes it means more like standard operating procedure or process - a standard way of doing things.
Secondly, for tech products, calling yourself an OS, you are associating yourself with things like Windows, Mac or Linux. You are indirectly trying to grandstand and position yourself as meaningful enough to be an "OS" when clearly, that is far from what an app layer + AI/LLM on top of a real OS is.
The biggest giveaway is this, and I'm exposing it right here -from a technical perspective, what operating system computer technology was built from scratch from first principles around AI/LLM?
Someone wants to be the first company to get huge sums of money/funding to be that startup/project, so that is also a positioning tactic.
The issue is of course, most people are standing on the shoulders of giants at this point... and OS has this conflicted meaning with nontechnical users also about work process vs the software that runs my computer.
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 deeply leveraging AI. This is more or less the culmination of my secret 10-year master plan.
This is a full-on personal app vibe coding platform, in which the sandbox is so secure that you can pretty much go wild -- the AI cannot introduce a significant security bug. We believe a company's security team can feel comfortable giving non-technical users permission to vibe code and then sleep soundly at night.
How is that possible? It's the Sandstorm security model, revisited. A "Gadget" is the same thing as a Sandstorm "Grain": a fine-grained app instance. For example, if you have a document editor app, each document runs as a separate instance of the app, in a separate sandbox (one "Gadget").
This means two things, both of which I think are Big Deals: 1. The platform can manage all access control, by controlling who can access the Gadget at all. There is no way the Gadget can accidentally leak itself to an attacker -- even an attacker who has access to other Gadgets based on the same app. 2. Since everyone is running their own copy of the code, everyone can freely modify their copy of the code.
Think about #2 a bit more.
What if, when you wanted a new feature in the software you are using, you could just prompt your agent to add it?
This doesn't work in the cloud Software-as-a-Service model, because you are not running your own copy of the app.
Sandstorm tried to change that 10 years ago, but the world wasn't ready, because not enough people had the skills or patience to actually modify their software. AI has changed that. Now you just ask the agent -- the same agent that you are using to help you interact with the Gadget can also modify the code of the Gadget.
And it is so fun.
Famous last words.
Uh-huh.
> "Give every person an agent and workspace built around how your company works, what it knows, and the systems it relies on."
Hundreds of thousands of so called "AI startups" have been eliminated.
https://github.com/open-webui/open-webui
In case anybody missed it.
The issue isn't letting end-users add features. The issue is twelve end-users customizing something that produces output, saving it, and now nobody can read it.
This can get solved. If it even gets a chance to gain traction (it should, though IT will of course push back). But let's not pretend we're there yet.
"Your Cloudflare account is on the Free plan, but the Cloudflare OS backend needs Dynamic Workers, which requires the Workers Paid plan."
Why would I use a shared LLM-in-the-cloud, instead of my own? The shared one precludes any possibility to customize or differentiate my workflow, prompts, or skills. As an employee that sounds like a death sentence to doing my job effectively.
EDIT: It let me down... (Something unexpected went wrong on our side.)
Please let me now if deploying it on your custom domain worked for you please...
EDIT: Retrying it now worked but I had to subscribe to R2 (which is free for 10GB apparently). However, after that it will tell you that you need to enable the Dynamic Workers which is actually paid...
"Your Cloudflare account is on the Free plan, but the Cloudflare OS backend needs Dynamic Workers, which requires the Workers Paid plan."
So no free preview for me today.
I see the examples, and they clearly tackle both organizational inefficiencies and human connection/communication as the core problems.
Sounds like things are converging to "my AI will talk to your AI" and the role of humans will just be a human "router" in the loop switching up nodes in a graph, like the return of Switchboard Operators from the 1950s.