Resources

The technical and project material behind the rest of this site: how the platform is designed to fit together, which components it builds on and under what licenses, what order it is being built in, and how to take part.

Project status The project is in Phase 1, architecture and evaluation. These pages describe design and intent, and are updated as decisions are made.

Technical

For architects, administrators and anyone evaluating whether the design holds up.

Target architecture: The five layers of the platform: access, identity, productivity services, administration and data. Covers how they map onto separated Linux virtual machines on Proxmox VE, and how one administration layer serves several tenants. Includes a conceptual architecture diagram.
Technology stack and licensing: Every open-source component under evaluation, what each one would do, its status, a link to the project, and a licensing review: the license of each component and the commercial, branding and network-use conditions that come with it.

The project

Where development stands and what comes next.

Development roadmap: Seven phases from architecture and evaluation to hardening, with the Migration Assessment & Readiness Engine as its own phase. Explains how status labels are decided and why no dates are published.
Project updates: Dated notes on what has actually happened: decisions, evaluations and changes to the plan. Entries are not rewritten after publication.
Frequently asked questions: Detailed answers on open source, hosting and Proxmox, Outlook and Office-file compatibility, SSO and MFA, tenant isolation, updates, MSP hosting, migration, cost and support.
Community and contributions: How to follow and contribute before and after the repository is published, the areas where help is planned, and how security issues will be reported and handled.

Not here yet

Some material you would expect to find in a project’s resources does not exist yet, because the project has not reached the point where it can exist honestly.

Installation and administration documentation, which needs software to document
A public source repository and issue tracker
Release notes, software bills of materials and security advisories, which come with the first releases
A security policy with a dedicated reporting address, to be published with the repository

Looking for migration material?

Migration has its own section: the overview, the planned assessment engine, the process, and a dedicated migration FAQ.

Something you need that isn’t here?

Tell us what you would need to evaluate Office Unbound. It shapes what gets documented first.