Frequently asked questions
Answers for operators, developers, and web3 apps evaluating Ekko for governed messaging, delivery, and PWA notifications.
What is Ekko?
Ekko is a product suite for governed user messaging and event-grounded notifications for onchain products. Teams use it to identify affected users or operators, route messages through reachable channels, and prove what was sent, suppressed, or missed.
Who is Ekko for?
Ekko is built primarily for protocol teams, wallet platforms, and web3 apps that need to reach users or operators when protocol, wallet, account, or product state changes.
Is Ekko a consumer app or an operator product?
The operator side comes first. Protocol Ops is the primary product, while PWA Notifications and Developer Platform extend delivery and integration when rollout needs them.
What products does Ekko offer?
Ekko currently groups into Protocol Ops, PWA Notifications, Developer Platform, and Marketplace.
What is Protocol Ops?
Protocol Ops is the web product for governed engagement, event-grounded messaging, trigger authoring, routing, governance, and operator controls. It is where teams define who should be reached, what message should exist, which channels are allowed, and what policy or provenance applies.
What is the Developer Platform?
Developer Platform includes APIs, webhooks, integration contracts, and implementation guidance for teams embedding Ekko into their own product or internal systems.
What is PWA Notifications?
PWA Notifications is an Ekko product for existing web3 apps that want governed web push for reachable users without building their own trigger, consent, and delivery stack.
Does Ekko replace my app?
No. Your team keeps the brand and product experience. Ekko handles trigger evaluation, push orchestration, subscription state, provenance, and delivery analytics.
Do I need to build a native iOS or Android app first?
No. PWA Notifications is specifically for teams that already have a web app and want governed push delivery for reachable users.
Can notifications deep-link back into my app?
Yes. The intended model is that delivered notifications send users back into the relevant product context inside the provider app.
How is Ekko priced?
Ekko pricing is structured around Protocol Ops. Free is a limited evaluation path, Pro starts at $499/month, and Enterprise is custom. PWA Notifications and Developer Platform are managed add-ons.
What counts as usage?
Usage can include notifications sent, reachable audience size, active message plans, observed wallets or accounts, and, for PWA Notifications, active push subscribers or delivered push volume.
How much does PWA Notifications cost?
PWA Notifications starts from $1,500/month plus usage. It is positioned as a sales-led add-on because it includes integration work, subscription management, provider identity mapping, and user-facing web push delivery.
Is PWA Notifications included in the base plan?
No. PWA Notifications is positioned as a separate add-on or sales-led package because it includes integration work, subscription management, and user-facing delivery infrastructure.
Do you provide APIs and webhooks?
Yes. Ekko supports API and webhook integration for teams that want to embed message plans, trigger logic, delivery outcomes, and audience context into their own systems.
Can I evaluate Ekko before a full rollout?
Yes. The intended path is to review docs, validate the API and payload model, and test the integration path before broader production rollout.
Can I integrate Ekko with an existing wallet or account model?
Yes. The intended model supports mapping provider users to wallets, accounts, and cohorts so messages and delivery can be scoped correctly.
How does Ekko handle permissions and approvals?
Ekko is designed around role-based workspace controls plus scope-based policy and approval rules, especially for user-affecting or higher-sensitivity workflows.
Can my team pause or stop delivery quickly?
Yes. The operational model includes pause, revoke, and kill-switch style controls so teams can stop unsafe or incorrect delivery fast.
Can users understand why they received a notification?
That is the goal. Ekko is designed to preserve provenance so teams and users can understand what triggered delivery and which workspace or plan caused it.
Still evaluating fit?
Talk to the team if you want help mapping Ekko to your product, delivery workflow, or PWA rollout path.