Concepts
Region mode
Three sovereignty profiles — default, eu-permissive, eu-strict — and exactly which hops they affect.
Region mode is a per-workspace setting that controls where your code and its derived embeddings travel. Three modes ship today:
| Mode | Storage | Indexer worker | Embeddings | Status |
|---|---|---|---|---|
default | EU (Supabase eu-central-1) | EU (Railway Frankfurt) | US (Voyage) | GA |
eu-permissive | EU | EU | US (Voyage) with audit log | GA |
eu-strict | EU | EU | EU (RunPod-hosted Qwen-Embed) | Phase 3 GA |
default
The out-of-the-box configuration. Code clones happen on the EU worker,
storage stays in eu-central-1, and only the embedding payload
(symbol-scoped code chunks, ~200–800 tokens each) hits Voyage
in the US. No identifying metadata is sent — just the raw chunk
text and an internal request ID.
eu-permissive
Same data flow as default, but every Voyage call is logged with
chunk hash, length, latency, and request ID. The audit log is
retained for 90 days inside your tenant's Supabase rows and exposed
via the dashboard (Phase 2.9). Use this when your compliance team
wants traceability for the US hop but does not require it eliminated.
eu-strict
Swaps Voyage for an EU-hosted Qwen-Embed deployment on RunPod (Frankfurt). No code or embedding text leaves the EU. Trade-off: slightly lower recall (~0.86 vs. 0.91 on the bench set), higher embed latency, and a higher embedding cost per token because we operate the GPUs ourselves rather than paying Voyage's amortised rate.
How to set it
Today: per-workspace, server-side, by us at provisioning time.
Self-service: arrives with the dashboard (Phase 2.9). The MCP server
respects a PROMETHEUS_REGION_MODE environment override for local
testing, but the authoritative setting lives on the workspace
record and the worker rejects index runs whose declared mode diverges
from the workspace's configured mode.
What does not change with region mode
- The Supabase region (
eu-central-1) is hard-coded for all Prometheus tenants. We do not offer US or APAC storage. - The MCP server transport (
stdio) runs entirely on your machine regardless of region mode. - The web surface (
prom.codes) is served from Vercel'sfra1edge region for every visitor.
If you need a region profile we do not list here (e.g. CH-only, on-prem), tell us — the architecture supports it, we just have not built the deploy automation yet.