Defender ends July 1.
We built where the monitoring goes next.
Drop your serverless.yml or defender-sdk JSON export and we will rebuild your sentinels in sixty seconds. Every chain you monitored on Defender, every notification channel, every alert threshold. The migration window is open from now to July 1, with the first month of GhostLabs Sentinel free for every contract you bring across.
Paste or drop your Defender export.
YAML or JSON · Max 2 MBFree first month. Concierge for treasuries.
- Free first month of GhostLabs Sentinel for every contract you bring across before July 1.
- $129 per contract per month after that. No tier games. Volume discount at ten plus contracts.
- Concierge migration if you run more than ten sentinels: we run the import, hand you the proof-of-migration report, and you sign once.
- Audited methodology. Every alert is backed by a public rubric you can read at /methodology.html.
Here is what we will rebuild.
Every sentinel from your Defender export, normalised to a GhostLabs MonitoredContract. Auto-mappable rows migrate self-serve. Needs-review rows go through concierge. Unsupported rows are testnet or deprecated chains we do not run in production.
Migrate your auto-mappable sentinels.
If every row in your diff is green, you can migrate without us. The first month is on us; from month two we bill $129 per contract per month. Cancel anytime via the magic link we email you.
Ten or more sentinels? We run it.
For multi-chain treasuries, multi-contract protocols, and Slack/webhook channels that need adapter work, our team runs the migration end-to-end and hands you a signed proof-of-migration report.
Three moves. No vendor lock-in.
The whole flow is designed so a single engineer at your team can complete it in an afternoon, and a CTO can forward the result as a one-page proof of migration.
Run sls pull from defender-as-code.
The OpenZeppelin defender-as-code plugin emits a serverless.yml with every sentinel, alert condition, and notification channel reference. Or use defender-sdk’s client.monitor.list() for JSON. Either format pastes here.
Every sentinel rebuilt, side by side.
We map Defender networks to GhostLabs chains, addresses to MonitoredContract rows, notification channels to Sentinel adapters. Auto-mappable rows turn green; channels we cannot auto-route surface as warnings so nothing migrates silently.
You decide the friction.
Self-serve is one Stripe checkout with the free-month coupon applied. Concierge is a fifteen-minute call where we run the migration on your behalf and hand you a signed report. Either path activates Sentinel before Defender shuts off.
The questions that come up most.
Will my Slack channels migrate?
Slack is not first-class on Sentinel v1. We auto-route Slack alerts to email by default. Concierge migration includes a Slack incoming-webhook adapter at no extra cost. Discord and Telegram migrate natively.
What about Defender Autotasks?
Autotasks are out of scope for v1 because their behaviour is open-ended JavaScript, not a monitoring contract. If your sentinels trigger autotasks today, document the action they take and we will translate them to native GhostLabs alert webhooks during concierge.
I use Defender Admin or CREATE2 deployment. Does GhostLabs cover that?
No. GhostLabs Sentinel is a monitoring product, not a deploy or admin product. The OpenZeppelin Monitor open-source repo handles the Admin path. If your team needs both monitoring and deployment governance, we recommend GhostLabs for the alert tail and OpenZeppelin Monitor for the deploy path.
What happens to my alert history?
Defender does not export alert history; only current configuration. Your firing log lives in the Defender UI through July 1. Export it manually if you need it for compliance.
How long is the free month valid?
The first month is on us for every contract migrated before July 1, 2026. The promotion stops the moment Defender shuts off. After day 31, the contract bills at the standard $129 per month and you can cancel anytime via the magic-link self-serve flow.
Do you store my serverless.yml?
No. The parser runs in-memory, returns the diff, and the buffer clears. We never persist the export. The MonitoredContract rows we create at checkout contain only the addresses, chain IDs, and channel preferences derived from the diff.