Skip to content

Integrations

Frontier integrates with a variety of third-party services to deliver real-time AI sales coaching. These integrations span meeting capture, speech-to-text, large language models, core cloud infrastructure, authentication, workflow orchestration, CRM actions, and observability. This page details the key external services involved in Frontier’s live operational path. For a comprehensive register of all data-path and dev-tooling sub-processors, refer to the Trust → Sub-processors page.

  • Recall.ai: This service facilitates meeting capture. The Recall Desktop SDK runs within the Electron desktop application on the rep’s machine (rather than a cloud bot joining the meeting), enabling calendar and meeting OAuth integrations via Google, Microsoft, and Zoom credentials to detect and manage calls.
  • Deepgram: This service provides speech-to-text transcription. Frontier is currently mid-migration to direct mic and speaker capture via the desktop application, streaming audio directly to Deepgram for complete separation of rep and customer audio feeds. This direct connection to Deepgram is now the authoritative transcription path.
  • Large Language Model (LLM) Providers: Frontier employs a multi-provider strategy for LLMs, integrating with Anthropic, OpenAI, Google (Gemini), and Together AI. These providers process call transcript and knowledge base content for tasks such as answer generation, question detection, and query rewriting, all managed via the Vercel AI SDK provider packages.
  • Cloudflare AI Gateway ‘frontier-ai’: This gateway serves as a routing layer for LLM requests within the Cloudflare environment.
  • OpenRouter: Acts as a fallback embedding provider (baai/bge-large-en-v1.5) when Cloudflare Workers AI times out or fails (with retry on 503/429/529). Today it is only an embeddings fallback — not a general LLM gateway/router.
  • Cloudflare AI Search: This is one of the backend services actively under evaluation for Frontier’s Knowledge Base (KB) layer, used for knowledge retrieval.
  • Supermemory: This service provides an interim bridge for the Knowledge Base and memory layer, actively utilized in answer generation and fast-answer flows.
  • Pinecone: An integrated vector database solution for embeddings and retrieval, with existing configurations for Cloudflare-fronted indexes.
  • Cohere: Employed for paraphrase and semantic similarity detection, particularly over script and manifest content within the Dashboard application.
  • Firecrawl: This service is used to crawl and scrape customer organization websites to build content for the Knowledge Base, including a webhook callback mechanism.
  • Cloudflare: Serves as Frontier’s primary compute substrate and a core data-path sub-processor. This includes Cloudflare Workers (hosting the Call Server and Durable Objects), Cloudflare D1 (SQLite databases for per-call state), Cloudflare Vectorize (indexes for embeddings and retrieval), Cloudflare R2 (for storing crawled site data and backing AI Search knowledge), and Cloudflare Workers AI (for various AI tasks, including embeddings).
  • Supabase: Provides external managed Postgres for application configuration, background job metadata, and real-time subscriptions, accessed via Drizzle ORM.
  • Clerk: The identity and authentication sub-processor. Clerk manages user identities, providing @clerk/nextjs for the Dashboard and @clerk/backend for the Call Server, alongside Google social sign-in. Webhooks from Clerk are verified using Svix.
  • Inngest: This service provides the durable asynchronous layer, hosted within the Dashboard (Next.js) application. Inngest handles a wide range of background jobs and event orchestration, including processing Recall webhooks, bot scheduling, preference changes, rate limiting, knowledge ingestion (document processing, deletion, status checks), AI Search re-indexing, FAQ/script synchronization, website crawls, user/organization lifecycle events, and call summaries/metrics. It also runs cron-scheduled jobs for periodic tasks.
  • Composio: An agent tool-router that executes external tools during call agent runs. It enables CRM tool actions by forwarding call context to external APIs.
  • Axiom: Provides logging, tracing, and metrics for the platform.
  • Sentry: Used for error tracking, with severity-based routing for incidents.
  • PostHog: Collects product and LLM telemetry. These observability services may receive call metadata, transcript-derived telemetry, and user identifiers.
  • Doppler: Manages secrets for all environments, providing a centralized and authoritative store for API keys and sensitive configuration, including those for all third-party integrations.