Data residency (EU / Turkey regions)
Pushizo runs each data region as a separate cell: the EU (Frankfurt) and Turkey (Istanbul) cells each have their own database, queue, analytics store and file storage. An organization's subscription,…
Pushizo runs each data region as a separate cell: the EU (Frankfurt) and Turkey (Istanbul) cells each have their
own database, queue, analytics store and file storage. An organization's subscription, user, event,
message and file data is processed and stored only in the region it selected (KVKK, the Turkish data protection law / GDPR). Decisions:
docs/adr/0032-hucre-mimarisi-white-label-bayi.md.
Choosing a region when creating an organization
In the dashboard, choose the Data region in the New organization form. The region cannot be changed from the dashboard later; migration is a verified operation performed by the support team (see below).
With the API (session-authenticated dashboard API):
GET /internal/v1/cells
→ { "enabled": true, "current_cell_id": "eu", "control_plane": true,
"cells": [{ "id": "eu", "name": "Europe (Frankfurt)", "api_url": "https://api.eu…", "dashboard_url": "https://app.eu…" }, …] }
POST /internal/v1/orgs
{ "name": "Acme", "region": "tr" }
→ 201 { "id": "org_…", "region": "tr", … }Single-region installations return enabled: false, and region is not provided.
Switching between regions (dashboard)
Your account is the same in every region. GET /internal/v1/cells/orgs lists your organizations across all regions; when you switch to an
organization in another region, the dashboard gets a single-use session handoff link valid for 60 seconds via POST /internal/v1/cells/handoff
and redirects you to that region's dashboard (/handoff). If you use the wrong region's login with an account registered
in another region, the login responds with 421 HS_WRONG_CELL and the correct dashboard address.
SDKs and the server API: regional address
Each region has its own API address (e.g. https://api.eu.pushizo.com, https://api.tr.pushizo.com).
- The Web, Android and iOS SDKs learn the regional address from the app configuration (
GET /sdk/v1/apps/:appId/config→api_url,cell_id) and use it for subsequent requests. If you passed your own domain/proxy server withapiUrlduringinit, that address is kept. - Every request sent to the wrong region returns
421 HS_WRONG_CELLwithout being processed;error.detailscontainscell_id,api_urlanddashboard_url. Data is never written to the wrong region. - Server SDKs and the REST API: configure the client with your org's regional address:
import { Pushizo } from '@pushizo/node';
const hs = new Pushizo({ apiKey: process.env.PUSHIZO_API_KEY!, baseUrl: 'https://api.tr.pushizo.com' });If you get a 421 response, write details.api_url into your configuration permanently.
Region migration
Migration is performed by the support team during a maintenance window: the organization becomes read-only (suspended) for a short time, all database records, analytics data and files (logo, exports) are copied to the target region and verified with row counts and checksums; if verification fails, nothing changes. The copy in the source region is deleted in a separate step after the target has been verified. After migration:
- SDKs switch to the new region's address via the 421 response; update the
baseUrlof your server integrations. - If you use a custom domain, update the CNAME record to the new region's target (see White-label).
- Temporary counters (such as rate limit windows) are reset.
Operational steps: docs/runbooks/cells.md.
FAQ
- Which data stays in the region? Organizations, apps, subscribers, users, events, messages, deliveries, templates, campaigns, audit logs, files and analytics. Only the account identity (email, name) and the organization → region mapping (name, short name) are shared across regions.
- How is cross-region traffic protected? Cells only access each other's APIs, with requests signed with a shared secret, timestamped and single-use; they have no network access to each other's data layer.
KVKK and GDPR compliance
Roles (data controller/processor), account owner rights (data download, account deletion, marketing consent), end-user rights, sign-up consent and terms version, retention, subprocessors, DPA and data residency.
Enterprise SSO (SAML 2.0 / OpenID Connect)
Connect sign-in to the Pushizo dashboard to your identity provider (Okta, Microsoft Entra ID, Google Workspace, Keycloak, OneLogin…). SSO is on the Enterprise plan. Decisions: ADR-0023.