Open-source workspace platform

Your workspace. Your infrastructure. Your rules.

Office Unbound is an open-source workspace platform in development, designed to bring email, calendars, files, documents, collaboration, and administration together without forcing businesses into a single cloud provider.

Planned as an alternative to Microsoft 365 and Google Workspace, with guided migration from both.

Proposed interface concept Not released · example data · subject to change

Home: today’s meetings, the messages that need you, recent files and notifications — a starting point, not a dashboard. Open this concept

Status: Phase 1, architecture and evaluation. Nothing on this site is released yet; screens are design concepts. How status is reported

See it as designed

One workspace, four ways to run it.

People work in the workspace. Organizations, managed service providers and infrastructure operators each get their own console, with separate access. These are proposed interface concepts, not released software.

  • For everyone The workspace Mail, calendar, files and documents from one start page. Proposed concept · not released
  • For organization administrators Organization admin center Users, groups, domains, security policies and updates. Proposed concept · not released
  • For managed service providers MSP Control Center Every customer organization, with access scoped per technician. Proposed concept · not released
  • For infrastructure operators Infrastructure Control Server Hosts, services, alerts and capacity across the platform. Proposed concept · not released

Why Office Unbound?

Your business. Your data. Your infrastructure. Your rules.

Modern collaboration shouldn’t require surrendering control of your business data, infrastructure decisions, update schedules or long-term technology strategy to a single provider. Office Unbound is being designed as a genuinely open-source, self-hosted or MSP-hosted alternative that puts businesses and service providers back in control.

Who it is for · Who it is not for · For MSPs

For businesses: why switch?

  • Data ownershipChoose where mail, files and records live: your servers, a private cloud or an MSP’s.
  • Vendor independenceLess reliance on one cloud provider’s pricing, roadmap and terms.
  • Hosting flexibilityRun it on your own infrastructure, or have an MSP run it for you.
  • Open-source transparencyPlanned: public source code, dependency inventories and published security fixes that anyone can inspect. The repository is not published yet.
  • Predictable operationsYou or your provider set maintenance windows and deployment policies.
  • Privacy and governanceYou decide access, retention, backups and how data is handled.
  • Business continuityBackup, restore testing, retention and disaster recovery under your control, run by your IT team or MSP.
  • Familiar productivityMail, calendars, contacts, documents, files, chat, meetings and calling.
  • Migration assistancePlanned discovery, readiness assessment, migration, validation and rollback.
  • PortabilityOpen protocols and exportable data lower the cost of leaving, including leaving Office Unbound.
Who holds what
  1. Your organizationUsers, data, policies, retention, who has access
  2. Your IT team or your MSPServers or private cloud, backups and restore tests, retention, disaster recovery, monitoring, updates on your schedule
  3. The Office Unbound projectOpen-source code, with signed releases, SBOMs and security advisories planned

More control means more responsibility

Whoever hosts Office Unbound, your IT team or your MSP, takes on the patching, monitoring, capacity and support that a SaaS provider would otherwise carry, and is responsible for backups, restore testing, retention and disaster recovery. The Infrastructure Control Server is designed to reduce that work, not remove it.

Who it is being built for Who it is not for

For MSPs: why offer it?

Build a managed collaboration service you control, not only resell one. See the full MSP opportunity.

  • A differentiated serviceA managed collaboration platform of your own, not a resold subscription.
  • Recurring revenue opportunitiesHosting, management, migration and support as ongoing services.
  • Infrastructure you controlCustomers run on hosting you choose, not entirely on another vendor’s cloud.
  • Room to improve marginsEfficient use of shared infrastructure may help margins. No savings are promised.
  • Multi-tenant administrationEvery customer an isolated tenant, managed from one console.
  • APIs for provisioning and billingDesigned for automated provisioning, usage reporting and billing integration.
  • Fits your MSP toolsPlanned integration with clientst0r and other PSA, RMM and documentation tools.
  • Infrastructure Control ServerHealth, monitoring, alerting, updates and capacity planning in one place.
  • Flexible customer environmentsServices, quotas and policies configured per customer.
  • Guided customer migrationsAssessment and staged moves from Microsoft 365 and Google Workspace.
  • Optional security servicesAdd services such as MailThreatZero for customers who want them.
  • Closer customer relationshipsYou run the service your customers depend on, directly.
