Katexs
Security overview

Security

Security overview

How Katexs isolates tenants, protects secrets and limits what every component can do.

Tenant isolation

Tenant isolation Each workspace owns its agents, numbers, calls, contacts and credits. Every voice resource is tagged with its workspace id, and any event whose tag does not match the owning workspace is refused. Workspaces never see each other Workspace Aworkspace_id = 7f3c… Agents Numbers Calls & chats Contacts Knowledge Credits Workspace Bworkspace_id = c219… Agents Numbers Calls & chats Contacts Knowledge Credits Enforced at four layers Database: row-level security on every table, scoped to workspace membership. Voice engine: every assistant and number carries metadata.workspaceId; events whose tag does not match are refused. Browser: short-lived, scoped tokens. Private keys never leave the server. Tools and chat: rate limits per workspace, contact and visitor.
Every workspace is isolated at the database, voice engine, browser and tool layers.
  • Database — row-level security on every table, scoped to workspace membership. Server code that needs elevated access re-checks the workspace explicitly.
  • Voice engine — every agent and number carries its workspace id. Each voice event is matched to the agent's workspace and refused if the tags disagree. A number can't route a call to another workspace's agent.
  • Browser — the browser only ever receives short-lived, single-purpose tokens. Chat visitor tokens are signed and bound to one agent.
  • Rate limits — per workspace, per contact, per visitor and per IP address.

Least privilege

  • Tools must be enabled per agent.
  • Custom functions can only call public HTTPS endpoints, never internal networks.
  • Team members get roles, and permissions are checked on the server for every request.
  • Flows call tools through a bridge scoped to one session, run and node.

Verified inputs

Every external boundary validates its input with a strict schema before acting: chat requests, tool arguments, widget settings, event payloads. Events from the voice engine are verified with a shared secret; unsigned requests are rejected and recorded.

No silent failures

Every failure path returns a clear message to the caller or visitor and writes a structured log with the reason. Failed charges are released for retry rather than dropped.

Last updated November 2026 · Found a problem? Email support@katexs.com