What SimpleTwo is
Applies to: SimpleTwo 0.9.x · Checked: 16.10.2026
SimpleTwo is a unified communications platform that runs in your own infrastructure. One delivery instead of several vendors: messaging, calls and conferences with external participants, meeting rooms, mail, files, a secure access network, bots and AI agents.
It ships as a base and products on top of it: the base (the console, the directory with the calendar, Messaging — chats, calls and conferences) is free with SimpleOne; Messaging Plus, Secure Access, Mail and Drive come separately. "The core" is the base's figurative name. There are no editions across the platform. What is in each and which roles it needs: Products.
Developed and owned by SimpleOne, part of ITG Corporation.
Every page has an English version — the user guide, administration, deployment, the reference section and the API. Nothing here is a machine translation: the pages were written in English from the same sources as the Russian ones, and the generated pages (the endpoint reference, the error catalogue, the environment variables) are emitted in both languages by the same generator, so the two cannot drift apart.
Russian remains the source language: a new page appears there first, and a check in CI refuses to let the English locale quietly grow a hole.
What it is made of
| Role | What it does | Product |
|---|---|---|
coordinator — the control plane | access policy and permissions, sign-in through your identity provider, the node registry, the admin console, certificate issuance. It installs every other role through its agents on the hosts | base |
messaging — chats | chats, threads, files in conversations, call signalling — the product server | base |
directory — the directory with the calendar | people, groups and the organisation's contacts, SCIM; calendars, ICS subscriptions, CalDAV, personal and team address books (CardDAV); sign-in of local accounts and guests and the broker to the organisation's identity provider | base |
postgres — the database | every role has its own database on one instance. Installed as a role, or point it at your own cluster | base, infrastructure |
sfu — media server | conference media: it forwards streams to participants rather than mixing them, and scales as a pool of nodes | base |
turn | a relay for clients behind strict NAT | base |
recorder | meeting recording into your storage | Messaging Plus |
redis — the bus | coordination of the sfu and mcu nodes and the recording jobs; needed from the second node | base and Messaging Plus, infrastructure |
mcu | your Poly and Cisco meeting-room terminals in meetings, with voice, video and presentation | Messaging Plus |
pstn — the PSTN gateway | the telephone network over a carrier's SIP trunks. See telephony | Messaging Plus |
support | the support bot: requests, the knowledge base, AI-assisted answers | Messaging Plus |
gateway | VPN nodes, one per location: access to the corporate network and egress in a chosen country | Secure Access |
mail and mx | mail: mailboxes, search and JMAP for the clients — mail; the edge in the DMZ — mx: receiving and sending internet mail, DKIM, checks and filters. See mail | |
drive | files: a personal space for everyone and a space per group. See files | Drive |
s3 — object storage | attachments, avatars, meeting recordings, mail and files. Installed as a role, or point it at storage you already run | infrastructure |
monitoring | metrics, logs and traces from every host; its interface opens from the console | an option for any installation |
| SimpleTwo Connect | the client: iOS, Android, macOS and web. One name on every platform; on Windows people use the web client — there is no separate build in 0.9.x | every product |
Where to start
- Choose what to install — Products: the base and each product.
- Install it — the deployment manual (Russian): one service,
coordinator, is installed by hand, and it installs every other role through its agents. You put the agent on a host yourself with the console's join command, or let the coordinator do it over SSH; from then on the agent pulls whatever its role needs from the coordinator. - Understand the topology and the numbers — Architecture and Sizing.
- Write an integration — API overview and the client–server protocol, which is a published contract rather than a description of current behaviour.
How this documentation is arranged
Three sections, three different readers:
| Section | For whom |
|---|---|
| For users | the person who works in SimpleTwo every day: chats and threads, calls and conferences, meetings, their own assistants, skills and kudos, the tunnel, installing the app |
| For administrators | the person who deploys and configures: topology and installation, sign-in through a corporate IdP, guests and federation, calls, telephony, the access network, client distribution, bots and AI, and the reference section |
| For developers | the person integrating from outside: the API overview, the protocol contract, error codes, the endpoint reference |
The same mechanism is described twice on purpose. A user needs to know what "the floor" is and how to raise a hand; an administrator needs to know that two media nodes without a shared bus are two islands, and that a call which connects with no sound is an address the client cannot route to.
Every article starts with the version it applies to and the date it was checked. The product
ships as 0.9.x branches, and an article without that line is one nobody can tell is current.