Data Residency
US primary today. EU region on the 2026 roadmap. Air-gapped self-host available today via Docker and Postgres. Enterprise dedicated instances with region of choice.
Where your data lives
All new accounts default to US-East-1. Vercel (global edge for the static site and CDN) + Supabase Postgres with pgvector (us-east-1) for memory storage. Railway (us-west) for compute workers.
Frankfurt (eu-central-1) for customers who need strict EEA data residency. Enterprise customers can provision an EU instance today on request; public availability planned Q3 2026.
Run REM Labs on your own infrastructure. Docker image + Postgres (any version ≥ 14 with pgvector). Works in any region, any cloud, and fully air-gapped. Zero phone-home, no license keys, no telemetry.
Single-tenant deployment with the region of your choice. Customer-managed encryption keys (CMEK), private network peering, and signed DPA + BAA (healthcare). Uptime SLA 99.95% with financially-backed credits.
How residency works
Memories you submit are written to the primary database in your region. Backups are encrypted and stored in the same region (or cross-region if you opt in).
Embedding calls to OpenAI or Anthropic go over TLS. Per their API terms, inputs are not used for training and are not retained beyond the immediate request. If you need fully-on-prem embeddings, use the self-host option with a local model.
The website you're reading is cached globally for performance. No user data is served from the edge — only public HTML/CSS/JS.
Every mutation is written to a region-local audit log. Enterprise customers can mirror to their own SIEM via webhook.
Need a specific region?
We prioritize our region roadmap based on customer demand. If you need a region we don't list today, email legal@remlabs.ai and we'll tell you the exact timeline (or spin up a dedicated enterprise instance now).