Skip to content
Current public resources

Find the fastest path into Ekko

Review the hosted app, public docs, API paths, delivery controls, and proof model before widening coverage.

Start freeExplore developer pathsTalk to sales
Evidence by default Privacy by design Developer first

Getting started in 4 steps

1

Connect

Link wallets and data sources.

2

Define audience

Build audiences.

3

Create message

Apply policy.

4

Send & prove

Capture proof.

Activity preview

12:04:18Trigger detectedCurrent
12:04:19Audience resolvedCurrent
12:04:20Message approvedCurrent
12:04:21DeliveredCurrent
12:04:22Receipt recordedProof ID

Delivery receipt

Completed
Event
Airdrop claim window opened
Audience
128,342 users
Channels
PWA Notifications, email, SMS, Telegram
Proof
View full receipt
Proof

Delivery proof model

Use trigger, affected cohort, expected notification, counterfactual action, and impact to reason about missed moments.

Overview
Core concepts
Operational guide
Next steps
Evaluation

API and webhook evaluation

Review current integration paths and payload expectations before a broader rollout.

Overview
Core concepts
Operational guide
Next steps
Integration

PWA Bridge Integration

Understand how governed web push fits into an existing web3 app.

Overview
Core concepts
Operational guide
Next steps
Support

Support and rollout help

Contact the team when your Protocol Ops workflow needs onboarding or integration planning.

Overview
Core concepts
Operational guide
Next steps

Only current, public paths

Everything here reflects what is available today. No private modules. No placeholder docs.

View API reference
Resource

Delivery proof model

Understand how Ekko frames trigger, affected cohort, expected notification, counterfactual action, and impact.

Resource

Current public resources

Use the hosted app, support path, and public integration guidance available now.