An open-source Solana crank protocol: the buyer posts a task with a per-crank SOL reward and any anonymous signer may execute it, so firing is time-only, but the executor set, the due-condition and the failed run are all public chain state — and a task can return its own successor, keeping a conditional loop entirely onchain. Strongest on what can fire the call, against what target, and who can check the condition was true (8/10): Firing is time-only: the TriggerV0 enum holds Now and Timestamp(i64), and a separate cron program queues tasks on a schedule. A task can call any instruction on any program, and RunTaskV0 checks the due-condition onchain ("task.trigger.is_active()"), so anyone can replay it. Weakest on the lateness the vendor will put in writing, and the conditions under which it declines to execute (6/10): No SLA, uptime figure or check cadence is published; the homepage promises tasks "run on time, every time". The docs state the decline conditions: the reward must exceed the crank cost or "crankers will not be incentivized to run your task", and a cron that runs out of funding leaves the queue. Published price: No rate card, subscription or vendor invoice exists; the only price mechanics are on https://
Automation & Keepers
Automation & Keepers evaluated across whether the job survives the vendor, what can fire the call and who can check the condition was true, whether a run that never happened is visible, and the lateness the vendor will put in writing.
Ranked here: automation and keeper services that notice when a contract call comes due and then make that call happen, for operators running routine business logic on a deadline. Not ranked here: services that only submit a transaction you have already decided to send, and security monitoring built to catch an attacker rather than run routine business logic.
Show the arithmetic
How this page is reviewed
Reviewed means every product ranked on this page was read against its sources on or after that date; every ranked category is re-read at least every 45 days. Models research, extract and parse. A deterministic engine ranks. Every quote passes an adversarial refute pass.
Accountable for this review: Mathias Siemonsmeier, Founder.
How we review · Review calendar · Corrections log · How we make money
Ranked on 4 published criteria weighted 28/30/24/18, which set goal alignment — 30 of the 86 points. The rest: regional access 20 (constant here), evidence depth 18 (constant here), ease of use 10 (constant here), institutional trust 8 (constant here). Profile match is shown in breakdowns but carries no weight.
- Control failure: a key or vote changes the rules, freezes or mints.Scored by What can fire the call, against what target, and who can check the condition was true · 28% (TukTuk (Helium) 8/10, KeeperHub 6/10, Reactive Network 8/10)
- Liveness failure: the operator stops, censors you or loses data.Scored by Whether a run that never happened is visible, or the job just goes quiet · 24% (TukTuk (Helium) 7/10, KeeperHub 4/10, Reactive Network 7/10)
- Execution failure: you get a worse price, later, or nothing.Scored by The lateness the vendor will put in writing, and the conditions under which it declines to execute · 18% (TukTuk (Helium) 6/10, KeeperHub 7/10, Reactive Network 5/10)
- Exit failure: you cannot get out at par, on time, or with what is yours.Scored by Whether the job survives the vendor: who else can turn the crank, and what end-of-life is published · 30% (TukTuk (Helium) 8/10, KeeperHub 6/10, Reactive Network 2/10)
What matters most before choosing in this category
Weighted on whether the job survives the vendor: who else can turn the crank, and what end-of-life is published, what can fire the call, against what target, and who can check the condition was true, whether a run that never happened is visible, or the job just goes quiet, and the lateness the vendor will put in writing, and the conditions under which it declines to execute, in that order. THE FAILURE THIS CATEGORY EXISTS TO PREVENT IS INSTRUMENTED BY NOBODY — 0 of 7. Not one vendor documents an alert that fires when a scheduled run does not happen, and the absence was established by exhausting each vendor's own corpus rather than by spot-check. Keep3r: 'notification', 'alert', 'monitor' and 'webhook' return zero hits across all 41 pages indexed at https://docs.keep3r.network/llms.txt.
The #1 overall and the scoring weights
How this category is reviewed
Reviewed on what can fire the call and who can replay the condition, whether the job survives the vendor, whether a run that never happened is visible, and the lateness the vendor will put in writing. Weights are the engine’s: 30 / 28 / 24 / 18. There is deliberately no cost axis — per-execution price is already scored on the sibling page that ranks bundlers and paymasters, so it appears here only as recorded disclosure.