Загрузка видео...

Не удалось загрузить видео

Возникла проблема при загрузке этого видео. Это может быть связано с временными проблемами сети или видео может быть недоступно.

На главную

⚡ i just dropped ActorCore v0.1.0 on NPM Cloudflare Developers durable objects will be the new cloud primitive in 2025, but they're vendor-locked to Workers ActorCore lets you deploy actors to any serverless cloud includes features like rpc, events, scheduling, & multiplayer

Nathan Flurry 🔩

6,215 subscribers

13,496 просмотров • 1 год назад •via X (Twitter)

Игры Наука и технологии

Anya Rossi• Live Now

Private livecam show

Комментарии: 11

Фото профиля Nathan Flurry 🔩

Nathan Flurry 🔩1 год назад

Rivet Actors are an open-source Durable Object alterntaive, so why'd we build this? ActorCore helps both Rivet & Cloudflare alike many companies want to use Durable Objects, but won't because it's a vendor-locked product more options = more users

Фото профиля Nathan Flurry 🔩

Nathan Flurry 🔩1 год назад

get the source – read the docs –

Фото профиля GitProtect.io

GitProtect.io2 лет назад

Automated GitHub, GitLab, Bitbucket and Jira backups, security compliance, data migration and every-scenario-ready Disaster Recovery for 360 cyber resilience. Schedule a custom demo or try 14 days for free.

Фото профиля brandon

brandon1 год назад

@CloudflareDev this is so cool, nice work

Фото профиля ELLIE X

ELLIE X1 год назад

@CloudflareDev wooo!!!! good job. will check things out

Фото профиля Nathan Flurry 🔩

Nathan Flurry 🔩1 год назад

@CloudflareDev would love any and all feedback! early days on ActorCore, a lot more coming soon

Фото профиля Sébastien Chopin

Sébastien Chopin1 год назад

@CloudflareDev Beautiful work, love the 5min demo

Фото профиля Aleksei Dolgikh 2025 | CVO, Scout VC, Collaborator

Aleksei Dolgikh 2025 | CVO, Scout VC, Collaborator1 год назад

@CloudflareDev RP, cool

Фото профиля J.J. Fliegelman

J.J. Fliegelman1 год назад

@CloudflareDev This is cool

Фото профиля steve.wasm

steve.wasm1 год назад

@CloudflareDev good idea

Фото профиля Nathan Flurry 🔩

Nathan Flurry 🔩1 год назад

@CloudflareDev and it has a standard http api, now imagine the cool demo i could ship if i didn't get sidetracked 🫢

Похожие видео

Finally (re)launching 🚀 MCPify is like Lovable/Bolt/V0, but for building MCP servers! You just talk to the AI and can create your own MCP server. I built this completely using Cloudflare Developers Cloudflare Workers + Durable Objects + Workers for Platforms

Finally (re)launching 🚀 MCPify is like Lovable/Bolt/V0, but for building MCP servers! You just talk to the AI and can create your own MCP server. I built this completely using Cloudflare Developers Cloudflare Workers + Durable Objects + Workers for Platforms

Bhanu Teja P

101,357 просмотров • 1 год назад

I built a self-hosted Sentry clone that runs entirely on Cloudflare Workers, and I think it showcases one of the most underrated features in the Cloudflare ecosystem: Service Bindings. Let me explain why this matters. When you have multiple Cloudflare Workers (an API, a webhook handler, a cron job), they all need common things: error tracking, authentication, rate limiting, metrics. The typical solution? External HTTP calls to third-party services. That means: - 50-200ms latency per call - Egress fees - Your data leaving your infrastructure - Another vendor to manage Service bindings let Workers call each other directly inside Cloudflare's network. No HTTP. No internet. Just internal RPC with <5ms latency. With Workers Sentinel, any Worker in my account can just point Sentry-SDK into the Service binding, and have all errors flow into one centralized dashboard, stored in Durable Objects with SQLite. No external calls. No added latency. Service bindings aren't just for error tracking. You can centralize: 🔐 Authentication — One Worker that validates tokens for all your services 📊 Metrics — Centralized collection without external observability costs 🚦 Rate Limiting — Shared counters that actually work across Workers 🚩 Feature Flags — Instant propagation, no deployment needed Think of it as building your own internal microservices mesh, but at the edge, with zero network overhead. Workers Sentinel uses two Durable Objects: - AuthState (singleton) — users, sessions, projects - ProjectState (per-project) — issues, events, stats Events are fingerprinted and grouped intelligently. The dashboard is a Vue.js app served from the same Worker. I could say i built this to learn Durable Objects or that I needed error tracking for side projects, but honestly I just need a way to show my wife why I'm sending $200/month to some guy named Claudio who apparently helps me write code. The whole thing is open source. Deploy it to your Cloudflare account, point your Sentry SDKs at it, and you're done. But more importantly: take a closer look at service bindings. They're the glue that turns a collection of Workers into an actual platform. Most Cloudflare customers I talk to aren't using them, and they're missing out. To the Sentry team: I love your work. Genuinely. Sentry is battle-tested, has incredible features, and is what you should use for anything that matters. This project is a toy. A learning exercise. A weekend hack that got slightly out of hand. Please do not trust your production errors to this dummy clone. If your startup goes down at 3 AM because Workers Sentinel missed an edge case, that's on you. I warned you. Use the real thing. But if you want to learn about Durable Objects, service bindings, and how error tracking works under the hood? Clone away. Your Workers shouldn't be islands. Connect them.

