Run it inside your own walls, with push content that stays on your own infrastructure.
When your policies require dedicated or in-country deployment, evaluate xNotify against your data-location, isolation and third-party-processing requirements. The options below are the ones the platform offers.
“The engagement platform you want is a shared cloud somewhere else. Push means giving the message to a device-maker network. The regulator asks what happens when a data centre goes dark.”
What you do on xNotify.
Choose where it runs.
DEPLOYMENTA shared service, a dedicated instance, or an on-premise, in-country installation, on the same platform.
Keep operational data in its own database.
DEPLOYMENTContact, consent and delivery records live in a database per customer; a query on the wrong connection returns nothing. Behavioural events sit in a shared analytics store, partitioned by customer with a mandatory tenant filter on every query.
Detail: physical separation for operational data; logical isolation for analytics.
Keep push content off third-party networks.
PUSHContent over our own connection, a content-free wake-up to the device makers, device-targeted encryption stated exactly, not end-to-end.
Have a real answer on resilience.
DEPLOYMENTHigh-availability pairs across the estate and a separate disaster-recovery site on dedicated deployments.
An evaluation plan, not a journey.
Steps for your team and ours. Nothing here runs in the journey builder.
- 01A dedicated or in-country deployment sized against your real traffic
- 02One journey live
- 03A security review against the white paper
This page describes platform controls; it is not a security attestation. Request the security white paper.