Analytics

Loading network analytics

Aggregating processor health, deployment metrics, and network-wide trends.

Resolving route12%

Acurast Pulse

Loading live view

Syncing chain state, reward ledgers, and fleet telemetry.

Resolving route12%

Workload Composition | Acurast Pulse

19.7kDeployments / 30d

658Per day (avg)

48Distinct deployers

NodeJSWithBundleDominant runtime

competingDominant strategy

0.81Median reward (ACU)

643In execution window now

Daily new deployments

Last 30 days · peak 779 on 2026-06-06

NodeJS bundle · 19,581NodeJS bare · 78Cargo (Shell) · 78

2026-05-082026-06-07

Execution cadence

how often the network's deploys run

Bucketed by schedule.interval on each deploy. The dominant cadence tells you the typical workload rhythm.

every ≤1 min0.1%22

every 1-5 min0.1%26

every 5-60 min1.4%285

every 1-24 h3.6%716

every 1-7 d94.7%18,688

Job lifetime

endTime − startTime distribution

Total deployment window length. Short bursts (≤1h) vs. long-running daemons (≥3 months).

≤1 hour1.2%237

1-24 h98.6%19,453

Composition breakdown

Runtime split

NodeJSWithBundle99.2%19,581

NodeJS0.4%78

Cargo (Shell)0.4%78

Strategy split

competing94.7%18,685

single5.3%1,052

Replicas requested

15.1%999

20.1%21

30.1%

Resource ceilings declared

of 19,737 deployments

How many deployments asked for an explicit constraint vs. taking the protocol default (effectively unlimited).

Memory ceiling622 (3.2%)

Storage ceiling617 (3.1%)

Network request budget809 (4.1%)

Required modules121 (0.6%)

Whitelisted sources597 (3.0%)

Verified-only19,147 (97.0%)

Top deployers

by deployment count

Per-execution reward

distribution across the cohort

Median (p50)0.81 ACUhalf of deployments pay at most this per execution

High end (p99)1.08 ACUonly the top 1% pay more than this

What do these terms mean?

Runtime: The execution environment the deployer requests on processors. NodeJSWithBundle is the standard — a packaged JS bundle that runs in Acurast's Node-on-mobile runtime. NodeJS is the bare Node runtime without bundle. Cargo (Shell) is a containerized deployment: a custom rootfs image (URL + SHA256) is downloaded onto the processor and the entrypoint script runs inside it — supports any language/binary that fits in a container (Python, Rust, native, etc.). Promoted from canary to stable on 2026-05-18.
Strategy: Single — one processor handles the deployment alone. Competing — N processors race for the same job slots; rewards split among those who report successfully.
Replicas (slots): How many concurrent processor slots the deployer asked for. Competing deployments usually request many; single-strategy is always 1.
Mutability: Immutable — the deployment's spec can never be changed after registration. Mutable — the registered editor can update certain fields (typically the script URL).
Reward / execution: The maximum cost cap per execution attempt (paid to processors out of the deployer's funded balance). Real cost can be less; this is the ceiling.
Resource ceilings: Optional per-execution caps the deployer enforces. Most deployments leave these at 0 / unset, accepting the protocol default.

Window: last 30 days (since 2026-05-08)Refreshed 45 min ago