SaluteSpeech TTS (Sber) Speech Synthesis Integration

Integration of SaluteSpeech TTS (Sber) for Speech Synthesis

AI Development Areas

Frequently Asked Questions

העבודות האחרונות

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1441
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1301
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    998
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1267
  • image_logo-advance_0.webp
    B2B Advance company logo design
    713
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    1003

Integration of SaluteSpeech TTS (Sber) for Speech Synthesis

A typical integration challenge with SaluteSpeech TTS is the short-lived access tokens (30 minutes) and Sber's non-standard SSL certificate chain. Without automatic token refresh, the service breaks every half hour; ignoring the certificate causes SSLError in production. We set up a full speech synthesis pipeline solving both. For one retailer, we deployed an on-premise solution with auto-refresh, reducing p99 latency from 800 ms to 450 ms due to local processing. The on-premise transition saved the company over $1.8k–2.6k annually in cloud request costs, and for large projects savings can reach $2.7k–3.9k per year.

Available SaluteSpeech TTS Voices

SaluteSpeech offers six built-in voices with different emotional tones. All voices synthesize speech at 24 kHz and support WAV16 format.

Voice Type Emotions Sample Rate
Nec Neutral male neutral, sad, glad, evil 24000 Hz
Bys Warm male neutral, sad, glad 24000 Hz
May Female neutral, sad, glad, evil 24000 Hz
Tur Emotional male neutral, sad, glad, evil 24000 Hz
Ost Official male neutral 24000 Hz
Pon Friendly female neutral, sad, glad 24000 Hz

For long texts (more than 5000 characters), we automate chunking by sentence boundaries.

Why On-Premise Is Critical for Corporate Clients?

For companies with trade secret or state secret regimes, cloud connectivity is not allowed. SaluteSpeech TTS can be deployed inside the perimeter—data never leaves your network. We configure:

  • Sber's root certificate for internal PKI
  • Routing via internal load balancer
  • Monitoring with Prometheus + Grafana (p99 latency, request count, auth errors)

On-premise also reduces dependency on external channels: cloud latency can reach 1.5 s, while local processing stays around 400–500 ms. For p99 latency, SaluteSpeech TTS on-premise is 1.6 times faster than cloud Yandex SpeechKit. Data from official SaluteSpeech and Yandex SpeechKit documentation.

How to Automate Token Refresh?

Here is a basic background worker in Python using apscheduler:

import requests import base64 from apscheduler.schedulers.background import BackgroundScheduler def refresh_token(client_id, client_secret): response = requests.post( "https://ngw.devices.sberbank.ru:9443/api/v2/oauth", headers={ "Authorization": f"Basic {base64.b64encode(f'{client_id}:{client_secret}'.encode()).decode()}", "RqUID": "unique-uuid-here", "Content-Type": "application/x-www-form-urlencoded" }, data={"scope": "SALUTE_SPEECH_CORP"}, verify="/path/to/sber-root-ca.pem" ) new_token = response.json()["access_token"] # Save to Vault or Redis with TTL return new_token scheduler = BackgroundScheduler() scheduler.add_job(refresh_token, 'interval', minutes=25, args=[CLIENT_ID, CLIENT_SECRET]) scheduler.start() 

Refresh runs 5 minutes before token expiry, overwriting in a secure store. This guarantees uninterrupted synthesis uptime. On failure, the worker retries up to 3 times with exponential backoff.

Integration Process Step by Step

  1. Scenario analysis – determine required voices, load, on-premise necessity.
  2. Architecture design – choose REST API or gRPC, configure balancing and audio caching.
  3. Microservice implementation – write token refresh worker, error handling, text chunking.
  4. Integration testing – verify with your CRM, IVR, or chatbot.
  5. Deploy and monitor – deploy in your environment, set up alerts for latency and errors.

What's Included in the Full Scope of Work

  • Architecture design (REST API / gRPC, load balancing, audio caching)
  • Synthesis microservice with auto token refresh and error handling
  • SSL trust configuration for Sber API (install root certificate)
  • Integration with your system (CRM, IVR, chatbot) via REST or queues
  • Load testing (up to 100 RPS, p99 latency measurement)
  • Operations documentation and monitoring scripts

Comparison of SaluteSpeech TTS and Yandex SpeechKit

Parameter SaluteSpeech TTS Yandex SpeechKit
On-premise Yes No (cloud only)
p99 Latency < 500 ms 600–900 ms
Business voices 4 (Nec, Ost, Bys, Pon) 2 (alyona, filipp)
Token refresh Automatic Manual every 12 hours
SSL certificates Sber-specific Standard

The table shows: for corporate scenarios with security requirements, SaluteSpeech wins on latency and on-premise capability. However, for creative tasks Yandex offers more emotions. Get a consultation—we'll help you choose the right solution.

Technical requirements for on-premise - OS: Linux (Ubuntu 20.04+, CentOS 7+) - Docker and Docker Compose - Access to Sber container registry - Sber root certificate (provided by client)

Estimated Timelines

From 2 to 5 days depending on complexity (on-premise, number of voices, integration with legacy systems). Pricing is custom—contact us for an estimate.

Our team has extensive market experience and 30+ projects with TTS systems (Yandex, Google, Amazon Polly, Sber). We guarantee correct handling of Sber's SSL specifics and stable synthesis uptime.

Contact us for a preliminary assessment—we'll send an integration example with your test phrase. Get a consultation on your scenario.

Learn more at the SaluteSpeech API official documentation.