Skip to main content
Version: v2.0

Agenta Sub-processors

Last updated: February 4, 2026

If you have questions, contact security@agenta.ai.

note

This list applies to Agenta Cloud (managed SaaS) only. It does not apply to self-hosted deployments.

Current Sub-processors (EU)​

Sub-processorPurposeLocation
Amazon Web Services (AWS)Cloud hosting providerEU (Frankfurt)
SuperTokensAuthentication providerEU
DaytonaCode execution sandboxEU
PostHogProduct analyticsUS (soon EU)
New RelicApplication monitoringEU
CrispCustomer support chatEU (Global)
StripePayments & billingUS (Global)
LoopsMarketing email providerUS (Global)
SendGridTransactional email providerUS (Global)

Current Sub-processors (US)​

Sub-processorPurposeLocation
Amazon Web Services (AWS)Cloud hosting providerUS (Ohio)
SuperTokensAuthentication providerUS
DaytonaCode execution sandboxUS
PostHogProduct analyticsUS
New RelicApplication monitoringEU
CrispCustomer support chatEU (Global)
StripePayments & billingUS (Global)
LoopsMarketing email providerUS (Global)
SendGridTransactional email providerUS (Global)

FAQ​

Do you send my data to LLM providers?​

Agenta does not process customer data through LLM providers by default.

When you use the Playground or run evaluations:

  • You bring your own LLM API keys (OpenAI, Anthropic, etc.).
  • Requests are sent directly from your browser/application to the LLM provider.
  • Agenta does not store or proxy LLM API calls in typical production use.

For demo/trial purposes, Agenta may provide demo API keys. For production workloads, use your own keys.

Does this list apply to self-hosted deployments?​

No. For self-hosted deployments, you control your own infrastructure and any sub-processors you choose to use.