Frequently asked questions
Answers for operators, developers, and web3 apps evaluating Ekko for governed messaging, WalletAlert, and delivery.
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. WalletAlert is the user-facing engagement module inside Protocol Ops, while Developer Platform extends integration when rollout needs it.
What products does Ekko offer?
Ekko currently groups into Protocol Ops, Developer Platform, and Marketplace. WalletAlert is the named Protocol Ops engagement module for provider-app notifications, contact capture, offline delivery, and alert subscriptions.
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 WalletAlert?
WalletAlert is a wallet-adjacent notification surface for existing web3 apps. It sits beside Connect Wallet so users can receive wallet-scoped updates, opt into offline channels, and subscribe to relevant alerts.
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. WalletAlert is for teams that already have a web app and want a notification-capable user experience before building a separate mobile product. PWA push is optional and depends on user opt-in and browser support.
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. WalletAlert is included as the named Protocol Ops engagement module.
What counts as usage?
Usage can include notifications sent, reachable audience size, active message plans, observed wallets or accounts, active WalletAlert sessions, active push subscribers, or delivered push volume.
Is WalletAlert included in Protocol Ops?
Yes. WalletAlert is the named engagement module inside Protocol Ops. High-volume usage, push subscriber scale, managed onboarding, or custom provider integration can affect usage pricing or rollout scope.
Is PWA push a separate product?
No. PWA push is an optional WalletAlert delivery channel for users who opt in and have a supported browser/device state.
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 WalletAlert to your product, delivery workflow, or rollout path.