Why Blendlix Call Service?

Blendlix Call Service gives applications a reusable way to add secure one-to-one audio calling without rebuilding realtime call infrastructure for every product.

Separation of business logic

Applications already know their own users, roles, permissions, subscriptions, and workflows. Blendlix Call Service does not replace that authority.

Instead, the application backend checks whether a call is allowed, then requests a short-lived session token for the client.

Scalable realtime architecture

Realtime calling needs presence, WebSocket signaling, call state, timeouts, rate limits, and connection cleanup. Keeping this logic in a dedicated service makes it easier to scale and maintain.

Reusable across products

The service uses generic terms such as:

• product
• caller
• receiver
• participant
• context
• role

This makes it suitable for different applications without changing the core service.

Backend-controlled authorization

The application backend remains responsible for authorization. Blendlix Call Service enforces the token claims it receives, including participant role limits and product isolation.

Secure token-based authentication

Clients do not receive product secrets. They receive short-lived session tokens that are scoped to one product, one user, one role, one context, and one allowed peer role.

Why WebRTC and WebSocket?

Why not embed calling inside every application?

Embedding call infrastructure into each application creates duplicated work and makes updates harder. A dedicated service gives every application the same calling foundation while allowing each application to keep control of its own business rules.