Skip to content
ЗАПЕЧАТАНОINVITE-ONLY

Foryour own.

Discord got blocked. Slack left. Telegram is next. So we built our own.

SVOI brand wax seal
Your network

A network of your own.

Everyone here was invited by someone you trust. No strangers.

A.I.
A. Ivanov
founder of the circle
M.K.
M. Klimov
invited by A. Ivanov
Your invite is waiting

You can only get in through someone who is already inside. Everyone here has someone who vouched for them.

The team has been inside for six months. Now we are opening it for our own.

the Svoi team

Svoi team wax seal
Under the hood

No promises.

Speed and secrecy you can verify.

Secure

E2E by default (MLS, RFC 9420). Keys never leave your device. The server cannot read the contents.

Your deviceTheir deviceKeys stay with youServer cannot read the contents

Fast

Messages travel directly, without relays. Encryption adds no latency you can feel.

Tapped sendEncryptedDeliveredReceived
Structure

Space. Channel. Thread.

A team, a topic, a conversation. All in one place without turning into chaos.

  1. 01

    Space

    A team, a community, or your own circle.

  2. 02

    Channel

    A topic, a project or an event inside a space.

  3. 03

    Thread

    A separate conversation inside a channel, without flooding the feed.

About the law

We follow the law.But we cannothand it over.

An opened personnel file: kraft folder, archive label, a typewritten response to a state‑surveillance request bearing a red «Secret» stamp, and the SVOI wax seal hanging from jute twine

We operate in Russia, under Russian law. If we need to register locally, we do. When a lawful request comes in, we cooperate.

The point is, our architecture means we can't see what you write either. End-to-end encryption, keys on your devices only, the server holds only a sealed ciphertext. Nobody reads it, not us, not the requester.

What the server does know: who is in which chat, when they connected, from which device. We keep the minimum, we hand over only what we must. The messages themselves we cannot hand over, because we don't have them in readable form.

Sorry, officer. That's the architecture.

We operate in Russia, under Russian law. If we need to register locally, we do. When a lawful request comes in, we cooperate.

The point is, our architecture means we can't see what you write either. End-to-end encryption, keys on your devices only, the server holds only a sealed ciphertext. Nobody reads it, not us, not the requester.

What the server does know: who is in which chat, when they connected, from which device. We keep the minimum, we hand over only what we must. The messages themselves we cannot hand over, because we don't have them in readable form.

Sorry, officer. That's the architecture.

How the encryption works

Start with your own.

Sergei M.online
  • Finally. Good to have you.

  • Let me show you.

  • Calling.

Sergei M.Incoming call…
Answer

Calls go through when others go silent. TLS 443. No UDP.

Enter my code

Roadmap
Svoi: messaging for trusted circles — Svoi