Platform

  • Overview
  • AI Gateway
  • Observability
  • FinOps
  • Reliability

Solutions

  • Optimization
  • Governance
  • Clyvel AI
  • Pricing
  • Enterprise

Resources

  • Documentation
  • Blog
  • Resources
  • Start free

Company

  • Home
  • For businesses
  • Contact
  • Sign in

Legal & security

  • Privacy policy
  • Terms of use
  • Security
  • Refund policy
  • Cookies
  • Data processing
Clyvel

© 2026 Clyvel

Operate

AI GatewayRoute and control every model request.ObservabilitySee every request, token, error and latency signal.ReliabilityIncidents, provider health, latency and failures.

Analyze

Costs & FinOpsUnderstand spend, budgets and cost allocation.OptimizationFind measurable savings across models and routing.

Control

GovernancePolicies, roles, approvals and audit controls.Clyvel AIAsk what changed, why it happened and what to do next.

One platform for production AI operations.

View all products
EngineeringDebug production AI traffic from one operational layer.Platform teamsStandardize routing, providers and reliability controls.FinOps & FinanceControl AI spend, budgets and optimization outcomes.Security & GovernanceApply access, policy and audit controls at scale.
Pricing

DATA PROTECTION

Subprocessors

Service providers used to operate Clyvel and the functions they perform.

Last updated September 22, 2026

Legal & trust

TermsRefunds & cancellationPrivacySecurityAcceptable useData processingSubprocessorsCookies

Core service providers

  • Vercel — frontend hosting, edge delivery and deployment infrastructure.
  • Railway — backend application hosting and production infrastructure used by Clyvel.
  • Resend — transactional email delivery when enabled in production.
  • Google — OAuth identity services when a user chooses Google sign-in.
  • Paddle — subscription checkout, billing and payment-related processing when paid billing is enabled.

Customer-directed AI providers

Clyvel can route traffic to AI providers selected and configured by the customer. Those providers process request content at the customer's direction and under the customer's relationship with the provider. Depending on configuration, this may include providers such as OpenAI, Anthropic, Google or other supported OpenAI-compatible endpoints.

Processing locations

Processing locations and data-residency options depend on the relevant provider, account and deployment configuration. Customers with mandatory residency or sector-specific requirements should confirm the applicable provider region and contractual terms before sending regulated data.

Changes

Clyvel may update this list when providers are added, replaced or removed. Material changes affecting customer personal data should be communicated through a reasonable notice mechanism where required by contract or law.