Architecture and deployment regions
Each customer runs on a dedicated instance: a console, an isolated database and a managed Infobip account provisioned for that customer alone. There is no shared application database and no shared messaging account.
The layers
- Console — the operator interface: inbox, CDP, automations, reporting, settings.
- Data layer — contacts, conversations, media and consent records, stored in your chosen region.
- Messaging back-end — a managed Infobip account holding your channel registrations, senders and numbers.
- Integration layer — CRM, helpdesk and data connectors, plus webhooks out to your systems.
What the region determines
Your region sets where message content, contact records and media are stored at rest. Carrier and platform delivery paths are inherently global: a message to an Australian mobile transits Australian infrastructure regardless of where your instance sits.
| Region | Storage location | Typical use |
|---|---|---|
| EU | Ireland / Germany | EU-headquartered and GDPR-first organisations |
| North America | United States | US and Canadian operations |
| APAC | Singapore / Australia | Asia-Pacific operations |
One MSA, one DPA and one support team cover every region.
Next step
Bring this to your enterprise stack
See how a dedicated Arino One instance — deployed in your region (EU, NA or APAC) — would sit inside your operation. Architecture, DPA, and rollout plan walked through live.