I built a self-hosted Sentry clone that runs entirely on Cloudflare Workers, and I think it showcases one of the most underrated features in the Cloudflare ecosystem: Service Bindings. Let me explain why this matters. When you have multiple Cloudflare Workers (an API, a webhook handler, a cron job), they all need common things: error tracking, authentication, rate limiting, metrics. The typical solution? External HTTP calls to third-party services. That means: - 50-200ms latency per call - Egress fees - Your data leaving your infrastructure - Another vendor to manage Service bindings let Workers call each other directly inside Cloudflare's network. No HTTP. No internet. Just internal RPC with <5ms latency. With Workers Sentinel, any Worker in my account can just point Sentry-SDK into the Service binding, and have all errors flow into one centralized dashboard, stored in Durable Objects with SQLite. No external calls. No added latency. Service bindings aren't just for error tracking. You can centralize: 🔐 Authentication — One Worker that validates tokens for all your services 📊 Metrics — Centralized collection without external observability costs 🚦 Rate Limiting — Shared counters that actually work across Workers 🚩 Feature Flags — Instant propagation, no deployment needed Think of it as building your own internal microservices mesh, but at the edge, with zero network overhead. Workers Sentinel uses two Durable Objects: - AuthState (singleton) — users, sessions, projects - ProjectState (per-project) — issues, events, stats Events are fingerprinted and grouped intelligently. The dashboard is a Vue.js app served from the same Worker. I could say i built this to learn Durable Objects or that I needed error tracking for side projects, but honestly I just need a way to show my wife why I'm sending $200/month to some guy named Claudio who apparently helps me write code. The whole thing is open source. Deploy it to your Cloudflare account, point your Sentry SDKs at it, and you're done. But more importantly: take a closer look at service bindings. They're the glue that turns a collection of Workers into an actual platform. Most Cloudflare customers I talk to aren't using them, and they're missing out. To the Sentry team: I love your work. Genuinely. Sentry is battle-tested, has incredible features, and is what you should use for anything that matters. This project is a toy. A learning exercise. A weekend hack that got slightly out of hand. Please do not trust your production errors to this dummy clone. If your startup goes down at 3 AM because Workers Sentinel missed an edge case, that's on you. I warned you. Use the real thing. But if you want to learn about Durable Objects, service bindings, and how error tracking works under the hood? Clone away. Your Workers shouldn't be islands. Connect them.

Gabriel Massadas

28,656 просмотров • 5 месяцев назад

We are super excited to make Restate Cloud publicly available today. Durable Execution, observability, and production-grade availability for workflows or AI agents. This release makes very smooth to work with serverless compute platforms like Cloudflare, Vercel, or Deno. And of course, your own infra on AWS, GCP, or Kubernetes. Signup is free and a few clicks with your GitHub account. A new built-in tutorial let's you run a first durable agent running in seconds. 👇

We are super excited to make Restate Cloud publicly available today. Durable Execution, observability, and production-grade availability for workflows or AI agents. This release makes very smooth to work with serverless compute platforms like Cloudflare, Vercel, or Deno. And of course, your own infra on AWS, GCP, or Kubernetes. Signup is free and a few clicks with your GitHub account. A new built-in tutorial let's you run a first durable agent running in seconds. 👇

Stephan Ewen

30,681 просмотров • 9 месяцев назад

Wanted to learn more about MCPs this weekend. So I built this mini-tool called Here is how it works: 1️⃣ Tell the AI what you want. 2️⃣ It creates an MCP server with various tools. 3️⃣ Talk with AI to add/remove/modify these tools. 4️⃣ Click on Deploy and get your own MCP Server URL. You can directly use in url in Cursor / Claude Desktop or anywhere you want. Completely powered by Cloudflare Developers Durable Objects + Workers for Platforms

Wanted to learn more about MCPs this weekend. So I built this mini-tool called Here is how it works: 1️⃣ Tell the AI what you want. 2️⃣ It creates an MCP server with various tools. 3️⃣ Talk with AI to add/remove/modify these tools. 4️⃣ Click on Deploy and get your own MCP Server URL. You can directly use in url in Cursor / Claude Desktop or anywhere you want. Completely powered by Cloudflare Developers Durable Objects + Workers for Platforms

Bhanu Teja P

108,366 просмотров • 1 год назад

🤔 “WE NEED YOU HOME” - Annie “The Poet” Guthrie chose that moment to plead for her mother’s return in Poetry? I HAVE SEEN THIS MOVIE BEFORE. I’m fairly sure I know how it ends. Only a few people would be aware The Ring Cam didn’t have a subscription. Let me explain how that works. If there is no subscription it won’t automatically upload to the cloud. If you have a subscription it will upload to the cloud BUT if you have access to the account you can delete it permanently instantly from the cloud. I hope I’m wrong on this but more importantly I hope Nancy Guthrie is ok. President Trump seems to indicate prior on AF1 that a resolution may be close..I have a feeling given our technology in 2026..we will know by tomorrow what transpired.

🤔 “WE NEED YOU HOME” - Annie “The Poet” Guthrie chose that moment to plead for her mother’s return in Poetry? I HAVE SEEN THIS MOVIE BEFORE. I’m fairly sure I know how it ends. Only a few people would be aware The Ring Cam didn’t have a subscription. Let me explain how that works. If there is no subscription it won’t automatically upload to the cloud. If you have a subscription it will upload to the cloud BUT if you have access to the account you can delete it permanently instantly from the cloud. I hope I’m wrong on this but more importantly I hope Nancy Guthrie is ok. President Trump seems to indicate prior on AF1 that a resolution may be close..I have a feeling given our technology in 2026..we will know by tomorrow what transpired.

