Current deployment
Early access currently operates from a single primary analytics region. The region-coded CDN and ingest architecture is already separated from the customer dashboard hostname, allowing new geographic collectors and storage planes to be added without changing the product model.
We disclose the available placement during onboarding. We do not market a future region as available before its collection, storage, backup and operational controls are actually ready.
What regional placement covers
A regional placement can cover customer web-event data, normalized server-log analytics, derived aggregate tables, site configuration and search/GEO analytics stored by Abnio for that service region. Exact scope, backup placement and subprocesses are documented in the customer agreement.
Regardless of region, Abnio does not store raw visitor IP addresses in analytics databases. The Web beacon also does not retain raw User-Agent strings. Optional server-log analytics retains User-Agent strings for crawler classification and investigation.
What may be processed elsewhere
Some limited data may be handled by providers outside the analytics region when required to operate a feature. Examples include transactional email delivery metadata, DNS/CDN security processing, support correspondence, and requests to external search or answer-engine APIs initiated for integrations. Google Search Console and monitored answer engines process requests under their own infrastructure and terms.
Backups, disaster recovery arrangements and operational access are governed by safeguards appropriate to the service and applicable customer terms. Contact us before onboarding if you have a strict in-country requirement that extends to every subprocess or support operation.
Global region roadmap
Additional ingest and storage regions will be added as customer demand grows. The intended model is region-aware collection, explicit customer placement and controlled migration—not silent replication into an undefined global pool.
A clear initial production location with documented providers and boundaries.
Deploy region-coded collection endpoints close to major customer geographies.
Offer explicit placement and migration as each full regional data plane becomes operational.
Your configuration matters
A customer may proxy the Abnio beacon through its own first-party origin, enable external integrations, or provide logs from infrastructure in another country. Those choices affect the full data path. We help customers document the actual architecture instead of relying on the location of a single server.
Residency questions
For architecture reviews, subprocess details or customer-specific residency requirements, contact: