DATA RESIDENCY

Your data, your region.

Tablize runs in 4 regions — San Jose, Tokyo, Hong Kong, Frankfurt. Pick one when you create a workspace. Your database, object storage, and MQTT broker all live in that region. Backups stay in-region too. Cross-region transfers happen only with your explicit configuration.

How to pick a region → Compliance details

Regions to choose from

Region per workspace

Automatic cross-region transfer

100%

Dedicated DB / S3 / MQTT

Available regions

Code

Location

Best for

US sjc

San Jose, USA

Default for North & South America. Low latency for US/Canada teams.

JP nrt

Tokyo, Japan

For customers in Japan and the broader APAC region with APPI requirements.

HK hkg

Hong Kong, China SAR

For Greater China, Southeast Asia, and customers who want APAC residency outside Japan.

DE fra

Frankfurt, Germany

For European Union customers, GDPR data residency, and Schrems II compliance.

Region is fixed at workspace creation. To change region you must create a new workspace and migrate.

How to pick your region

Five steps, about two minutes. A screenshot-rich walkthrough lives in the quickstart guide.

Sign in to console

Open console.tablize.com and sign up or log in.

Click "New Workspace"

The top-right New Workspace button opens the creation modal.

Choose your region

The Region dropdown lists all 4 regions: sjc (San Jose), nrt (Tokyo), hkg (Hong Kong), fra (Frankfurt). Pick the one that matches your residency requirement.

⚠️ Region is immutable after creation. If you pick the wrong one, you have to create a new workspace.

Set slug + display name, then Create

Slug is the URL identifier (lowercase alphanumeric + hyphens, 3–32 chars). Display name is the human-readable label. Click Create — a dedicated PostgreSQL, S3, and MQTT broker spin up in your chosen region within about 60 seconds.

Verify the location

Settings → Workspace shows the region code. If it reads, say, fra (Frankfurt, Germany), every data plane component lives in that region. Backups stay in-region too.

⚠️ Tip

Region is per-workspace, not per-account. Run a US workspace for your HQ team and a Frankfurt workspace for your EU subsidiary from the same account.

What stays in your region

Once you pick a region, all of the following live in that region's infrastructure.

Uploaded files

CSV, Excel, PDF, images — stored in your region’s S3-compatible object storage.

Analytical database

A dedicated PostgreSQL instance (with TimescaleDB) per workspace. Aggregations, samples, scripts — all run on this regional DB.

Integration sync data

Records pulled from Shopify, Stripe, HubSpot, GA4, etc. land in your regional workspace DB, not a shared multi-tenant pool.

Chat & saved assets

Agent conversations, reports, scripts, dashboards, and Watches all persist to your region.

IoT device messages

A dedicated MQTT broker (EMQX) per workspace, in-region. Telemetry never crosses borders.

OAuth credentials

Encrypted with libsodium sealed boxes and stored in your regional credential vault. Tablize operators cannot decrypt them.

For transparency: what may briefly leave the region

These happen by default in the managed configuration. Each has a documented workaround if your compliance posture rules them out.

LLM inference

If you use our managed LLM pool, prompts route to Anthropic / OpenAI APIs (typically US). Responses are not retained. Workaround: bring your own LLM key (Anthropic, OpenAI, Azure OpenAI in any region, or self-hosted Llama / Qwen). Prompts then bypass our servers entirely.

Billing

Card data is handled by Stripe (US-based). Card numbers never reach Tablize servers (we are PCI DSS out-of-scope).

Watch alerts and team invites send via Postmark (US). The agent sends summaries only — never raw rows or sensitive payloads.

Compliance

GDPR (EU)

For Frankfurt (fra) workspaces, data stays in the EU and your workspace acts as the data controller. We sign DPAs (Standard Contractual Clauses included) on Enterprise plans. Right to access, rectify, port, and erase are all wired into the workspace settings.

APPI (Japan)

For Tokyo (nrt) workspaces, we operate as a data handler under the Japanese Personal Information Protection Act with appropriate oversight of subprocessors. Disclosure / correction / deletion requests are honored within 30 days.

CCPA / CPRA (US)

Right to know, delete, and opt out of "sale" (we don’t sell). Privacy notice and deletion tooling exposed in workspace settings.

Encryption

TLS 1.3 in transit; disk-level encryption at rest (Fly.io infrastructure). OAuth credentials get an additional libsodium envelope encryption layer.

Tenant isolation

Dedicated machine, dedicated DB, dedicated storage per workspace. Physical-layer tenancy separation. Tablize staff need Privileged Access Management with audit-logged approval to touch production data.

Audit logs

On Pro and above we log every sensitive operation (integration connect, credential change, role change, data export, public link creation). Exportable on Max / Enterprise.

Backups & recovery

Managed workspaces: nightly snapshots, 7-day retention, in-region. RPO 24h, RTO 4h. Enterprise unlocks extended retention and point-in-time recovery.

SOC 2 / ISO 27001

Not yet certified. We are running Drata-style controls and preparing for SOC 2 Type II audit window. Reach trust@tablize.com for current status.

DPA

For Enterprise customers we sign DPAs aligned with GDPR, APPI, and US state laws. Subprocessor list, data flow diagram, and deletion procedures are attached.

For the strictest sovereignty requirements: self-host

When third-party clouds are off the table — financial, healthcare, public sector, defense — run Tablize on your own infrastructure. Same binary, deployed via Docker Compose on AWS, GCP, Azure, Alibaba Cloud, Sakura, Oracle Cloud, OVH, or on-premises. Your network boundary, your encryption keys, your audit log.

Self-host docs →

Frequently asked questions

Can you prove my workspace is actually in the region I selected?

Yes. Settings → Workspace shows the region code. On request we provide Fly.io machine placement evidence and DNS dig results. Enterprise DPAs include this as an annex.

Can free-tier workspaces pick a region?

Yes. Free can pick any of the 4 regions at creation, but free workspace data is ephemeral (discarded at session end). Persistent regional storage starts at Plus.

Can I migrate an existing workspace to a different region?

Not in-place. Create a new workspace in the target region and re-import via exports or re-connect integrations. For large workloads contact support@tablize.com — we help with the migration.

Can I self-host instead?

Yes — Pro plan and up. Same binary, deployed via Docker Compose on your AWS, GCP, Azure, on-prem, or sovereign cloud (e.g. Sakura, Oracle, OVH, Alibaba). See self-host docs.

Does IoT telemetry also stay in-region?

Yes. Each workspace gets its own MQTT broker (EMQX) in the selected region. Devices connect over TLS (port 8883) directly to your regional endpoint.

Can I keep LLM inference in-region too?

Two paths. (1) Bring your own LLM key — for example Azure OpenAI deployed in Frankfurt or Tokyo, or Anthropic via your own account. (2) Self-host with `BYO_LLM_URL` pointing at an on-prem Llama / Qwen / Mistral. Both keep prompts and responses inside your chosen jurisdiction.

My auditor needs the exact data center address.

Each region maps to Fly.io facilities (nrt = Tokyo area, fra = Frankfurt, sjc = San Jose, hkg = Hong Kong). Formal location attestation, Fly.io SOC 2 reports, and subprocessor details are available via trust@tablize.com.

What happens when I request data deletion?

Deleting a workspace purges the PostgreSQL DB, S3 bucket, MQTT broker, and credential vault within 30 days. For immediate deletion email trust@tablize.com — we issue a deletion certificate. Backups roll over within 7 days, leaving no residual data.

For procurement and audit teams

DPAs, subprocessor list, pen-test results, SOC 2 status, Fly.io location attestation — email trust@tablize.com and we'll send a Trust Pack within 2 business days.

Request Trust Pack