Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.factory.ai/llms.txt

Use this file to discover all available pages before exploring further.

Factory operates a dedicated EU deployment, fully isolated from the Global (US) deployment, with its own backend, database, and LLM inference endpoints in Europe. Each Factory client (CLI, desktop app, and web app) ships as a single build that works in both regions; after login, the client detects the organization’s region and routes all subsequent requests to the correct deployment.
Enterprise Feature — The EU deployment is available to enterprise customers with European data-residency requirements. Contact us to provision an EU organization for your team.

​
Infrastructure

The EU API backend is hosted on Vercel in Frankfurt (fra1), within the European Economic Area, and reachable at api.eu.factory.ai. Customers should allowlist *.factory.ai hostnames. Outbound LLM traffic from the EU backend targets the EU-region endpoints of the providers listed under Inference.

​
Data

Stored in the EU (europe-west1, Belgium):
  • Session content (prompts, assistant messages, tool calls and results, Droid messages, Git AI notes, and Git AI checkpoints) lives in a managed database instance in Belgium, provisioned separately from the global database with its own credentials, backups, and access controls.
  • Raw request and response bodies are never written to logs or object storage.
Stored in the global deployment (US):
  • Organization records (a small pointer document with the org’s region tag), user profiles, and billing data. These contain no user-generated content and are required for cross-region authentication and account management.

​
Inference

All LLM requests from EU organizations are dispatched to EU-region endpoints only; prompts and conversation history do not transit US infrastructure.

Anthropic Claude

Served via AWS Bedrock (Frankfurt, eu-central-1) and Google Vertex AI (europe-west1). Includes Claude Opus 4.5, Opus 4.6, Opus 4.7, Sonnet 4.5, Sonnet 4.6, and Haiku 4.5.

OpenAI

Served via the OpenAI direct API using a dedicated project configured for EU data residency. Includes the GPT-5 family (GPT-5.2, GPT-5.3 Codex, GPT-5.4, GPT-5.4 Mini, GPT-5.5, and GPT-5.5 Pro).
Models or providers not available in the EU are hidden in the model picker and rejected at the server.

​
Enforcement

Identity is global (WorkOS-based SSO), but each organization is pinned to a region at creation time. Region matching is enforced at multiple layers so traffic and data can never be served by the wrong backend. Server-side. Session data access and LLM inference are both gated by region-aware checks on the backend. Requests for an organization whose region does not match the deployment fail closed with an error, and requests for ineligible models or providers are rejected before any traffic is dispatched. EU traffic cannot reach US-only data or providers, and Global traffic cannot reach EU-only routes. Client-side. After login, each client reads the org’s region and routes all subsequent API requests to the matching backend:
  • Web app: Each canonical hostname (app.factory.ai, app.eu.factory.ai) is statically backed by exactly one regional backend. Users who land on the wrong region are shown a redirect page with a link to the correct origin; they are not signed out.
  • Desktop app: Reads the org’s region from the authenticated session and targets the matching API host on every request.
  • CLI: The region is pinned to the user’s local token cache on first login and used to resolve the API host for every request. Logout and re-login re-derive the region.