Acurast

• Name: Acurast
• URL: https://acurast.com/
• Category: Decentralized compute network / phone-powered confidential-compute infrastructure / TEE-backed DePIN
• Summary: Acurast is a decentralized compute network that uses smartphones as attested compute providers instead of centralized data centers. Its official docs make the operating model unusually concrete: developers package Node.js jobs with an Acurast CLI, deploy them onto the network, and target attested phone-based processors that can run either as dedicated Android nodes or lighter edge-time workers on everyday devices. The project sits in a useful crypto-adjacent lane because it blends decentralized infrastructure, trusted execution environments, onchain coordination, and developer tooling into a verifiable compute marketplace rather than a simple consumer app.
• What it does:
  • Lets developers deploy JavaScript/Node.js workloads to a decentralized network of smartphone-based processors
  • Uses attested devices and phone TEEs as the trust anchor for confidentiality and hardware authenticity
  • Offers a CLI, docs, example apps, and deployment config (acurast.json) for shipping jobs onto the network
  • Supports dedicated Android “Processor Core” nodes and lighter “Processor Lite” participation on Android and iOS devices
  • Maintains an open GitHub surface spanning the CLI, Substrate chain, docs, SDKs, example apps, indexer, and processor-management components
• Key claims:
  • Official docs describe Acurast as a verifiable, scalable, and confidential compute network powered by smartphones rather than data centers
  • The docs homepage says the incentivized testnet had onboarded 227,181 compute units worldwide and processed more than 250 million transactions on testnet at the time of review
  • Acurast says its network is active across 140+ countries and already powers security-sensitive workloads
  • The processor docs position dedicated Android Core devices as higher-reliability nodes for longer-running or more critical deployments, while Lite broadens supply through everyday phones
  • The deployment tutorial shows a concrete developer workflow using an Acurast CLI, faucet-funded accounts, project manifests, encrypted environment variables, and optional USDC-on-Base deployment via a Deploy Agent
• Whitepaper: No classic standalone whitepaper or litepaper was found during this pass. The strongest primary materials were Acurast’s official docs homepage, deployment tutorial, processor documentation, and GitHub organization/repositories; see ../whitepapers/acurast-primary-sources-2026-04-26.md.
• Sources:
  • https://acurast.com/
  • https://docs.acurast.com/
  • https://docs.acurast.com/developers/deploy-first-app/
  • https://docs.acurast.com/acurast-processors/
  • https://github.com/Acurast
  • https://raw.githubusercontent.com/Acurast/acurast-docs/main/README.md

Internal linkages

• Best comparisons: fluence for the data-center marketplace contrast and lilypad for the heavier crypto-economic verification layer.

Control surface

• The leverage sits in processor admission, attestation policy, job-routing defaults, developer tooling, and how much practical trust actually rests on the Acurast-managed deployment path versus the raw device supply.

• So keep the note grounded. Acurast is useful because the phone-TEE trust model is concrete, not because every decentralized compute label suddenly means the same thing.

• Last reviewed: 2026-04-26 UTC