A recurring managed service
  1. Assess and migrateProject revenue to bring a customer over
  2. HostMonthly hosting on infrastructure you run
  3. Manage and secureAdministration, updates, monitoring, optional security services
  4. Support and reportHelp desk and regular customer reports

Renewed each term; customers add services as they grow.

Your own offering, around an open-source core

MSPs can build commercial services on the open-source core: hosting, management, migration and support. Those offerings are subject to the licenses of Office Unbound and of the components deployed, for example a commercial document-engine edition where a customer needs one.

Explore MSP administration Revenue and operating costs

From vendor dependency to customer control

Microsoft 365 and Google Workspace already offer regional data controls, integrations, strong security features and data export. This compares deployment models, not product quality: Office Unbound is a different approach, not a universally better one.

TopicTypical SaaS-only modelOffice Unbound approach (planned)
Where it runs In the provider’s cloud, often with regional data options Self-hosted, private cloud or MSP-hosted
Update timing Set by the provider, with some admin controls Maintenance windows and rollout rings you or your MSP set
Dependencies Proprietary services and APIs, with export tools Open standards: IMAP, SMTP, CalDAV, CardDAV, WebDAV, Matrix
Infrastructure visibility Service health pages; the infrastructure itself is not visible Direct visibility into hosts, services and capacity
Operations Run by the provider Configurable: in-house, MSP-managed or shared
Migration Often planned with separate third-party tools Assessment and migration tooling planned as part of the platform
Service packages Plans and bundles defined by the provider Service offerings an MSP defines for its customers
How a migration is planned
  1. Discover
  2. Assess
  3. Map and plan waves
  4. Transfer
  5. Verify
  6. Cut over, with rollback

The staged migration process

How updates are planned to be controlled
  1. Signed release and advisory
  2. Review
  3. Schedule a window
  4. Pilot ring
  5. Broad rollout
  6. Roll back if needed

Planned release signing, SBOMs and update control

Common questions

Why would I switch from Microsoft 365?

You may not need to. Microsoft 365 is mature and capable. Office Unbound is for organizations that want their data on infrastructure they choose, updates on their schedule and software they can inspect, and that accept running it themselves or paying an MSP to. It is in development, so for now the realistic step is to follow the project or take part in testing. Compared workload by workload.

Can I keep using Outlook or other mail clients?

Standard IMAP, SMTP, CalDAV and CardDAV access is planned, so clients such as Thunderbird, Apple Mail and phone mail apps are intended to connect. Outlook for Windows and macOS is not claimed: that depends on which mail server is selected. No client has been tested yet. Mail clients and sign-in.

What will it cost?

Office Unbound’s own code is intended to be open source, with no license fee for it; its license has not been selected yet. Running it still costs hosting, administration and support, either in-house or within an MSP’s service price. Some deployments also choose commercial component editions or vendor support, such as a supported document engine. No pricing has been set, and no savings are promised. Costs and licensing.

Is the software actually open source?

That is a founding principle: the source code for Office Unbound’s own components is intended to be public, with signed releases and software bills of materials planned from the first release. None of these exist yet: the public repository has not been published. Some components it is designed to use also sell commercial editions alongside their open-source ones. Why open source.

Who maintains updates and security?

The project plans to publish releases and security advisories; none have been published yet. Whoever hosts a deployment, your IT team or your MSP, applies them on the schedule they set, with planned rollout rings and rollback. Critical security fixes are not meant to be deferred indefinitely. Security controls.

Can an MSP host and manage everything?

That is a primary design goal: multi-tenant administration, customer isolation, delegated technician access, and the Infrastructure Control Server for operations, while each customer keeps its own admin center and audit log. These capabilities are planned, not built. For managed service providers.

How will migrations work?

In planned stages: read-only discovery, an assessment of what moves directly, needs conversion or is not supported, identity mapping and waves, staged transfer, verification, then cutover with a rollback window. How long it takes depends on the organization; figures shown on this site are illustrative. Migration overview.