Johnny St.Pete

151,386 просмотров • 5 месяцев назад

Incredible. If you’ve been frustrated (like I have!) by pricey AI agents that feel like black boxes, you’ve got to try the new Stagehand! 🔥 It's a web agent SDK that runs locally or in the cloud, gives you full browser control, works with any LLM, & is 100% open-source! 🧵 ↓

Incredible. If you’ve been frustrated (like I have!) by pricey AI agents that feel like black boxes, you’ve got to try the new Stagehand! 🔥 It's a web agent SDK that runs locally or in the cloud, gives you full browser control, works with any LLM, & is 100% open-source! 🧵 ↓

Charly Wargnier

90,579 просмотров • 1 год назад

🚀 Introducing LangGraph Cloud 🚀 LangGraph helps you build reliable agents that actually work. Today, we've launched LangGraph Cloud, our new infrastructure to run fault-tolerant LangGraph agents at scale. With LangGraph Cloud, you can: • Handle large workloads with horizontally-scaling servers, task queues, and built-in persistence • Debug agent failure modes and iterate quickly in a visual playground-like studio • Deploy in one-click and get integrated tracing & monitoring in LangSmith This builds on LangGraph v0.1, our latest stable release supporting diverse control flows - whether it's single- or multi-agent, hierarchal or sequential. You'll be able to create flexible agents with human-in-the-loop collaboration and first-class streaming support. We can't wait to see the agentic workflows you'll ship. LangGraph Cloud is available in closed beta today. 👉 Join the waitlist for LangGraph Cloud: ✍️ Read our blog post announcement: 📽️ Watch the video walkthrough: 🌀 Haven't tried LangGraph yet? Give it a spin here: 🙌 Check out the new LangGraph landing page:

🚀 Introducing LangGraph Cloud 🚀 LangGraph helps you build reliable agents that actually work. Today, we've launched LangGraph Cloud, our new infrastructure to run fault-tolerant LangGraph agents at scale. With LangGraph Cloud, you can: • Handle large workloads with horizontally-scaling servers, task queues, and built-in persistence • Debug agent failure modes and iterate quickly in a visual playground-like studio • Deploy in one-click and get integrated tracing & monitoring in LangSmith This builds on LangGraph v0.1, our latest stable release supporting diverse control flows - whether it's single- or multi-agent, hierarchal or sequential. You'll be able to create flexible agents with human-in-the-loop collaboration and first-class streaming support. We can't wait to see the agentic workflows you'll ship. LangGraph Cloud is available in closed beta today. 👉 Join the waitlist for LangGraph Cloud: ✍️ Read our blog post announcement: 📽️ Watch the video walkthrough: 🌀 Haven't tried LangGraph yet? Give it a spin here: 🙌 Check out the new LangGraph landing page:

LangChain

134,051 просмотров • 2 лет назад

Wow Gemini is basically your own cloud computer now 🔥 You can ask it to generate any document like - Docs - Sheets - PDF - CSV But also things like Word, Excel, LaTeX, txt, etc. So you're not limited to just standard textual chats... which is VERY powerful. Even tables and diagrams can be integrated in the docs.

Wow Gemini is basically your own cloud computer now 🔥 You can ask it to generate any document like - Docs - Sheets - PDF - CSV But also things like Word, Excel, LaTeX, txt, etc. So you're not limited to just standard textual chats... which is VERY powerful. Even tables and diagrams can be integrated in the docs.

Paul Couvert

20,311 просмотров • 2 месяцев назад

.Nick Grossman is betting that in the future, AI agents will look more like cloud infrastructure than digital employees. "Part of the Rebel Alliance thesis for us is that agents are moving from personified people you hire to cloud infrastructure." "We're not just talking about, 'Will there be other agents that compete with Claude or ChatGPT?' I think that's one version of what agents look like. Another version is cloud infrastructure where every company that's building any system is going to have agents and the orchestration of hundreds or thousands of agents built into their underlying platform." "If you think of agents as infrastructure as opposed to agents as employees, I think that's where a lot of these forces come into play."

.Nick Grossman is betting that in the future, AI agents will look more like cloud infrastructure than digital employees. "Part of the Rebel Alliance thesis for us is that agents are moving from personified people you hire to cloud infrastructure." "We're not just talking about, 'Will there be other agents that compete with Claude or ChatGPT?' I think that's one version of what agents look like. Another version is cloud infrastructure where every company that's building any system is going to have agents and the orchestration of hundreds or thousands of agents built into their underlying platform." "If you think of agents as infrastructure as opposed to agents as employees, I think that's where a lot of these forces come into play."

TBPN

28,239 просмотров • 13 дней назад

🚨 JUST IN - Q: Will you seek Congressional authorization for any land attacks on cartels in Venezuela? PRESIDENT TRUMP: I don't have to tell them. That's been proven. But I wouldn't mind it - I just hope they wouldn't LEAK it. They're politicians. They leak like a SIEVE!

🚨 JUST IN - Q: Will you seek Congressional authorization for any land attacks on cartels in Venezuela? PRESIDENT TRUMP: I don't have to tell them. That's been proven. But I wouldn't mind it - I just hope they wouldn't LEAK it. They're politicians. They leak like a SIEVE!

Eric Daugherty

225,712 просмотров • 6 месяцев назад

