Technology · Security
01

Data inside Russia
stored and processed in the Russian contour

02

Encryption in transit
and encryption on disk at rest

03

Training on your data
models are never fine-tuned on customer dialogues

Secure by default

02CONTROLS

The contour under control

Security is not a slide — it is a set of working mechanisms. Here are the main ones.

/01

Tenant isolation

Every company lives in its own space — the data never crosses over.

/02

Keys in the vault

Credentials and tokens live in secure storage — not in the code and not in the dialogues.

/03

Role model

Owner, administrator, operator, guest — each with exactly their own rights.

/04

Action log

Who changed what and when — visible to your security team.

/05

Rate limits

Protection from brute force and overload: requests are rate-limited.

/06

Backups

Regular backups and a rehearsed restore.

03Architecture

Data at the centre

Your data in the centre, the perimeter around it. Encryption, roles and isolation hold the border; the log, the vault and monitoring run inside it without a break.

Perimeter
Your data
Encryption
Roles
Isolation
Backups
Knowledge base
Vector store
Dialogues
Log
Secrets
Monitoring
Updates
Recovery
04AUDIT

Do not take our word for it, check

We are for audits, not promises. The architecture description, data-flow diagrams, connector action lists and the call log — all handed to your security team before launch.

01

On trust.
Every access and every external call is agreed and recorded.

02

Contours.
The data never leaves the perimeter you chose — the Russian cloud or your own.

03

Transparency.
The action log is available to your security team.

05WHERE THE DATA LIVES

You choose the perimeter

One and the same product, three degrees of isolation. From a managed cloud in Russia to an install with no internet access at all.

RUSSIAN CLOUD

A managed contour

Sites in Russia, tenant isolation, encryption by default.

ON-PREMISE

Your perimeter

The whole platform on your own servers.

AIR-GAP

No internet

A fully isolated install for strict contours.

06RELIABILITY

Reliability in numbers

Security without availability is worth nothing. The platform is observable at every node, and recovery is a rehearsed procedure rather than heroics.

01

Availability
the target service level

02

Monitoring
metrics and alerts on every node

03

Detection
alerts arrive before complaints

04

Data incidents
in the whole history of the platform

Recovery · min · by scenario
PeakTypical
GET STARTED

Test it on your own data

Upload your own documents and catalogue — then ask the assistant the questions people ask you. That is the only test that means anything.