Is Office Unbound available today?

No. The project is in Phase 1, architecture and evaluation. Nothing has been released, and the screens on this site are design concepts. You can register interest, become an MSP design partner or contribute. Roadmap.

Workspace concepts

Designed to feel familiar on the first day.

Simple for users, powerful for administrators. People coming from Outlook and Microsoft 365 should find their way without training. Select an application to see its design concept.

Mail that works the way people already work.

Folders, a message list and a reading pane; shared mailboxes beside personal ones; the calendar and directory one click away. Standard IMAP, SMTP, CalDAV and CardDAV underneath, so phones and existing mail apps can connect, designed to use modern sign-in or per-device app passwords rather than password-only legacy authentication.

In place of Exchange Online, Outlook on the web, Gmail

Business email & calendar

Proposed interface concept Not released · example data · subject to change

Webmail with personal and shared mailboxes, folders, flags, attachments and a reading pane. Open this concept

Documents, spreadsheets and presentations in the browser.

Word-processing, spreadsheet and presentation files opened from storage and edited together, with comments, version history and sharing that follows the same permissions as the file.

In place of Word, Excel, PowerPoint, Google Docs, Sheets, Slides

Documents & office applications

Proposed interface concept Not released · example data · subject to change

One frame — title, sharing, comments, version history — around an editor provided by Collabora Online or ONLYOFFICE Docs, whichever the deployment selects. Open this concept

Personal files and team libraries, synced to the desktop.

One place for a person’s own files and their teams’ shared storage, with sharing, permissions, version history and a desktop client that keeps chosen folders available offline.

In place of OneDrive, SharePoint document libraries, Google Drive

Files, storage & sync

Proposed interface concept Not released · example data · subject to change

Personal files and team libraries with sharing, sync state, permissions and versions in one place. Open this concept

Teams, channels and threads on an open standard.

Channels for each team, threaded replies, direct messages and files shared in the conversation, built on the Matrix protocol so the data model is documented and portable.

In place of Microsoft Teams chat, Google Chat

Team chat & collaboration

Proposed interface concept Not released · example data · subject to change

Team channels with threads, files, mentions and scheduled meetings in the conversation. Open this concept

Meetings scheduled from the calendar, joined from the browser.

Video and audio meetings with screen sharing, a participant list and in-meeting chat, scheduled from the same calendar as everything else.

In place of Teams meetings, Google Meet

Meetings & calling

Proposed interface concept Not released · example data · subject to change

A meeting with a shared screen, raised hands and chat, in the dark meeting theme. Open this concept

One console for users, policies and updates.

Users, groups, roles and MFA in one directory; mail, storage and security policy in one place; service health and pending updates with maintenance windows the organization sets.

In place of Microsoft 365 admin center, Google Admin console

Identity & administration

Proposed interface concept Not released · example data · subject to change

One admin console for users, MFA, storage, service health and update approval. Open this concept

All workspace and administration concepts · Design principles

Infrastructure operations

More than a productivity suite. Operations designed in from the start.

Self-hosted productivity usually means assembling separate tools to watch, patch, recover and grow the servers underneath it. Office Unbound is planned with its own operations layer, the Infrastructure Control Server, designed to monitor services, detect failures, carry out approved recovery actions, manage updates and forecast capacity for the infrastructure it runs on.

Planned, and built on established open-source components. It does not remove the need for administrators; it gives them one place to work.

Proposed interface concept Not released · example data · subject to change

The deployment on one screen: hosts, VMs, containers, service health, open incidents, maintenance and a capacity estimate. Open this concept

Infrastructure operations

Built for managed service providers

Many customer organizations, one console.

Many small and mid-sized businesses buy productivity services through an MSP. Office Unbound is being designed so a provider can deliver them from infrastructure it chooses: isolated customer tenants, delegated technician access with audit, migration projects run as a service, and updates scheduled per customer. A provisioning and management API is planned, including integration with clientst0r.

  • Separate, isolated customer tenants
  • Role-based technician access, every action audited
  • Migration assessments as a service
  • Rollout rings and maintenance windows per customer
  • Monitoring, patching and alerting for every customer environment
  • Planned clientst0r integration and management API

