Speko icon

Speko

Speko is a voice AI router that benchmarks speech models by language and routes STT, LLM, and TTS through one API. It also offers packaged infrastructure and enterprise contracts.

Speko

Overview

Speko is a router for voice AI that presents itself as a hosted, provider-neutral STT, LLM, and TTS data plane. The homepage says it wires every speech model into one API and adds typed contracts and managed routing at router.speko.dev.

Its public site is centered on model selection and routing for voice applications. Speko benchmarks speech models language by language, then shows how those models compare on accuracy and cost across stages such as speech-to-text, LLM, text-to-speech, and speech-to-speech.

The pricing page separates the product into three paths: Router, Speko infra, and Enterprise. Router is in public preview and adds measured selection and pre-response failover on top of provider rates; Speko infra bundles the three voice-model legs into a single per-minute price; Enterprise is contract-based with deployment reviews and committed monthly minimums.

Overall, Speko is aimed at teams that need to choose among multiple speech providers and want that decision to be guided by benchmarks, routed through a single interface, and packaged with a clearer commercial boundary than stitching providers together manually.

Core capabilities

One API for the voice stack

Speko positions the Router as a hosted, provider-neutral runtime for speech workflows, combining STT, LLM, and TTS behind one API surface.

Language-level benchmark coverage

The homepage says models are benchmarked language by language, so selection can reflect how a model performs in the user’s language rather than relying on a single English ranking.

Managed routing and failover

The site presents routing as measured selection with pre-response failover, which suggests the product can choose among providers before a response is sent.

Contract-based API access

The homepage references typed contracts and public OpenAPI and AsyncAPI contracts for the hosted Router, which points to a formal integration interface for automated clients.

Gateway for voice frameworks

The Gateway section shows native integrations for LiveKit and Pipecat, plus support for provider-direct streaming and local BYOK credentials.

Comparative model boards

The homepage includes benchmark boards for speech-to-text, LLM, text-to-speech, and speech-to-speech, making model comparison part of the product workflow.

Where Speko fits

  • Selecting the right model per language

    Use Speko when a product needs to route speech traffic across multiple providers and choose models based on language-specific benchmark results rather than a single global ranking.

  • Centralizing a voice pipeline

    Use the Router when you want one hosted interface for STT, LLM, and TTS without wiring each provider separately, especially if your application already treats those stages as a pipeline.

  • Working inside voice frameworks

    Use the Gateway integrations when building with LiveKit or Pipecat and you want provider-direct streaming plus optional Speko-managed routes in the same setup.

  • Purchasing for a formal deployment

    Use Enterprise when procurement or operations require deployment reviews, contract-based access, dedicated support, or a committed monthly minimum.

Pros and Cons

Pros

  • Benchmarks are organized by language, which is useful when model performance varies across markets.
  • The product covers multiple voice stages, including STT, LLM, TTS, and speech-to-speech.
  • Pricing and routing boundaries are spelled out clearly across Router, Speko infra, and Enterprise.
  • The homepage surfaces typed contracts and public OpenAPI and AsyncAPI contracts for the hosted Router.
  • Native Gateway integrations are shown for LiveKit and Pipecat, which may reduce framework integration work.

Cons

  • The public pages do not provide a full integration reference, so implementation details are still sparse from the source material provided.
  • Router is listed as a public preview, and the pricing page notes there is no SLA during preview.

FAQ

What does Speko do?

Speko provides a router for voice AI that connects speech models into one API. The homepage describes it as a hosted, provider-neutral STT, LLM, and TTS data plane with typed contracts and managed routing.

How is Speko priced?

The pricing page separates three commercial paths: Router, Speko infra, and Enterprise. Router is public preview and adds managed routing on top of provider rates; Speko infra bundles speech-to-text, LLM, and TTS into a per-minute price; Enterprise is by contract with deployment reviews and a committed monthly minimum.

How do teams connect to Speko?

The homepage says the Router is available at router.speko.dev and can be used through public OpenAPI and AsyncAPI contracts. It also shows native Gateway integrations for LiveKit and Pipecat, plus an MCP endpoint for Claude or Cursor.

What is benchmarked on the site?

The benchmark tables on the homepage compare models by language and by stage, including speech-to-text, LLM, and text-to-speech. The pricing page also notes that routing includes measured selection and pre-response failover.

What information is not covered on the public pages?

The site does not present a full integration reference on the pages provided, so setup details such as authentication flow, SDK coverage, and endpoint schemas should be confirmed in the docs before implementation.

Quick Facts

Category
Voice AI router
Website
speko.ai
Primary workflow
Model routing and benchmark-based selection for voice apps
Public API surface
Hosted Router with OpenAPI and AsyncAPI contracts
Framework integrations
LiveKit, Pipecat
Pricing paths
Router, Speko infra, Enterprise