MenuClose
Off Gelato, Chainlink Automation and Defender
Gelato Web3 Functions and Chainlink Automation stopped this year, and so did OpenZeppelin Defender, whose steps now have a page of their own, the Defender migration guide. Below are the end dates and what changes when a scheduled job moves to a caller you run.
End dates
| Service | Stopped | Source |
|---|---|---|
| OpenZeppelin Defender | Sign-ups closed 2025-06-30; retired 2026-07-01 | OpenZeppelin, 2025-06-30 |
| Defender docs and migration guide | Removed 2026-10-02 | #243; last version of the guide |
| Gelato Web3 Functions and Automate | 2026-03-31 | Gelato's in-app notice, quoted by Mimic and KeeperHub; Gelato's own pages for it now return 404 |
| Gelato relaying in Safe's Relay Kit | 2026-09-01 | Safe docs |
| Chainlink Automation | v1.x 2026-06-30; v2.1 2026-07-31 (testnet 2026-06-24) | Chainlink docs |
| Blocknative APIs (gas estimates, mempool data, transaction notifications) and Gas Network | 2026-06-19 | Blocknative's notice; its team joined Deloitte |
OpenZeppelin Defender
Relayer and Monitor configurations exported before July go into the open-source programs' config folders; relayer keys could not be exported, so every relayer gets a new address; Actions have no successor. The Defender migration guide has the steps, the SDK call table and what to change before the funds move.
Gelato Web3 Functions and Chainlink Automation
A Gelato task called your contract from Gelato's dedicated msg.sender proxy, so a contract that allowlisted that address has to authorize the new caller. Resolver functions (a checker() returning canExec and the call data) keep working as they are, since only the caller changes. Web3 Function code (onRun) needs a new runtime.
Chainlink's replacement is CRE. Deploying a CRE workflow needs Early Access approval, and there is no public price (deploy access). Contracts that check msg.sender or an Automation forwarder have to authorize whatever calls them next.
Plan for the job stopping without an error. On 2026-08-20 Sommelier reported that the last UpkeepPerformed on the v2.1 registry had been on 2026-08-05, that its upkeep was still funded, unpaused and returning true from checkUpkeep, and that 19 of its vaults could not process withdrawals (cellar-contracts #197). An alert on "no successful run in N intervals" catches that on the first missed interval, which a failure alert does not.
Moving with us
Nonceworks is setting up hosted Monitor and Relayer for small teams, with the signing key in your own KMS or Turnkey account. Moving a Defender stack is $400 and replacing a raw key on a server is $300, both fixed; the pricing page lists what each includes.
Hosting after either move is $49 a month, first month free. AWS KMS signing has been tested end to end against a real AWS key; Google Cloud KMS and Turnkey have not, so before a move we run your key end to end on a testnet.
Running your own Defender export through the validator costs nothing. Scheduled and conditional jobs, such as an upkeep, a Gelato function or a Defender Action on a timer, are being built now. If you have one that stopped, write and we will tell you when it can move.