The cloud was never meant to be owned by giants.
@Acurast is taking it back, phone by phone.
Join the #CloudRebellion and help push decentralized compute back to the people: https://t.co/bM27LFdOsa
#Acurast#DePIN
Cloudflare just confirmed it: agents now outnumber humans on the web.
57.4% of all traffic is automated, most of it AI agents browsing and acting for us. The crossover wasn't expected until 2027. It happened this week.
Every one of those agents runs somewhere. Right now that means a handful of centralized clouds. One outage, one policy change, and part of the agentic internet goes dark.
Acurast runs a network of 260,000+ smartphones across 175+ countries. Real devices, no data centers, no single point of failure. Acurast is the compute layer the agentic internet actually needs.
Join the rebellion:
https://t.co/3oBAEjo1RD
@Acurast The internet quietly crossed a line and most people didn’t even notice. We spent years talking about AI agents, now they’re already the majority traffic online. Go @Acurast
Acurast and Numbers Protocol are exploring a question the AI industry can’t avoid forever: how do you verify what autonomous systems are doing?
Decentralized compute is one piece of the puzzle. Provenance, accountability and verifiable outputs are the other. The combination of @Acurast’s phone-powered infrastructure and @numbersprotocol’s authenticity framework points toward AI systems that are trustworthy by design, not by marketing.
Missed our live deep dive with @numbersprotocol ?
We broke down what the infrastructure stack looks like when accountability is built into autonomous AI from the ground up.
Tune in: https://t.co/6HqG9BM1jO
@Acurast@numbersprotocol The interesting part isn’t just autonomous AI. It’s making sure AI can actually prove where its outputs came from. @Acurast + @numbersprotocol are tackling the trust layer most projects leave as an afterthought.
Compute is scarce. Old smartphones are not.
@Acurast closes that gap, turning the most abundant piece of personal hardware in the world into productive, rewarded infrastructure.
Your spare phone isn't dead. It's just waiting.
The @peaq pay-per-skill leasing idea reframes robotics from “sell the machine, lose the upside” to “own a slice of every job it performs.”
That matters because autonomous machines will not just need financing. They will need revenue rails, insurance logic, usage tracking, and settlement built into the runtime itself.
Robots earning on-chain is not a gimmick. It is infrastructure for machines becoming economic actors.
#peaq #DePIN
.@peaq is pointing at a real shift here. Robots are becoming productive assets, not just hardware SKUs. When revenue can be split automatically per task, the manufacturer, financier, and insurer can all sit inside the same machine economy without drowning in invoices.
@peaq This is the part most robotics decks politely skip: selling the machine once is easy. Owning the upside after it starts earning is the actual business model. GJ @peaq
.@numbersprotocol and @Acurast are lining up the two pieces AI agents will badly need: provenance and verifiable compute.
Because once autonomous agents start acting for users, “trust me bro” stops being infrastructure. The real question is who can prove what happened, where it happened, and why.
Numbers Protocol is joining @Acurast for an X Space tomorrow.
Subject: verifiable AI agents. What it means to run autonomous agents on infrastructure that can prove what it did.
Numbers Protocol brings the provenance layer. Acurast brings the decentralized compute layer. The overlap is the accountability question: when an agent acts, is there a record?
Set a reminder: https://t.co/HuaEa5UfW9
Cargo might be one of the most important upgrades @Acurast has shipped so far.
Before Cargo, developers were boxed into a much narrower runtime. Now Acurast brings full Linux workload support to a decentralized network of real Android smartphones.
That turns “cloud in your pocket” from a slogan into actual infrastructure, with VPS-like workflows, SSH access, and support for Python, Go, Rust, and more.
It opens the door for AI agents, automation, backend services, and workloads that need cheaper, distributed, confidential compute.
Acurast is not trying to copy the cloud....
It is trying to make the cloud harder to monopolize!
Watch the clip:
https://t.co/xVjbFkLUz6
#Acurast #DePIN @a_d_c_
Cargo might be one of the most important upgrades @Acurast has shipped so far.
Before Cargo, developers were boxed into a much narrower runtime. Now Acurast brings full Linux workload support to a decentralized network of real Android smartphones.
That turns “cloud in your pocket” from a slogan into actual infrastructure, with VPS-like workflows, SSH access, and support for Python, Go, Rust, and more.
It opens the door for AI agents, automation, backend services, and workloads that need cheaper, distributed, confidential compute.
Acurast is not trying to copy the cloud....
It is trying to make the cloud harder to monopolize!
Watch the clip:
https://t.co/xVjbFkLUz6
#Acurast #DePIN @a_d_c_
Acurast’s Cargo upgrade is a big deal because it turns the network from “decentralized compute with limits” into something much closer to a real cloud layer.
Linux workloads, familiar developer tooling, and secure execution across phones. That is not just a feature drop, that is @Acurast widening the door.
@Acurast@a_d_c_ This is the kind of “small word, huge upgrade” moment that actually matters. Cargo sounds simple until you realize it basically removes the training wheels. @Acurast
.@Acurast Cargo running full Linux containers on Android phones is where things get properly interesting.
My first spin-up would be a lightweight API/backend, because that’s the cleanest test: uptime, latency, logs, deployment flow, and whether decentralized phone compute can feel boring in the best possible way.
Cargo runs full Linux containers on Android phones. Which means you can deploy almost anything to the network now.
What's the first thing you'd spin up?
Whatever you picked, drop the actual idea below. Our favourite idea gets a walkthrough.
@Acurast I’d pick An API or backend first. Not the flashiest answer, but usually the one that turns “cool infra” into something people actually build on. @Acurast