Import history
Bring a CSV export, a warehouse import or a CDP connector into Edverix. Every upload is validated against the schema on the way in, so history arrives clean.
Compare
Where legacy engagement platforms stop, and Edverix starts.
Three structural differences: what you pay for, who owns the data, and whether you can see a campaign's result before you send it. Everything else on this page follows from those.
The short version
Five things to remember.
One event store, so analytics and messaging are the same system.
The number in a funnel and the number in a campaign are the same number, and any report becomes an audience in one click.
Your data stays queryable, exportable and yours.
Events live in Postgres. Query them in SQL, sync them to your warehouse, export everything on demand, or run the whole platform in your own cloud.
We never resell you a message.
Bring your own push, email, SMS and WhatsApp providers and keep the rates you negotiated. Edverix takes no margin on delivery.
See exactly who gets a campaign before you send it.
Simulation replays thirty days of real events through the draft and returns the people, the messages and the timing. Not an estimate, a list.
Priced on what you use, published on the website.
Events processed and messages orchestrated are the only meters. Profiles, seats, journeys and AI are not.
Matrix
Capability by capability.
Sender-of-record platforms run their own delivery infrastructure and bill for it. Orchestrator platforms let you bring providers but keep your data behind their query language. Edverix does neither.
| Capability | Sender-of-record platformsRun delivery themselves and bill for it | Orchestrator platformsYou bring providers; data stays behind their query language | EdverixOne event store, your providers, real SQL |
|---|---|---|---|
| Pricing | |||
| Pricing basis | MAU + message volume | MAU + message volume | Events processed + messages orchestrated |
| Margin on delivery | Yes, per message | No | No |
| Data | |||
| Raw-event SQL access | JSON query language | None | Real SQL |
| Warehouse sync | Via bucket export | None or third party | Direct |
| Full export on demand | Limited | Limited | Yes, no notice period |
| Profile timeline lookback cap | Varies | Limited | None |
| Delivery | |||
| Bring-your-own provider | Partial | Yes | Yes |
| Switch providers by config | No | Partial | Yes |
| Per-message delivery log with reason | Partial | Partial | Yes |
| Blast-radius ceiling | No | No | Yes |
| Journeys | |||
| Simulation before send | Audience estimate | Audience estimate | 30-day replay |
| Journeys as code | No | No | Yes |
| Funnel to audience in one click | Partial | Yes | Yes |
| Universal holdout | Yes | Yes | Yes |
| Governance | |||
| Schema enforced in CI | No | No | Yes |
| Undo a bad identity merge | Rare | No | Yes |
| AI | |||
| AI metered separately | Typically | Typically | No |
| MCP server with permission mirroring | Partial | No | Yes |
| Platform | |||
| Self-hosting | No | No | Yes |
| KYC-backed onboarding | No | No | Yes |
Sender-of-record and orchestrator describe categories, not specific vendors. Check any row against the platform you are evaluating; the Edverix column is described in full on the module pages.
Migration path
Six steps from a legacy platform to Edverix.
Nothing here needs a big-bang cut-over. Teams run both platforms in parallel and move one channel at a time.
Step 01 Step 02 Run both in parallel
Add Edverix as a destination alongside the platform you have. Events flow to both, and the catalog and profiles build up before anything is sent.
Step 03 Port templates and segments
Templates use a Liquid-compatible syntax, so most move with light edits. Segments rebuild in the condition builder, or as SQL when the form is not enough.
Step 04 Simulate journeys against 30 days
Rebuild each journey on the canvas and replay the last thirty days of real events through it. The output names who would have entered, what they would have received and where a cap would have stopped a send.
Step 05 Cut over channel by channel
Connect a provider, point one channel at Edverix and watch the delivery log. Move the next channel when the first one is clean.
Step 06 Export or archive the old platform's data
Take a final export from the old platform and load it as history, or archive it to your own bucket. Edverix keeps the full timeline with no lookback cap.
FAQ
Questions about migrating
The questions that come up in the first call, answered the way we answer them on the call.
We are still under contract with our current platform. Does it make sense to start now?
Yes. Running Edverix in parallel costs only the events you send it, and the Developer plan is free for small volumes. Teams use the overlap to import history, rebuild segments and simulate journeys, so the cut-over happens the week the old contract ends rather than the quarter after.
Will our existing templates work?
Edverix templates use a Liquid-compatible syntax with filters, conditionals and loops, so templates written in a Liquid-style language move with light edits. Every token declares a fallback, and the QA pass flags any token that lacks one before the first send.
Can we backfill historical users and events with their original identities?
Yes. Bulk import and warehouse import accept your user ids, anonymous ids and original timestamps, and the identity stitching that runs on live traffic runs on the import too. If a merge turns out to be wrong, it can be undone with both histories intact.
What does running both platforms in parallel cost?
On Edverix, the events you send during the overlap and the messages you orchestrate, at the published per-unit rates. Channels you have not moved yet cost nothing on Edverix, and delivery is billed by your own providers at your own rates either way.
In what format can we export our data from Edverix later?
Events and profiles export on demand through the REST API, to S3, Google Cloud Storage or Azure in JSON, CSV or Parquet, or directly to BigQuery, Snowflake, Redshift or Databricks. The schema is documented and there is no notice period.
Get started
Run the comparison on your own 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