Company

We build the engagement platform we wanted to buy.

Edverix is product analytics, customer profiles, segmentation, journeys and every messaging channel on one event store you can query in SQL. We built it because the tools we used kept the data and charged for the delivery.

Request a demo Get started free

Why

Every tool we used had the same shape, and the same gap.

Analytics tools know everything and do nothing. They can show you exactly where a checkout stalls, and the insight stops at the chart. Turning it into a message means exporting a list into a second product that has never seen the event.

Messaging tools do everything and know nothing. They will send a push, an email and a WhatsApp template in one campaign, to an audience defined by whatever attributes were synced last night. The conversion they report is not the conversion the analytics team reports.

Sender-of-record platforms mark up delivery. Every message travels through their provider accounts at their rates, so the bill grows with your volume and the delivery log belongs to them. And none of them lets you simulate a journey against real history before it touches a customer.

One event store, your own providers, and a dry run before every send. That is the whole thesis.

Principles

Five rules the platform is built around.

Each one is a product decision you can check, not a value statement.

One event store

The report and the campaign read the same rows. A funnel drop-off becomes a segment in one click, and the conversion a journey reports is the conversion the dashboard reports, because there is only one definition of it.

Product Analytics

Your data is yours

Events and profiles live in Postgres under your project. Query them in SQL, sync them to your warehouse, export everything with no notice period, or run the whole platform inside your own cloud account.

Data Platform & Warehouse

No margin on delivery

You connect your own push, email, SMS and WhatsApp providers and keep the rates you negotiated. Edverix orchestrates, personalises, governs and logs every send. It meters the orchestration, not the delivery.

Messaging Channels

Simulate before you send

Every journey can be replayed against real event history before it is activated. You see who would have entered, which branch they would have taken and how many messages would have gone out, before anyone is messaged.

Journey Orchestration

Propose, then wait

The assistant drafts copy, builds segments and proposes journey changes as a diff. Nothing applies until a person with permission approves it, and the approval is written to the audit log.

AI & Predictive

How we work

A small team that ships the platform and answers the tickets.

Engineering-led

The people who design the platform talk to the people who run it. Product decisions come from support threads and SQL, not from a roadmap deck.

Ship weekly

Small releases every week, behind flags wherever a change touches delivery. Nothing waits for a quarterly launch.

Public changelog

Every release is written up with what changed and why, including the releases that fix our own mistakes.

Support by the people who wrote it

Tickets go to the engineers who own the module. There is no script between you and an answer.

Where

Built in India, deployed in your region or your own cloud.

Engineering is based in India. Your project's data lives in the region you choose at onboarding, and regulated customers can run the whole platform inside their own cloud account with the same feature set.