Help decide what gets built first

MSP design partners

Managed service providers who would host Office Unbound for customers. Design partners review tenant management, delegated technician access, migration workflows and update control against how they run customers today, and test early builds against real operating practice.

Useful to tell us: customers and seats managed, current platforms, hosting model, the tools you already use (for example a PSA or documentation platform such as clientst0r).

Early adopters

Organizations that would run Office Unbound themselves or through a provider. Early adopters say which workloads matter most and are contacted when a component reaches early testing that matches.

Useful to tell us: the workloads you depend on, what you run today, and whether a Microsoft 365 or Google Workspace migration is likely.

Developers

Integration, the web interface, desktop and mobile clients, migration connectors and the management API. Registered developers hear first when the repository opens and where help is needed.

Useful to tell us: languages and areas you know, and how much time you could give.

Technical contributors

Not all contributions are code. Security review, documentation, accessibility testing, packaging for deployment and translation all matter, and some can start before the repository opens through design review.

Useful to tell us: what you would review or write, and any relevant experience.

Sponsors

Organizations that want to fund development, test infrastructure or a specific workstream such as migration tooling or security review.