Integrations
Edverix connects to what you already pay for and takes no margin on delivery. Messages go out through your own accounts; data syncs to storage you own.
Delivery
A provider is a setting, not an architecture. Connect two providers of the same channel, route between them by segment or message type, and fail over automatically when one degrades.
Edverix meters events processed and messages orchestrated. Delivery is billed by your provider at the rate you negotiated.
Service-account keys and API tokens are encrypted per project. A provider is added, rotated or removed from the dashboard.
Bounces, complaints, quality ratings and delivery receipts flow back through webhooks and land on the profile as events.
Catalog
The products the platform connects to, grouped by what they carry. Names are the third-party products themselves and imply no partnership.
Bring your own Firebase project and APNs key. Tokens live in your project; probes and sends go through your credentials.
How it connects: Service-account credentials encrypted per project; silent probes for uninstall detection.
Any SMTP or API-based email service. Bounces, complaints and unsubscribes flow back as events.
How it connects: Provider adapter with webhooks for delivery events; failover between two providers.
Your negotiated rate, your sender ids, with Indian DLT and TRAI requirements handled per sender.
How it connects: Template registration synced per gateway; sends refused if no approved template matches.
Meta Cloud API directly, or any business solution provider with a template and messaging API.
How it connects: Template sync with approval state, quality-rating alerts, interactive flows.
Rich messaging where SMS used to be, and the chat apps your market lives in.
How it connects: Channel adapters with rich-card templates and delivery events.
Direct sync without an intermediate bucket, or scheduled files to your own storage.
How it connects: Incremental sync of events and profiles as tables; JSON, CSV or Parquet to buckets.
Already sending events somewhere? Add Edverix as a destination and skip instrumentation.
How it connects: Destination connectors that map identify and track calls onto the Edverix schema.
Install source lands on the profile automatically and becomes a split dimension in every report.
How it connects: Postback ingestion mapped to profile attributes.
Sync any segment to paid channels so owned and paid target the same definition.
How it connects: Hashed audience upload, one-off or on a recurring schedule.
Orders, refunds, tickets and deals feeding the same profile as your app.
How it connects: Webhook receivers and server-API mappings.
Threshold alerts, anomaly reports and approvals where your team already works.
How it connects: Outbound notifications and approval actions.
Bring your own model keys, and let your team's assistant drive the platform through MCP.
How it connects: Configurable model gateway; MCP server with permission mirroring.
Request
Most providers with a messaging or webhook API connect through the generic adapter today. Tell us which one you use and an engineer replies with the mechanism and the setup steps.
Get started
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.