Skip to content
Live signal routing

Turn onchain moments into timely user messages

Identify affected users, route event-grounded messages through reachable channels, and prove what was sent, suppressed, or missed.

Ekko embedded notification demo showing a connected wallet and a critical bridge delay notification
Product demo screenshot showing Ekko notifications mounted beside a connected wallet control.

Workflow

From onchain signal to delivery proof

Ekko turns missed onchain moments into governed user and operator messages with auditable delivery outcomes.

1

Missed moment

Detect what matters

2

Affected cohort

Resolve who is affected

3

Expected notification

Control what gets sent

4

Delivery proof

Prove what happened

Governed by design. Proven by default.

Roles, approvals, policies, and audit trails are built in so your team can move fast with confidence and prove every outcome.

Learn about governance
Trust & access

Operate with confidence and public evidence

Protocol teams use the hosted app, public docs, API paths, and proof model to validate delivery controls before widening coverage.

Passkey-ready access

Secure, passwordless sign-in for your team and partners.

Delivery receipts

See what was sent, delivered, bounced, or suppressed.

Suppression history

Understand who was suppressed and why.

API and webhook paths

Integrate with your systems and automate operations.

Workspace roles

Granular permissions for safe, team-based operations.

Support-led rollout

Get guidance for workflow design, testing, and launch.

Getting started

Everything you need to evaluate and run a first workflow.

1

Connect

Build your audience, message, and proof path.

2

Define

Build your audience, message, and proof path.

3

Create

Build your audience, message, and proof path.

4

Send & prove

Build your audience, message, and proof path.

Message receipt

Delivered
Message ID
msg_8f3c2d9a
Audience
12,842 users
Channels
Email, push, inbox
Delivered9,65275.1%
Bounced1,1028.6%
Suppressed1,83414.3%
Unreachable2542.0%
Ready to explore the docs? View docs
Operational scale

Start with Protocol Ops. Grow as your workflows mature.

Turn missed moments into governed messages first, then add PWA delivery, APIs, and advanced automation as your team's operational needs scale.

12:04:18Trigger detected
12:04:19Audience resolved
12:04:20Message approved
12:04:21Delivered
12:04:22Receipt recorded

Delivery receipt

Completed
Event
Bridge Pause (Ethereum)
Audience
12,842 users
Outcome
Sent 10,128 · Suppressed 1,254
View full report