CamplaxAlways involved
| Provider | What it does for Camplax | Where |
|---|---|---|
| Cloudflare | Runs the Camplax website, console and API, and the platform database, queues and key-value stores. Provides DNS, TLS certificates, the network edge and firewall in front of every app, file storage (R2), the sign-up bot check (Turnstile), deploy screenshots (Browser Rendering), and inbound email routing. | Global network; storage in [[Cloudflare D1 and R2 storage region]] |
| OVHcloud | The servers (“cells”) that run customer apps, their databases, and builds. | United States; [[OVHcloud contracting entity and datacenter]] |
| Amazon Web Services (Amazon SES) | Sends email for Camplax (sign-in links, alerts) and for apps. | United States (us-east-2, Ohio) |
| Stripe | Takes card payments for plans and credit packs, and keeps the payment details. Camplax never stores full card numbers. | United States and others, per Stripe |
| Better Auth | Sign-in infrastructure for Camplax console accounts (not for the people who sign in to your app). | [[Better Auth Cloud region and the data it receives]] |
Only when a feature is used
| Provider | What it does for Camplax | When |
|---|---|---|
| OpenAI | The model behind Lee, the console assistant. Receives the question and the project context Lee reads to answer it. | When someone uses Lee |
| OpenRouter | The AI gateway for apps: forwards an app’s model requests to the model provider the app chooses, which also receives them. | When an owner turns AI on for an app |
| GitHub | Imports and deploys code from a connected repository, and signs people in with GitHub. | When you connect a repository or choose GitHub sign-in |
| Signs people in with a Google account. | When you choose Google sign-in | |
| Fly.io and Prisma (Prisma Postgres) | Compute and databases for apps created before cells. Being retired; new apps never use them. | Only for apps made before cells |
How we manage changes
Camplax updates this page before a new provider starts handling customer data, subject to any notice period in the data processing addendum. A customer with a signed addendum may object by writing to [[privacy contact email and postal address]]; the final addendum states the review and objection process.
Data location and transfers
Customer apps and their databases run on Camplax’s own servers in the United States. The control plane runs on Cloudflare’s global network. Camplax does not yet offer a choice of region. Transfers rely on [[transfer mechanism for each provider, for example the EU Standard Contractual Clauses, as confirmed by counsel]]. See the Privacy Notice for the broader handling explanation.