Resources · Updates

Project updates

Dated notes on what has happened in Office Unbound development: decisions made, components evaluated, and changes to the plan. Newest first.

Project status One entry so far. Updates are added when something has actually happened, not on a schedule.

All updates

Each entry is dated and is not rewritten after publication. Corrections are added as later entries.

· Phase 1

Website published; the project is in architecture and evaluation

This website is the first public description of Office Unbound: what it is meant to be, how it is meant to work, and what order it is being built in. Nothing is available to install yet, and no public code repository has been published. Every capability on this site carries a status label that says so.

The project is in Phase 1, architecture and evaluation. That phase is about making the decisions the rest of the platform depends on, before code is written for it.

  • Technology selection. Candidate components for each workload are being assessed: Keycloak for identity, grommunio/Gromox and Stalwart for mail, Nextcloud for files and sync, Collabora Online and ONLYOFFICE Docs for document editing, Matrix with Element for chat, LiveKit and MatrixRTC for meetings, and FreeSWITCH for telephony. None has been selected yet.
  • Licensing review. Each candidate’s license, commercial editions and trademark rules are being reviewed against what the platform needs to do. The current findings are on the technology and licensing page.
  • Security architecture. The tenant-isolation model, administrative boundaries and update-control approach are being designed first, so multi-tenant features are not retrofitted later.
  • Integration design. How the components will share one identity, one interface and one administration layer. The current picture is on the target architecture page.
  • Migration discovery architecture. What the planned assessment engine needs to read from Microsoft 365 and Google Workspace, with which permissions, and how it will report compatibility.

Proxmox VE with Linux virtual machines has been set as the initial deployment target.

How to follow along. The most direct way is to register for early access and say which workloads you would test first. Registrants are contacted when a component they care about reaches early testing, and when the roadmap changes in a way that affects them. MSPs can use the MSP partnership inquiry, and developers the developer interest form. Future updates will also appear on this page.

What gets an update

An entry is written when something changes that a reader planning around Office Unbound would want to know about. Updates are not written to show activity.

  • A component is selected, or rejected, with the reason
  • A licensing finding that changes what can be built or shipped
  • A roadmap change: phases reordered, items moved or dropped
  • The public repository is published
  • A component reaches early testing
  • A correction to something said earlier on this site
No newsletter

Submitting a form on this site does not add you to a mailing list. Registrants are contacted about the interests they told us about, and this page is the public record. See the privacy notice.

Be told when something changes

Register for early access and choose the workloads that matter to you. We write when a relevant component reaches early testing.