Why OpenClaw will create jobs: " I can't see these as doing anything other than creating a lot more jobs. Like there's just so much more stuff that needs to get built and needs to get managed." "The same thing happened with cloud, right? When cloud came around, I remember sitting in my big corporate job thinking 'half of these people will be gone in five years.'" "And then, lo and behold, 10 years later, 20 years later, the IT organizations are bigger than they were then, and they're spending even more money." " Trying to ignore this new technology and waiting for it to go away usually doesn't work." Yoko Guido Appenzeller on the AI + a16z Podcast

Why OpenClaw will create jobs: " I can't see these as doing anything other than creating a lot more jobs. Like there's just so much more stuff that needs to get built and needs to get managed." "The same thing happened with cloud, right? When cloud came around, I remember sitting in my big corporate job thinking 'half of these people will be gone in five years.'" "And then, lo and behold, 10 years later, 20 years later, the IT organizations are bigger than they were then, and they're spending even more money." " Trying to ignore this new technology and waiting for it to go away usually doesn't work." Yoko Guido Appenzeller on the AI + a16z Podcast

a16z

19,734 просмотров • 3 месяцев назад

We just had the worst crash in crypto history. But that was just the start If I held any crypto besides $ZEC, I'd be running as fast as I could to sell A video covering: - My full system to win big on black swan events & never get liquidated - Why you should never use perp DEXs

We just had the worst crash in crypto history. But that was just the start If I held any crypto besides $ZEC, I'd be running as fast as I could to sell A video covering: - My full system to win big on black swan events & never get liquidated - Why you should never use perp DEXs

Brandon Hong

210,979 просмотров • 9 месяцев назад

Ginkgo Bioworks CEO Jason Kelly explains how "cloud-style" automated science labs can create "millions of scientists" by democratizing access to experimentation: “Science is the formalization of human curiosity. The reason everyone doesn't do science today is that you're blocked by the cost and expense of all the physical infrastructure.” “If it was available cloud-style, for example, how many people would want to be doing science? Maybe they have a health condition they want to study themselves, maybe they have a new idea for a material, maybe they're a gardener and they want to make a new plant variety?” “I know that sounds crazy, but I'll tell you something else that sounded crazy. In 1960, if you said random, average people will program computers, that sounded insane.” "The model’s ability to access literature and be smart and tell you how to turn your question into an experiment—and then the autonomous labs that could do that experiment for you in the cloud—means we'll have millions of scientists, just like we have millions of programmers now as we made it easier."

Ginkgo Bioworks CEO Jason Kelly explains how "cloud-style" automated science labs can create "millions of scientists" by democratizing access to experimentation: “Science is the formalization of human curiosity. The reason everyone doesn't do science today is that you're blocked by the cost and expense of all the physical infrastructure.” “If it was available cloud-style, for example, how many people would want to be doing science? Maybe they have a health condition they want to study themselves, maybe they have a new idea for a material, maybe they're a gardener and they want to make a new plant variety?” “I know that sounds crazy, but I'll tell you something else that sounded crazy. In 1960, if you said random, average people will program computers, that sounded insane.” "The model’s ability to access literature and be smart and tell you how to turn your question into an experiment—and then the autonomous labs that could do that experiment for you in the cloud—means we'll have millions of scientists, just like we have millions of programmers now as we made it easier."

TBPN

13,054 просмотров • 5 месяцев назад

META launches a new feature that will allow Facebook and Instagram to continuously scan all your photos and video and upload them to their cloud “Facebook is now using AI to scan every single photo and video within your phone — This is terrifying. Not only are they scanning those photos and videos, but then they're uploading it to the cloud continuously. It's operating continuously in the background scanning those photos to figure out the time of day, the location, the other people in your photos, that it can determine what it thinks you should post” The scanning happens on-device using AI models for suggestions, but Meta can upload and process data to the cloud when you interact It’s in opt in feature, so make sure to never opt in and if you have make sure to opt out The service is called ‘Camera Roll Sharing Suggestions’

META launches a new feature that will allow Facebook and Instagram to continuously scan all your photos and video and upload them to their cloud “Facebook is now using AI to scan every single photo and video within your phone — This is terrifying. Not only are they scanning those photos and videos, but then they're uploading it to the cloud continuously. It's operating continuously in the background scanning those photos to figure out the time of day, the location, the other people in your photos, that it can determine what it thinks you should post” The scanning happens on-device using AI models for suggestions, but Meta can upload and process data to the cloud when you interact It’s in opt in feature, so make sure to never opt in and if you have make sure to opt out The service is called ‘Camera Roll Sharing Suggestions’

Wall Street Apes

199,855 просмотров • 1 день назад

