Governments
The collaborative suite for an entire civil service, on national soil.
A single platform operated by the state, in its own data center. Ministries that administer their environment independently. Staff who keep their tools and their habits.
Our references since 2011
CNPS · ANINF · Customs
CNPS on BlueMind, ANINF and Ivorian Customs on Zimbra: major public-sector accounts that entrusted us with the deployment and maintenance of their mail systems.
What a government gains with Oworks.
Its data at home
Mail, calendars, conversations and documents stay in the national data center, beyond the reach of foreign laws.
A common foundation
One platform, one directory and security rules shared by every administration, instead of dozens of disparate mail systems.
Autonomy for the ministries
Each ministry’s IT department manages its staff, its domains and its services without depending on the others.
Spending under control
No per-seat license paid to a foreign vendor: a subscription, and value that stays in the national economy.
Governance
The government sets the framework. Each ministry organizes itself within it.
- The central IT department runs the platform, creates the organizations, and sets the security rules and the quotas.
- Each ministry’s IT department manages its domains, its accounts, its groups and its brand, and delegates to its directorates.
- The government directory lets a staff member find and invite a staff member from another ministry, without opening either one’s data to the other.
The government’s Oworks platformCentral IT department · government directory
Each ministry’s IT department in its own console.
Its staff, its groups and its organizational units, synchronized with its directory or created by hand. It sees nothing of the other ministries.
In the government cloud
On your Kubernetes, in your national data center.
Oworks installs on the government’s Kubernetes, in the national data centers opening across the continent. The government owns the infrastructure, the data and the keys; the platform grows by adding servers.
- Over 100,000 concurrent users
- Redundancy and failover to a second site
- Monitoring handed over to your teams
From your existing systems
A gradual switchover, with no big bang.
- Zimbra: Oworks and your Zimbra share the same domain; accounts switch over at your own pace, or Oworks takes over your instances.
- Microsoft 365 or Exchange: federation with Microsoft Entra ID, coexistence for as long as needed, then mailbox migration in batches.
- Outlook: staff keep it, natively connected.
Your console
Ministry staff
The ministry IT department sees only its own organization: neither the staff nor the content of other ministries.
Our approach
From workshop to knowledge transfer.
Our integration engineers run the project with your IT department, from Abidjan and on site.
- 01WorkshopYour administrations, your existing systems, your target governance.
- 02ArchitectureSizing, sites, security and switchover plan.
- 03PilotA first ministry in production, measured and adjusted.
- 04RolloutThe administrations join the platform in waves.
- 05TransferYour teams trained to run it; operations delegated if you prefer.
No licenses. A subscription, and a team for your own specific needs.
Each year
The subscription
- Updates and new versions
- Security fixes
- Integrated and tested suite
- Support with service level commitments
Per-user pricing, with volume discounts, or a flat rate for a government.
One time
Onboarding
- Architecture and installation
- Integration with the directory and the information system
- Mailbox migration
- Administrator training
Custom
Our R&D team
- Electronic signature
- Correspondence management (GEC)
- Internal social network
- AI hosted on your premises: email summaries and translation
Modules in preparation, available on request.
Let’s arrange a workshop with your IT department.
Half a day to map your administrations and your existing systems, and to design the target platform.