Product
Industry-standard components. A single platform.
Oworks brings together Carbonio, Zimbra, Matrix, Meet, OpenCloud, OnlyOffice and Keycloak with Postfix and Rspamd for mail routing and filtering, into one suite, isolated per organization and ready for the scale of a state.
The architecture, layer by layer.
The applications rest on a common foundation: a single identity, isolated organizations, a single console. All of it runs on the Kubernetes you control.
1Access
- Browser
- Mobile apps
- Desktop app
- Outlook
- Standard clients
2Standard protocols
- HTTPS
- MAPI over HTTP
- EWS
- ActiveSync
- IMAP
- SMTP
- CalDAV
- CardDAV
- WebDAV
- Matrix
- WebRTC
3Applications
- WebmailCCarbonio
- Mail, calendar, contacts
- Chat
Matrix
Element - MeetingsMMeetLLiveKit
- Files
- Documents
OnlyOffice - Routing and antispam
Postfix
- BackupCCopy on the customer side
4Oworks foundation
Identity · Keycloak- Organizations and delegation
- Admin console
- Audit log
- Monitoring
5Infrastructure
Kubernetesstorage · backups
Where it runsGovernment data centerTelecom operatorCloud4Africa
Why these components.
Each one is open source, proven in production and maintained by a solid community or vendor. None of them locks you in.
| Use | Component | Why this choice | Standards |
|---|---|---|---|
| Webmail | Carbonio | The open source web interface from the Italian vendor Zextras, which we reworked for an experience close to Outlook. | HTTPS |
| Mail, calendar, contacts | Zimbra | A collaborative server proven at telecom operators and public administrations; run by our teams for years. | IMAP, SMTP, CalDAV, CardDAV |
| Mail routing | Postfix | The reference open source mail transfer server, known for its security and its performance under load. | SMTP, MTA-STS, DANE |
| Antispam and antivirus | Rspamd | Fast, tunable filtering of spam, phishing and dangerous attachments, with quarantine. | SPF, DKIM, DMARC, ARC |
| Backup | To be confirmed | Encrypted backup of the platform, with an optional copy in the customer’s object storage, which can be locked. | S3 |
| Chat | Matrix · Element | An open protocol chosen by the French government (Tchap) and the German army (BwMessenger); self-hosted servers that can be federated. | Matrix |
| Meetings | Meet from La Suite numérique | Developed by DINUM on LiveKit, under the MIT license; designed for large meetings, in the browser. | WebRTC |
| Files | OpenCloud | Derived from ownCloud Infinite Scale, co-developed with CERN and maintained by the Heinlein group; with no central database, it scales with the storage. | WebDAV |
| Documents | OnlyOffice | Real-time co-editing, faithful to Microsoft Office formats. | DOCX, XLSX, PPTX, ODF |
| Identity | Keycloak | The open source reference for identity management: single sign-on, second factor, directory federation. | OIDC, SAML, LDAP |
Multi-organization
Three levels of administration, airtight boundaries.
Each organization is an isolated space: its identities, its mailboxes, its rooms, its meetings and its files are visible to it alone. Its administrators have control over it and nothing else.
| Permission | PlatformCentral IT department or operator | OrganizationMinistry, customer | UnitDepartment, local office |
|---|---|---|---|
| Creates organizations and their quotas | Yes | No | No |
| Sets the common security rules | Yes | Can tighten them | No |
| Manages its mail domains | Validates | Yes | No |
| Creates accounts and groups | No | Yes | Within its scope |
| Sees user data | No | Per its own rules | No |
| Applies its branding | Default branding | Logo and color | No |
| Views the audit log | Platform | Its organization | Its unit |
Default distribution of permissions; it can be adjusted to the way each government is organized.
Platform level
The platform operator sees each organization, its subscription and its usage, never its content.
Organization level
Its administrators manage its users, its groups and its organizational units.
Platform level
3 organizations
At this level: subscriptions, quotas, and usage. No access to the organizations’ mailboxes, files, or conversations.
Organization level
Users
Scale and availability
Built for an entire civil service.
100,000+concurrent users
700,000users: the target sizing at national scale
Contractual uptimeTo be confirmed
- Each service scales on its ownMail, chat, meetings and files run in containers and scale independently, by adding servers.01
- No single point of failureEvery component is redundant; the platform can span several data centers for disaster recovery.02
- Continuously monitoredMetrics, logs and alerts from the whole platform, available to your operations teams.03
- Updates without interruptionNew versions roll out service by service, without stopping the suite.04
Security
Your rules, on your servers, with verifiable code.
- Strong authenticationSingle sign-on and second factor for every application.
- Encryption in transitTLS on all traffic, between users and between services.
- Audit logEvery administrative action logged and exportable.
- Mail protectionAntispam, antivirus and quarantine.
- Controlled sharingFile and calendar sharing rules set by the organization.
- Auditable codeEvery component is open source and can be audited by a third party.
Let’s talk about your project
Do your architects have questions?
Our engineers will walk you through the architecture, the sizing and the deployment plan for your infrastructure.
A no-obligation conversation with our teams.