Proposed interface concept Not released · example data · subject to change

Many customers, each a separate tenant, operated from one console with scoped technician access. Open this concept

Migration from Microsoft 365 and Google Workspace

Migration without guesswork.

Migration starts with a read-only assessment that inventories the source and states what will transfer, what needs conversion and what will not, before a single mailbox moves. Each stage has a validation step and an operator approval before the next.

What can be moved depends on the source platform’s APIs, the customer’s licenses and the workloads in use. The assessment reports this per tenant.

  1. DiscoverConnect read-only and inventory the tenant.
  2. AssessCompatibility, volumes, blockers.
  3. PlanMap users and groups; set batches.
  4. PilotDry run with a small group.
  5. TransferStaged batches, then delta sync.
  6. VerifyCompare counts and content.
  7. Cut overApprove, change DNS, keep a rollback point.

Proposed interface concept Not released · example data · subject to change

Assessment before anything moves: what was found, what converts, what does not, and in what order. Open this concept

Documents

Your choice of document engine.

Office Unbound is designed to work with two established open-source editing engines through one integration layer. Users see the same file browser, sharing, comments and version history whichever engine a deployment selects.

Collabora Online

Based on LibreOffice. Integrates through the WOPI protocol; ODF formats native, with OOXML support.

Under evaluation

ONLYOFFICE Docs

Built around Office Open XML (docx, xlsx, pptx). Integrates through its Document Server API, with WOPI support.

Under evaluation

The integration layer

Common handling of file access, permissions, sessions, locking, saving and versions, so an administrator can select the engine per deployment and change it later through a planned, controlled cutover.

Planned

Neither engine is recommended over the other: licensing, editions and format needs differ between organizations. Document engines: comparison and architecture

Open and transparent

Claims you can check.

Open source does not make software secure by itself. It makes the claims checkable. Office Unbound is designed to publish its source, sign every release, publish a software bill of materials with each one, and handle vulnerability reports through coordinated disclosure. The first four are planned and do not exist yet: no repository or release has been published.

Security and transparency · Report a vulnerability

Public source
Planned: the code that runs the platform, readable by anyone evaluating it.
Signed releases
Planned: release artifacts signed so administrators can verify what they install.
Bills of materials
Planned: an SBOM listing every component and version in each release.
Advisories
Planned: security advisories with affected versions and fixes.
Disclosure
Available now: a private route for reporting vulnerabilities. A formal disclosure policy is planned.

Current project status

Every capability carries one of seven labels.

A label moves forward only with evidence: public code for Implemented, published test results for Tested, a supported release for Production-ready. Today nothing is past In development.

  1. ConceptIdea or design direction
  2. Under evaluationBeing assessed
  3. PlannedOn the roadmap
  4. In developmentBeing worked on
  5. ImplementedCode in a public repository
  6. TestedPassed published tests
  7. Production-readySupported release
Where things stand
AreaDetailStatus
Phase 1Architecture and component evaluationIn development
ComponentsKeycloak, grommunio or Stalwart, Nextcloud, Collabora Online or ONLYOFFICE, Matrix, LiveKitUnder evaluation
ApplicationsThe workspace applications above, with identity and administrationPlanned
MigrationAssessment and readiness engine, then executionPlanned
Infrastructure operationsControl server: monitoring, alerting, recovery, patching, capacityPlanned
InterfaceWorkspace and administration screens on this siteConcept

The roadmap, phase by phase

Get involved

Help decide what gets built first.

The project is at the stage where outside input changes the design. Each route below reaches the project directly; you are contacted about what you asked for, and nothing else.

  • MSP design partners

    Shape tenant management, delegated access and migration workflows around how you run customers today.

    Become a design partner
  • Early adopters

    Name the workloads that matter most and test early builds when they match what you need.

    Register for early testing
  • Developers

    Integration, interface, clients and migration connectors, once the source is published.

    Developer interest
  • Technical contributors

    Security review, documentation, testing and packaging, at whatever depth suits you.

    Ways to contribute
  • Sponsors

    Fund development, infrastructure or a specific workstream, such as migration tooling.

    Sponsoring the project
Share