Dear ICP community, the Internet Computer has now been running strong for 5 years 👏👏👏 Here is a celebratory preview of ICP "cloud engines," the sovereign frontier cloud technology the network shall soon provide from Main points: — Cloud engines enable anyone to spin up their own sovereign frontier cloud. The technology involves an extraordinary inventive step, in which cloud is created from a mathematically secure network of nodes. The nodes run as part of the Internet Computer network ( but are selected and configured by the cloud engine's owner. — The frontier cloud provided by engines is strongly focused on enabling AI agents to build and update online applications and services for us. The world is changing fast, and nearly all new online apps and services are already being built with the help of AI, and thus cloud engines target the future of cloud. — Software hosted on cloud engines is tamperproof, which means that it is immune to infrastructure hacks, because it runs inside a mathematically secure network protocol, rather than on computers directly. This means that AI agents, and those building with them, don't need to have a security team in the loop, or to trust someone else's security team. This is crucial, because in the future, non technical people will demand the freedom to build with full automation — where they just need to issue instructions to AI about what to build, and don't need to worry about anything or anyone else. Of course, apps and services running on engines are also vastly safer from the new breed of hacker being enabled by frontier AI. (The cloud engines themselves are also "tamperproof." Even if a hacker gains physical access to some portion of a cloud engine's nodes, and can make arbitrary changes, the computations and data of the hosted apps and services cannot be corrupted or interrupted so long as the network's fault bounds aren't exceeded. The recent hack of Vercel, a major cloud platform, which gave hackers access to the apps it hosted, provides additional perspective on the importance of this advantage.) — Software hosted on cloud engines is guaranteed to run, so long as a sufficient number of the engine's nodes are running. This means that AI can build applications and services without the need to have a human systems admin team constantly tinkering with the underlying platform to keep it running, which is again crucial, because in the future, non technical people will expect the freedom to use AI to build without the support of others. — New frontier programming language technology, in the form of the Motoko language developed by Caffeine Labs, leverages seminal "orthogonal persistence" technology that unifies program logic and data to deliver further unlocks for AI (Motoko is the first computer language being developed that targets agents that are writing software rather than humans engineers per se). Nowadays, AI can build and update production apps at a prodigious rate, even at the speed of conversation. But it can also make mistakes, and there's a risk that an update it creates might be "lossy" in the sense it causes some transformed data to be lost. Again, in this new world, it's both undesirable and impractical for everyone to have to have a systems admin team on-hand to detect lossy updates and roll them back, but Motoko provides a solution: it can detect new software updates are lossy before they are applied, reducing potentially catastrophic errors by AI to harmless coding retries. — Software hosted on cloud engines is "serverless" but unlike traditional serverless software, directly it directly incorporates data through "orthogonal persistence." Another key purpose is simplify backend software logic and fuel the modeling power of AI by increasing abstraction (sorry for the technical language!!!). Put simply, this enables AI to produce more sophisticated backends, faster, and at dramatically lower costs, as measured by the number AI API tokens consumed during coding. (Tip for the technical: orthogonal persistence is a new paradigm where "the program is the database," and data lives inside program variables, which is possible because it's as if hosted software runs forever in persistent memory). — An expanding database of skills at shall make it possible to develop and directly deploy apps and services to your cloud engines directly from Claude Code, Perplexity, Codex and other AI platforms. Further, your account on can be connected, so that new apps and updates created through conversation automatically appear hosted from your cloud engine. In the future, R&D is going to be very seamless. You converse with AI, and your secure and unstoppable apps or services are created or updated. Cloud engines are designed to directly support this "self-writing cloud" future where we can work hands-free. — Tech sovereignty is becoming a huge issue worldwide, with governments and corporations seeking to create sovereign tech stacks owing to geopolitical tensions. Increasingly, people are realizing that tech provided by foreign nations can come with hidden backdoors and kills switches, from the base platform, right up through hosted apps and services. ICP technology is open source, and those building on ICP using AI own their own source code. When you have the source code, you can verify that there are no backdoors, and when you own the source code thanks to AI, you can update it at will, freeing you from vendor lock-in. But cloud engines take sovereignty much further... — You create a cloud engine by selecting the nodes that will be combined. You can choose the class of nodes used, and their number, but more importantly, you can choose who operates the nodes, and where they are located. Almost any configuration is possible, because the Internet Computer scales the security privileges afforded to hosted software within the network according to configuration (software hosted on cloud engines can directly interoperate with software on other engines and traditional subnets, but base restrictions are applied according to security rules). A cloud engine can be created within a region such as Europe, to comply with regs such as GDPR, or completely within a sovereign state like Switzerland or Pakistan. But cloud engines go further still... — Sovereignty is also about freedom from vendor lock-in. Cloud engines are essentially ICP (Internet Computer Protocol) network configurations, and this means the underlying compute nodes they combine can be swapped out without interrupting their hosted apps and services. This is a big deal. In addition, cloud engines now support nodes that are instances running on Big Tech's clouds, in addition to nodes that are dedicated specialized hardware, as per the Gen I and Gen II nodes that dominate the Internet Computer today. For example, it is possible to have an engine running across different AWS data centers, say, and then reconfigure the engine to run across a mixture of AWS, Google, Azure and Hetzner for even more resilience, without the users of hosted apps and services noticing a thing. That's true freedom. — Sovereign AI is becoming increasingly important too, and cloud engines allow special "AI nodes" to be added to them, so that hosted software can perform inference on hardware provisioned by the owner from a location the owner has selected. Even though the AI nodes are only accessible within the cloud engine, they can still benefit from the forthcoming Internet Intelligence Gateway (IG), which will make it possible to validate inference performed on key frontier open weights LLMs, even when the inference is performed on completely independent AI clouds. When the results of inference are received, this technology can verify that neither the prompt+context (input) nor the inference result (output) have been modified, and that the results were produced by the precise LLM expected. This ensures that AI clouds don't cheat by running inference on cheaper models than are being paid for, and bad actors aren't modifying the inputs or outputs to surreptitiously insert advertising into results, say, or change facts, or insert malware when code is being generated. What's super cool about this technology is the cost of the verification is scalable. A very valuable additional security can be achieved with only 1-2% of extra cost. — Scaling apps and services when they hit capacity limits is another thorny problem that cloud engines help the world address. Engines make scaling possible without rewriting or reconfiguring software. The query workload capacity of hosted software can be horizontally scaled simply by adding new nodes to an engine, and nodes can also be added in geographical proximity to demand. Meanwhile, update workload capacity can first be scaled-up by swapping an engine's nodes out for the next class up, and then when no larger class of node is available, horizontally scaled-out by "splitting" the engine into two, which doubles available capacity. (Technical tip: horizontally scaling update capacity by splitting engines requires multi-canister architectures). — For those who have been following how Caffeine builds apps that can efficiently store large numbers of files, I should mention that apps built on cloud engines will also support the new ICP Blob Storage cloud network (since cloud engines currently have up to about 3 TB of memory, which apps storing large amounts of files can easily exceed). We are also working on allowing blob storage nodes to be added to cloud engines, to enable sovereign mass blob storage within an engine, similarly to how AI nodes can be added currently. — Lastly, but certainly not least, I should mention that cloud engines are multi-blockchain capable, and ready for digital assets, thanks to the clever math at their core. For example, an e-commerce service built on a cloud engine can securely accept and custody stablecoin payments, or a multi-chain DEX could be hosted. Further, engines can support software autonomy (software orchestrated and controlled by other autonomous software, in a decentralized way) and can themselves be orchestrated by SNS technology, and thus run autonomously too. Today, though, the focus is on *mainstream* cloud. This year, the cloud industry will generate approximately one trillion dollars in revenue. That number is already huge, but is expected to grow to two trillion dollars by 2030. After years of continuous development, which have seen more than $500m spent on R&D, the Internet Computer network is now tacking directly toward this mainstream cloud market with cloud engine technology. In their first version, cloud engines are not meant to be a cloud panacea. For example, currently they are not ideal for working with big data. You should use something like DataBricks for that. Cloud engines are carefully targeted at enabling AI to produce traditional online applications and services, including SaaS, in a safer and more productive way, which represents a new market segment with tremendous potential. Of course, DFINITY will continue to work relentlessly to push forward ICP's capabilities, so expect further developments. It's worth mentioning that this cloud segment isn't just about creating new apps and services using AI, it's also about replacing legacy systems and apps built on super expensive SaaS services. Caffeine Labs is working to produce technology (Caffeine Snorkel) that can study an enterprise's legacy systems and app built on SaaS, create replacement systems and apps, and migrate the data, while supporting key stakeholders through the process over email and chat, with full automation. Thus the legacy systems and SaaS markets shall also be addressed by cloud engines. Zooming out, and reasoning in a more metaphysical way, we believe, as we always have, that there is room for a new kind of cloud created by mathematical networks, that provides seminal advances in the fields of security and resilience, as well as true sovereignty and freedom from lock-in. That this same technology, with the help of additional technologies like orthogonal persistence and Motoko, enables AI to build for us without the need for so much oversight, and to create more backend sophistication while consuming fewer AI API tokens, enables ICP to bring game-changing advances to the world. Cloud engines will work synergistically with the Intelligence Gateway, which will enable apps and services running on engines to seamlessly leverage AI, wherever that AI is running, while providing verifiability at extremely low cost for open weights frontier models. We believe that cloud engines represent an inflection point in the storied history of the Internet Computer project, and I'm very proud to be sharing the details with you on the network's fifth birthday 💪 I'll be back with more news soon!!

Dear ICP community, the Internet Computer has now been running strong for 5 years 👏👏👏 Here is a celebratory preview of ICP "cloud engines," the sovereign frontier cloud technology the network shall soon provide from Main points: — Cloud engines enable anyone to spin up their own sovereign frontier cloud. The technology involves an extraordinary inventive step, in which cloud is created from a mathematically secure network of nodes. The nodes run as part of the Internet Computer network ( but are selected and configured by the cloud engine's owner. — The frontier cloud provided by engines is strongly focused on enabling AI agents to build and update online applications and services for us. The world is changing fast, and nearly all new online apps and services are already being built with the help of AI, and thus cloud engines target the future of cloud. — Software hosted on cloud engines is tamperproof, which means that it is immune to infrastructure hacks, because it runs inside a mathematically secure network protocol, rather than on computers directly. This means that AI agents, and those building with them, don't need to have a security team in the loop, or to trust someone else's security team. This is crucial, because in the future, non technical people will demand the freedom to build with full automation — where they just need to issue instructions to AI about what to build, and don't need to worry about anything or anyone else. Of course, apps and services running on engines are also vastly safer from the new breed of hacker being enabled by frontier AI. (The cloud engines themselves are also "tamperproof." Even if a hacker gains physical access to some portion of a cloud engine's nodes, and can make arbitrary changes, the computations and data of the hosted apps and services cannot be corrupted or interrupted so long as the network's fault bounds aren't exceeded. The recent hack of Vercel, a major cloud platform, which gave hackers access to the apps it hosted, provides additional perspective on the importance of this advantage.) — Software hosted on cloud engines is guaranteed to run, so long as a sufficient number of the engine's nodes are running. This means that AI can build applications and services without the need to have a human systems admin team constantly tinkering with the underlying platform to keep it running, which is again crucial, because in the future, non technical people will expect the freedom to use AI to build without the support of others. — New frontier programming language technology, in the form of the Motoko language developed by Caffeine Labs, leverages seminal "orthogonal persistence" technology that unifies program logic and data to deliver further unlocks for AI (Motoko is the first computer language being developed that targets agents that are writing software rather than humans engineers per se). Nowadays, AI can build and update production apps at a prodigious rate, even at the speed of conversation. But it can also make mistakes, and there's a risk that an update it creates might be "lossy" in the sense it causes some transformed data to be lost. Again, in this new world, it's both undesirable and impractical for everyone to have to have a systems admin team on-hand to detect lossy updates and roll them back, but Motoko provides a solution: it can detect new software updates are lossy before they are applied, reducing potentially catastrophic errors by AI to harmless coding retries. — Software hosted on cloud engines is "serverless" but unlike traditional serverless software, directly it directly incorporates data through "orthogonal persistence." Another key purpose is simplify backend software logic and fuel the modeling power of AI by increasing abstraction (sorry for the technical language!!!). Put simply, this enables AI to produce more sophisticated backends, faster, and at dramatically lower costs, as measured by the number AI API tokens consumed during coding. (Tip for the technical: orthogonal persistence is a new paradigm where "the program is the database," and data lives inside program variables, which is possible because it's as if hosted software runs forever in persistent memory). — An expanding database of skills at shall make it possible to develop and directly deploy apps and services to your cloud engines directly from Claude Code, Perplexity, Codex and other AI platforms. Further, your account on can be connected, so that new apps and updates created through conversation automatically appear hosted from your cloud engine. In the future, R&D is going to be very seamless. You converse with AI, and your secure and unstoppable apps or services are created or updated. Cloud engines are designed to directly support this "self-writing cloud" future where we can work hands-free. — Tech sovereignty is becoming a huge issue worldwide, with governments and corporations seeking to create sovereign tech stacks owing to geopolitical tensions. Increasingly, people are realizing that tech provided by foreign nations can come with hidden backdoors and kills switches, from the base platform, right up through hosted apps and services. ICP technology is open source, and those building on ICP using AI own their own source code. When you have the source code, you can verify that there are no backdoors, and when you own the source code thanks to AI, you can update it at will, freeing you from vendor lock-in. But cloud engines take sovereignty much further... — You create a cloud engine by selecting the nodes that will be combined. You can choose the class of nodes used, and their number, but more importantly, you can choose who operates the nodes, and where they are located. Almost any configuration is possible, because the Internet Computer scales the security privileges afforded to hosted software within the network according to configuration (software hosted on cloud engines can directly interoperate with software on other engines and traditional subnets, but base restrictions are applied according to security rules). A cloud engine can be created within a region such as Europe, to comply with regs such as GDPR, or completely within a sovereign state like Switzerland or Pakistan. But cloud engines go further still... — Sovereignty is also about freedom from vendor lock-in. Cloud engines are essentially ICP (Internet Computer Protocol) network configurations, and this means the underlying compute nodes they combine can be swapped out without interrupting their hosted apps and services. This is a big deal. In addition, cloud engines now support nodes that are instances running on Big Tech's clouds, in addition to nodes that are dedicated specialized hardware, as per the Gen I and Gen II nodes that dominate the Internet Computer today. For example, it is possible to have an engine running across different AWS data centers, say, and then reconfigure the engine to run across a mixture of AWS, Google, Azure and Hetzner for even more resilience, without the users of hosted apps and services noticing a thing. That's true freedom. — Sovereign AI is becoming increasingly important too, and cloud engines allow special "AI nodes" to be added to them, so that hosted software can perform inference on hardware provisioned by the owner from a location the owner has selected. Even though the AI nodes are only accessible within the cloud engine, they can still benefit from the forthcoming Internet Intelligence Gateway (IG), which will make it possible to validate inference performed on key frontier open weights LLMs, even when the inference is performed on completely independent AI clouds. When the results of inference are received, this technology can verify that neither the prompt+context (input) nor the inference result (output) have been modified, and that the results were produced by the precise LLM expected. This ensures that AI clouds don't cheat by running inference on cheaper models than are being paid for, and bad actors aren't modifying the inputs or outputs to surreptitiously insert advertising into results, say, or change facts, or insert malware when code is being generated. What's super cool about this technology is the cost of the verification is scalable. A very valuable additional security can be achieved with only 1-2% of extra cost. — Scaling apps and services when they hit capacity limits is another thorny problem that cloud engines help the world address. Engines make scaling possible without rewriting or reconfiguring software. The query workload capacity of hosted software can be horizontally scaled simply by adding new nodes to an engine, and nodes can also be added in geographical proximity to demand. Meanwhile, update workload capacity can first be scaled-up by swapping an engine's nodes out for the next class up, and then when no larger class of node is available, horizontally scaled-out by "splitting" the engine into two, which doubles available capacity. (Technical tip: horizontally scaling update capacity by splitting engines requires multi-canister architectures). — For those who have been following how Caffeine builds apps that can efficiently store large numbers of files, I should mention that apps built on cloud engines will also support the new ICP Blob Storage cloud network (since cloud engines currently have up to about 3 TB of memory, which apps storing large amounts of files can easily exceed). We are also working on allowing blob storage nodes to be added to cloud engines, to enable sovereign mass blob storage within an engine, similarly to how AI nodes can be added currently. — Lastly, but certainly not least, I should mention that cloud engines are multi-blockchain capable, and ready for digital assets, thanks to the clever math at their core. For example, an e-commerce service built on a cloud engine can securely accept and custody stablecoin payments, or a multi-chain DEX could be hosted. Further, engines can support software autonomy (software orchestrated and controlled by other autonomous software, in a decentralized way) and can themselves be orchestrated by SNS technology, and thus run autonomously too. Today, though, the focus is on mainstream cloud. This year, the cloud industry will generate approximately one trillion dollars in revenue. That number is already huge, but is expected to grow to two trillion dollars by 2030. After years of continuous development, which have seen more than $500m spent on R&D, the Internet Computer network is now tacking directly toward this mainstream cloud market with cloud engine technology. In their first version, cloud engines are not meant to be a cloud panacea. For example, currently they are not ideal for working with big data. You should use something like DataBricks for that. Cloud engines are carefully targeted at enabling AI to produce traditional online applications and services, including SaaS, in a safer and more productive way, which represents a new market segment with tremendous potential. Of course, DFINITY will continue to work relentlessly to push forward ICP's capabilities, so expect further developments. It's worth mentioning that this cloud segment isn't just about creating new apps and services using AI, it's also about replacing legacy systems and apps built on super expensive SaaS services. Caffeine Labs is working to produce technology (Caffeine Snorkel) that can study an enterprise's legacy systems and app built on SaaS, create replacement systems and apps, and migrate the data, while supporting key stakeholders through the process over email and chat, with full automation. Thus the legacy systems and SaaS markets shall also be addressed by cloud engines. Zooming out, and reasoning in a more metaphysical way, we believe, as we always have, that there is room for a new kind of cloud created by mathematical networks, that provides seminal advances in the fields of security and resilience, as well as true sovereignty and freedom from lock-in. That this same technology, with the help of additional technologies like orthogonal persistence and Motoko, enables AI to build for us without the need for so much oversight, and to create more backend sophistication while consuming fewer AI API tokens, enables ICP to bring game-changing advances to the world. Cloud engines will work synergistically with the Intelligence Gateway, which will enable apps and services running on engines to seamlessly leverage AI, wherever that AI is running, while providing verifiability at extremely low cost for open weights frontier models. We believe that cloud engines represent an inflection point in the storied history of the Internet Computer project, and I'm very proud to be sharing the details with you on the network's fifth birthday 💪 I'll be back with more news soon!!

dom | icp

259,534 просмотров • 2 месяцев назад

🚨 New Tutorial Alert 🚨 Rendering Google Earth Engine & Cloud-Optimized GeoTIFF Tiles in 3D with Google Earth In this tutorial, I demonstrate how to visualize Google Earth Engine tile layers and Cloud Optimized GeoTIFFs (COGs) directly in Google Earth’s 3D environment. This approach lets you bring together high-resolution historical imagery and Street View data into one powerful platform. It’s a simple but effective way to make your geospatial data more accessible—just like sharing a Google Doc link. 🔗 Notebook: ▶️ Video: #geospatial #googleearth #dataviz #earthengine

🚨 New Tutorial Alert 🚨 Rendering Google Earth Engine & Cloud-Optimized GeoTIFF Tiles in 3D with Google Earth In this tutorial, I demonstrate how to visualize Google Earth Engine tile layers and Cloud Optimized GeoTIFFs (COGs) directly in Google Earth’s 3D environment. This approach lets you bring together high-resolution historical imagery and Street View data into one powerful platform. It’s a simple but effective way to make your geospatial data more accessible—just like sharing a Google Doc link. 🔗 Notebook: ▶️ Video: #geospatial #googleearth #dataviz #earthengine

Qiusheng Wu

16,391 просмотров • 10 месяцев назад

i have my opinions on Surrogate but you will LICHURALLY never be able to tell me this part is "just noise" like, this is my favorite drop I've seen in any FNF song this year

i have my opinions on Surrogate but you will LICHURALLY never be able to tell me this part is "just noise" like, this is my favorite drop I've seen in any FNF song this year

Sophie (COMMS OPEN)

34,357 просмотров • 1 год назад

Apple announces Swift Assist for Xcode 16! "Swift Assist serves as a companion for all of a developer’s coding tasks, so they can focus on higher-level problems and solutions. It’s seamlessly integrated into Xcode, and knows the latest software development kits (SDKs) and Swift language features, so developers will always get the latest code features that blend perfectly into their projects. With Swift Assist, tasks like exploring new frameworks and experimenting with new ideas are just one request away. Swift Assist uses a powerful model that runs in the cloud — and like all Apple developer services, it is built with privacy and security in mind. Developers’ code is only used to process requests and never stored on servers, and Apple will not use it to train machine learning models." Swift Assist is coming later this year to Xcode 16.

Apple announces Swift Assist for Xcode 16! "Swift Assist serves as a companion for all of a developer’s coding tasks, so they can focus on higher-level problems and solutions. It’s seamlessly integrated into Xcode, and knows the latest software development kits (SDKs) and Swift language features, so developers will always get the latest code features that blend perfectly into their projects. With Swift Assist, tasks like exploring new frameworks and experimenting with new ideas are just one request away. Swift Assist uses a powerful model that runs in the cloud — and like all Apple developer services, it is built with privacy and security in mind. Developers’ code is only used to process requests and never stored on servers, and Apple will not use it to train machine learning models." Swift Assist is coming later this year to Xcode 16.

M1

79,615 просмотров • 2 лет назад

SCHIFF: "Will you be able to review hundreds of cases on day one? Of course you won't..." BONDI: "Can I answer the question? You were censured by Congress, Senator, for comments just like this & they're so reckless!" 🔥🔥🔥

SCHIFF: "Will you be able to review hundreds of cases on day one? Of course you won't..." BONDI: "Can I answer the question? You were censured by Congress, Senator, for comments just like this & they're so reckless!" 🔥🔥🔥

Breaking911

2,809,194 просмотров • 1 год назад

On today’s episode of “Pissing off the HOA”, the neighbors have decided that today they will pretend to be fertilizing their lawns just to say FAFO. I don’t know about you, but I love the new addition to the golf cart! How long do you think this war will continue? I don’t see either side backing down any time soon. 😂

On today’s episode of “Pissing off the HOA”, the neighbors have decided that today they will pretend to be fertilizing their lawns just to say FAFO. I don’t know about you, but I love the new addition to the golf cart! How long do you think this war will continue? I don’t see either side backing down any time soon. 😂

CeCe

244,920 просмотров • 18 дней назад