This list reflects Limena’s current production stack: the third-party services that may process tenant data. Pure infrastructure that does not process tenant data (DNS, uptime monitoring) is not listed.
- Fly.ioLondon (lhr)Live
Hosting for the FastAPI backend and ARQ worker (api.limena.io).
- VercelGlobal edge (CDN)Live
Hosting and CDN for the Next.js application at limena.io.
- SupabaseEU (London)Live
Managed PostgreSQL: the primary application database holding tenant records.
- UpstashEU (London)Live
Managed Redis: cache, ARQ job queue, rate-limit counters, and AI usage quotas.
- Cloudflare R2Global edgeLive
Object storage for files you upload: prospect-list CSVs and entity attachments.
- AnthropicUnited StatesLive
AI inference for tenants on the managed "Limena AI" tier (Claude API). Bring-your-own-key tenants use their own provider instead.
- OpenAIUnited StatesLive
Text embeddings for semantic search and record-similarity features (Embeddings API). Short snippets from your records are sent to generate vectors; per OpenAI’s API terms, inputs are not used to train their models.
- ResendEULive
Outbound system mail: invitations, password resets, demo-request notifications. NOT outbound tenant campaigns (those route through your connected Gmail or Microsoft 365 account).
- SentryEU (Frankfurt)Live
Backend + frontend exception capture. Tenant data is never intentionally sent; stack traces, request IDs, and URL paths only.
- Google (Gmail API)Your account’s regionLive
Only for tenants who connect a Gmail or Google Workspace mailbox via OAuth. Limena reads + sends on the connected mailbox; reply notifications use Google Cloud Pub/Sub.
- Microsoft (Graph API)Your account’s regionLive
Only for tenants who connect a Microsoft 365 / Outlook mailbox via OAuth. Limena reads + sends on the connected mailbox, with reply ingestion via Graph subscriptions.
Materially new sub-processors (meaning a new third party that will process tenant data beyond what these existing categories cover) are announced here at least 30 days before going live, except where they are a like-for-like replacement of an existing entry.