Self-Hosted Deployment

KugelAudio TTS can be deployed on your own infrastructure. We ship to Kubernetes clusters and provide a Helm chart for installation, configuration, and upgrades. There are two ways to run it:

	Self-managed	Managed on-premise
Who operates it	Your team, using the Helm chart	KugelAudio, inside your infrastructure
Support	Standard support	24/7 support hotline
Upgrades	You apply them	Handled for you

Managed on-premise

With a managed on-premise deployment, KugelAudio runs and maintains the stack inside your environment — you get the operational model of the hosted API without the audio ever leaving your infrastructure. Why teams choose it

Data protection. Text and audio are processed entirely within your network. Nothing is sent to a third-party endpoint, which is what makes the deployment workable under strict data-residency, GDPR, and sector-specific requirements in healthcare, finance, the public sector, and legal.
Latency. Serving the model next to the application that calls it removes the network round trip to a public endpoint — normally one of the three components of end-to-end latency, and the one you otherwise cannot tune. See Latency for the full breakdown.
Operations. KugelAudio handles rollout, upgrades, and monitoring, backed by a 24/7 support hotline.
Restricted environments. Works where egress to public APIs is limited or unavailable.

If you are prototyping or your data has no residency constraints, the hosted API is the simpler choice — start there and move later if you need to.

Get in touch

Both options are arranged through sales. Tell us which one fits and we’ll either send the Helm chart and a license key and walk you through the rollout, or scope the managed deployment with you.

Contact sales

hello@kugelaudio.com

Connect your SDK

Point the SDK at your deployment by setting the API URL directly. This overrides both the region parameter and any API key prefix.

Python
JavaScript
Java
cURL

from kugelaudio import KugelAudio

client = KugelAudio(
    api_key="your_api_key",
    api_url="https://tts.example.com",
)

Or with separate backend and TTS servers:

client = KugelAudio(
    api_key="your_api_key",
    api_url="https://api.example.com", # Backend for REST API
    tts_url="https://tts.example.com", # TTS server for streaming
)

import { KugelAudio } from 'kugelaudio';

const client = new KugelAudio({
  apiKey: 'your_api_key',
  apiUrl: 'https://tts.example.com',
});

Or with separate backend and TTS servers:

const client = new KugelAudio({
  apiKey: 'your_api_key',
  apiUrl: 'https://api.example.com', // Backend for REST API
  ttsUrl: 'https://tts.example.com', // TTS server for streaming
});

import com.kugelaudio.sdk.*;

KugelAudio client = new KugelAudio(
    KugelAudioOptions.builder("your_api_key")
        .apiUrl("https://tts.example.com")
        .build()
);

Or with separate REST and TTS servers:

KugelAudio client = new KugelAudio(
    KugelAudioOptions.builder("your_api_key")
        .apiUrl("https://api.example.com") // Backend for REST API
        .ttsUrl("https://tts.example.com") // TTS server for streaming
        .build()
);

curl -X POST https://tts.example.com/v1/tts/generate \
  -H "Authorization: Bearer $KUGELAUDIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text": "Hello from KugelAudio!", "model_id": "kugel-3", "voice_id": 1071}'

Replace the example hostnames with the endpoints supplied for your deployment.

Get started

Build a voice agent

Generate audio

Voices

Deploy

SDK Reference

API Reference

Self-Hosted Deployment

Managed on-premise

Get in touch

Contact sales

Connect your SDK

​Managed on-premise

​Get in touch

Contact sales

​Connect your SDK

Managed on-premise

Get in touch

Connect your SDK