Compatibility
Applies to: SimpleTwo 0.9.x · Checked: 19.10.2026
1. Client
| Platform | Minimum | Notes |
|---|---|---|
| iOS | 18.0 | distributed through TestFlight |
| Android | 8.0 (API 26) | built against API 36; from Google Play or as an APK |
| macOS | 14.0 | its own build, updates itself |
| Web | current browsers (ES2020) | Chrome, Safari, Firefox, Edge |
| Windows | — | there is no separate build; use the web client |
| Linux | — | no separate build |
The Android minimum is not arbitrary: API 26 is where always-on VPN and modern notifications exist, and without them a call on a locked screen does not behave like a call.
The web client does not do everything
The browser gives you messaging and joining a meeting, including as an external guest. End-to-end encrypted chats and the corporate tunnel are app features: both need keys and a network stack a browser tab does not have.
2. Server roles
| What | Supported | Notes |
|---|---|---|
| OS | Linux with systemd (verified on Ubuntu 24.04 LTS) | the agent installs services through systemd, packages through apt, the boundary through ufw or firewalld |
OS for the s3 role | FreeBSD on ZFS | chosen deliberately: an object is a file there, and a ZFS snapshot is therefore a backup of the objects |
| Postgres | 16 | one database per service; an existing cluster can be used instead |
| Redis | 7 | distribution package; required from the second sfu node onwards and from the second mcu node |
| Architecture | x86-64 (amd64) only — for Linux and FreeBSD alike | the server side is built for x86-64 only; the coordinator refuses to enrol a host of any other architecture |
A firewall on the host is not a recommendation: installing the s3 role on a host without
ufw, firewalld or pf is refused.
3. External systems
| System | How it connects | Notes |
|---|---|---|
| Identity providers | OpenID Connect; SAML 2.0 — through identity | verified with Entra ID, ADFS, Keycloak, Okta, Google; ID-token signatures are RS256. identity takes several providers at once and can use the provider's own second factor |
| Active Directory | through ADFS or Entra ID; directly over LDAP — people into the coordinator, groups into identity | the manager is carried by a pair of claims |
| Your applications | OpenID Connect, SAML 2.0, LDAP, SCIM 2.0 — from the identity role | identity is the sign-in provider for the organisation's applications; SAML is sign-in started by the application (SP-initiated), LDAP is read-only |
| Mail programs | JMAP; sending — SMTP on 587/465 with an app password | IMAP and POP3 are not supported, see section 4. Printers and systems that cannot sign in with a password send through the devices connector on mx |
| Calendars | ICS subscription (webcal://) and CalDAV | Apple Calendar, Thunderbird, anything speaking CalDAV |
| Meeting rooms | SIP terminals: Poly Trio, Poly, Cisco — Opus and H.264 | the mcu role, see Meeting rooms and SIP terminals |
| Object storage | S3-compatible | the s3 role or external storage |
| Model providers | Anthropic API and OpenAI-compatible | including local vLLM and Ollama |
| Push | APNs and FCM | keys are configured by the administrator |
4. What is not supported
Listed separately because these are the questions that get asked:
- EWS, MAPI and ActiveSync are not supported and will not be — Exchange's mail protocols are not part of this product;
- IMAP and POP3 are not supported and will not be: our clients' mail goes over JMAP;
- SMB for files is not supported and will not be; WebDAV and a web surface for files are not built yet;
- SAML directly is not spoken by the coordinator: an IdP that only speaks SAML connects
through
identity(or through ADFS and Entra ID).identityis itself a SAML provider for your applications too; - ES256 for ID-token signatures is not accepted yet — RS256 only;
- Windows and Linux client builds do not exist;
- ARM on the server (aarch64: Kunpeng, Baikal-M, Graviton and the like) is not supported yet: the server roles are built for x86-64 only, and the join script stops on an ARM host with "only x86-64 is supported". The client apps are not affected — iOS, Android and macOS on Apple Silicon work as before.