Novo Agents Subprocessors

Third-party providers used to operate Novo Agents.

Last updated: July 10, 2026

Novo Agents Subprocessors

Last updated: July 10, 2026

Novo uses the third-party providers below to operate Novo Agents. AI requests are routed to one or more of the listed AI providers depending on the task, your configuration, and availability, and routing is restricted to this disclosed set. Selecting the strict data-handling option further restricts AI processing to configurations verified for zero data retention and no training use, as described in the product documentation.

Infrastructure and operations

ProviderPurpose
VercelHosting, compute, workflow runtime, isolated execution sandboxes, and AI gateway routing
SupabaseDatabase and object storage
WorkOSConsole authentication, organization management, and account email delivery
StripePayment processing and billing records
SentryError reporting and reliability diagnostics
PostHogProduct analytics (content-free usage events)
Google and MicrosoftSign-in identity when selected as a console sign-in method

AI and media providers

ProviderPurpose
AnthropicAI inference
OpenAIAI inference and image generation
Google Cloud (Vertex AI)AI inference, media generation and analysis, and temporary staging storage
xAIAI inference
Fireworks AIAI model hosting
BasetenAI model hosting
Together AIAI model hosting
Microsoft AzureAI model hosting
Amazon Web ServicesAI model hosting
ElevenLabsSpeech and audio generation
PerplexityWeb search
BrowserbaseManaged browser sessions

Customer-directed destinations

Data also flows to systems that you configure and control, at your direction. These are not Novo subprocessors:

  • execution environments, tool servers, webhooks, and result destinations you connect;
  • source-control hosts you connect, such as GitHub;
  • websites and third-party services your agents interact with at your direction.

Novo reviews providers before material changes and updates this list before a new provider receives Customer Data.