Data Collection & SDKs
SDKs for web, iOS, Android, React Native, Flutter and server, with offline queues, consent gating and automatic lifecycle events.
21 capabilitiesExplore
Platform
Five layers. One event store. Every channel.
Collect every event once. Understand it on the raw events. Decide who gets what with live segments and journeys. Deliver through your own providers, under your rules. Operate it with AI that proposes and waits, on a platform built for enterprise security.
Architecture
How it fits together
Sources on the left, the event store and its four engines in the middle, channels on the right. Every event takes the same path, so the profile, the report, the segment and the send all read the same record.
Scroll sideways to see the full diagram.
Layer 01 · Collect
Every surface, one event model, one profile per human.
SDKs for web, mobile and server feed a single event store, with schema enforced at the door and identity stitched across devices.
3 modules · 47 capabilities
Customer Profiles & Identity
Anonymous history is stitched onto the known user at login, with computed attributes, reachability and a full event timeline.
15 capabilitiesExplore
Event Catalog & Tracking Plan
Auto-discovered events, inferred property types, top values for pickers, and a tracking plan you can enforce in CI.
11 capabilitiesExplore
Layer 02 · Understand
Funnels, retention, paths and revenue on the raw events.
The full report suite runs directly on the event store, so the number in a report and the number in a campaign are the same number.
2 modules · 30 capabilities
Layer 03 · Decide
Segments and journeys that say who gets what, and when.
Continuously evaluated audiences, a visual journey canvas, and experiments with real control groups.
3 modules · 40 capabilities
Segmentation & Audiences
Behavioural, demographic and technographic conditions, nested any way, evaluated live, with reachable counts before you launch.
13 capabilitiesExplore
Journey Orchestration
Triggers, waits, branches, goals and channel actions on a visual canvas, with per-node stats, versioning and a 30-day replay.
16 capabilitiesExplore
Experimentation & Attribution
A/B and multivariate tests, bandits, control groups, a universal holdout, attribution windows and feature flags.
11 capabilitiesExplore
Layer 04 · Deliver
Every channel, through your own providers, under your rules.
Push, in-app, email, SMS, WhatsApp, RCS, web and webhooks, personalised at send time and governed by caps, quiet hours and a blast-radius ceiling.
3 modules · 46 capabilities
Messaging Channels
Mobile push, web push, in-app, inbox, email, SMS, WhatsApp, RCS, on-site and webhooks, with no margin on delivery.
21 capabilitiesExplore
Content, Personalisation & Catalog
Versioned templates, tokens with fallbacks, reusable blocks, catalog-driven recommendations and prices resolved live.
13 capabilitiesExplore
Delivery Governance
Frequency caps, quiet hours, suppression, send-rate throttling, a blast-radius ceiling and a delivery log that explains every miss.
12 capabilitiesExplore
Layer 05 · Operate
AI that proposes and waits. Security that closes the deal.
Assistants that draft, simulate and diff before a human approves, on a platform built for enterprise access control, residency and audit.
2 modules · 25 capabilities
AI & Predictive
Copy, segments, reports and journeys from plain language, predictive scores with explanations, and an assistant that never acts without approval.
13 capabilitiesExplore
Security, Compliance & Platform
Multi-tenant isolation, roles that match your org chart, SSO and SCIM, PII masking, encryption with your keys, residency and audit.
12 capabilitiesExplore
Only on Edverix
What no legacy engagement platform does, or does well.
42 capabilities across the platform carry this mark. Each one is described in full on its module page.
Data Collection & SDKsOnly on Edverix
- Live integration debuggerWatch raw payloads and validation results arrive while you are still wiring the SDK.
- Ingestion error streamRejected payloads by count, type, source and time, so a broken release surfaces in hours, not at quarter close.
Customer Profiles & IdentityOnly on Edverix
- Undo a bad mergeIdentity bugs are inevitable; ours are reversible. Demerge a profile and both histories come back intact.
- Every computed number shows its workingClick any derived attribute to see the events it was calculated from.
Event Catalog & Tracking PlanOnly on Edverix
- Top values for pickersThe most frequent value of every property, ordered by frequency, so segment and funnel filters suggest real values.
- Contract enforced in CIDefine the plan once; pull requests that change instrumentation show the schema diff and fail on violations.
- Typed code generationTypeScript, Swift and Kotlin types generated from the plan, so a misspelled property is a compile error.
Product AnalyticsOnly on Edverix
- Funnel to audience in one clickEveryone who dropped off at step three becomes a live, refreshing segment you can message immediately.
- Anomaly detection that explains itselfNot just that checkout starts fell, but that they fell only on Android 14, only since the 3.2 release.
Data Platform & WarehouseOnly on Edverix
- SQL consoleReal SQL over raw events and profiles, with saved queries, sharing and a query history.
- SQL-defined segmentsAn analyst's query becomes a campaign audience directly, with no export or CSV handoff.
- Ask in plain languageA question in, the answer and the SQL it ran out, so you can verify it.
- Take everything with youFull export in a documented schema, on demand, with no notice period and no support ticket.
- Self-hosted deploymentRun the whole platform in your own cloud for regulated workloads.
Segmentation & AudiencesOnly on Edverix
- SQL-defined segmentsWrite the audience as a query when the form is not enough.
- Change historyWho changed a definition and when, so when a number moves you know whether the world changed or the filter did.
Journey OrchestrationOnly on Edverix
- LLM stepPass customer and event context to a model mid-flow and use its output to write, classify or choose a branch.
- Simulate against thirty days of historySee exactly who would have entered, what they would have received and how often, before activating.
- Run history with explainabilityEvery run snapshots the evaluated state, so it stays explainable after the journey is edited.
- Journeys as codeDefine a journey in your repository, review it in a pull request, validate in CI, promote from staging and roll back like any deploy.
Experimentation & AttributionOnly on Edverix
- Cost per conversion by channelBecause you bring your own providers, every send has a cost, and the only number that matters is what a conversion cost.
- Flag state on every eventSegment any funnel, retention grid or revenue report by which variant a person was in.
Messaging ChannelsOnly on Edverix
- Digests instead of spam"Three people commented" rather than three pushes, with a collection window you control.
- Drop-in inbox componentsPre-built React components for feeds, toasts and banners, so a product team ships a notification centre in a day.
- Bring your own providerFirebase, APNs, any email service, any SMS gateway, any WhatsApp business provider. We take no margin on delivery.
- Switch providers in an afternoonA provider is a setting, not an architecture. Moving vendors is a config change, not a migration.
Content, Personalisation & CatalogOnly on Edverix
- Fallbacks that actually workEvery token declares its fallback, and any token without one is flagged before the send.
- Automated QA before every sendTokens resolve, SMS length and cost are sane, the unsubscribe link is present, the template matches what the regulator approved.
- Recommendations that respect marginRank by contribution, not just by likelihood to click.
Delivery GovernanceOnly on Edverix
- Blast-radius ceilingA maximum send volume for the organisation. Anything projected to exceed it refuses to activate; a running campaign that breaches it halts itself.
- Organisation-level notification policyA workspace admin sets rules for their whole team, overriding individual preferences. Essential for B2B products.
- Simulation before activationReplay any campaign over thirty days of real events: who would have received it, how many times, and where a cap would have stopped it.
- Per-message delivery logEvery attempted send with its outcome and reason: suppressed, capped, outside quiet hours, token expired, provider rejected.
- Delivery forensics in plain languageAsk why a specific person did not receive a specific message and get an answer, not a ticket.
AI & PredictiveOnly on Edverix
- Ask your data a questionThe answer and the SQL it ran, so you can verify it.
- Explanations, not scoresNot "churn risk 0.81" but "these customers all hit the same payment error before they left."
- Propose, simulate, diff, approveGenerate and simulate in one motion; nothing applies until a person with permission says so.
- LLM step inside a journeyUse a model mid-flow to write, classify or route.
- MCP serverYour team's own assistant can pull analytics, build segments and check campaigns, with exactly that person's permissions.
- Analytics for the agents you buildMulti-step task funnels with retries, escalations and tool failures as first-class events.
- Not metered separatelyAI is part of the product, not a credit pack.
Security, Compliance & PlatformOnly on Edverix
- KYC-backed onboardingOrganisations are verified before activation, with jurisdiction-specific document requirements.
13
Modules
across five layers
188
Capabilities
each described on its module page
8-step
Funnels
four events per step, any property filter
30-day
Journey simulation
replayed on real events before activation
Explore by role
Start from the work you do.
Each role touches a different part of the platform first. The links go to the three modules that matter most on day one.
Marketing
Build an audience from behaviour, put it on the journey canvas and simulate the result before anyone is messaged. Caps, quiet hours and the blast-radius ceiling apply to every send without a second thought.
Product
Funnels, retention and paths run on the raw events, so a drop-off at step three becomes a live audience in one click. In-app messages and feature flags ship without an app-store release.
Data
Events live in Postgres. Query them in SQL, sync them to your warehouse without a bucket hop, and turn an analyst's query into a campaign audience directly.
Engineering
Typed SDKs for every surface, a tracking plan enforced in CI and journeys that live in your repository. The live debugger shows every payload as it arrives.
Security
Tenant isolation at the schema level, roles that separate building from approving, and an audit log of every administrative action. Residency and self-hosting for regulated workloads.
FAQ
Questions teams ask first
The short answers. Every module page has its own questions underneath.
What is Edverix, in one sentence?
A customer engagement platform, meaning product analytics, customer profiles, segmentation, journey orchestration and every messaging channel, built on one event store that you can query in SQL.
How is that different from a product analytics tool plus a messaging tool?
Their analytics tool knows everything and can do nothing; their messaging tool can do everything and knows nothing. With one event store there is one definition of a conversion, used by both the report and the campaign, and any report becomes an audience in one click.
Do you deliver messages yourselves?
No. You connect your own push, email, SMS and WhatsApp providers and keep the rates you negotiated. Edverix orchestrates, personalises, governs and logs every send but takes no margin on delivery.
Who owns the data?
You do. It lives in Postgres, you can query it in SQL, sync it to your warehouse, export everything on demand with no notice period, or run the platform in your own cloud.
How long does implementation take?
A web or React app sends its first event within an hour. A mobile app with push adds a native SDK and a provider credential. Most teams have their first journey live inside the first week, and the simulation feature means it can be tested against real history before anyone is messaged.
Is there a free tier?
Yes. The Developer plan is free for small event volumes and includes the full analytics suite so a team can evaluate on real data. Paid plans are priced on events processed and messages orchestrated, never on how many people exist in your database.
Get started
One event store. Every channel. Your data.
Send your first event in an hour, simulate your first journey against real history, and keep every byte of it in a database you can query.
- No credit card for the Developer plan
- Bring your own providers
- Export everything, any time