The role of a provider depends on the data and feature involved. The first table identifies providers that may process Customer Personal Data for delivery, security, execution or observability of the Service. Official provider legal references are supplied for procurement review. The second table identifies other material business providers so the distinction is not hidden or overstated.
Provider
Purpose
Role
Use
Provider legal
Supabase
Database, storage and server-side data infrastructure
Subprocessor
Core
Vercel
Application hosting, server execution and edge delivery
Subprocessor / infrastructure provider
Core
Clerk
Authentication and identity management
Subprocessor for account/identity data
Core
Composio
Managed connections and tool execution for customer-authorised third-party integrations
Feature-dependent subprocessor
Only when enabled/connected
Upstash
Redis-backed abuse prevention and request rate-limiting
Security infrastructure subprocessor
When production rate limiting is configured
Inngest
Durable event orchestration, retries and background workflow execution
Execution infrastructure subprocessor
When durable execution is enabled
Sentry
Application error monitoring and operational diagnostics
Observability subprocessor
When error monitoring is configured
PostHog
Optional product and sandbox analytics
Analytics subprocessor
Client analytics only after required consent; server telemetry when configured
Google Workspace
Business and application transactional email using an authorised Workspace mailbox
Business communications service provider
Stripe
Payments, subscriptions and billing
Payment provider; role may vary by processing activity
Apollo
B2B sales research/enrichment and outbound operations
Sales-data/service provider; not used as a customer pipeline data store
AI/model providers
Assisted extraction, classification, research or drafting when configured
Feature-dependent; relevant provider disclosed/configured for the workflow
A provider is not treated as active for a customer workflow merely because it appears on this page. Feature-dependent providers process data only when the relevant feature is configured or used. Provider documentation is maintained by the provider and may change independently. Material changes to Customer Data subprocessors will be handled under the Aveniqra DPA.
