TeamHub

Resources

Everything needed to check what the rest of this site says.

The pages before this one are written for somebody deciding. This one is for somebody verifying. Nothing here is behind a form.

Install and evaluate

RequirementsNextcloud 33 to 35, PHP 8.1 to 8.5. No additional infrastructure, no separate database, no outbound connectivity.
InstallFrom the Nextcloud App Store, like any other application.
Current version4.13.0. On the App Store since 20 April 2026.
LicenceBase application under AGPL-3.0. Gated modules under a commercial licence.
TrialOne full 30-day trial per instance, requested by e-mail from the License tab in the TeamHub admin settings.
Huub, the TeamHub digital assistant, looking through binoculars.

Huub says: verify it

Don’t take the marketing page on trust. Check the requirements, source, documentation and legal terms below. TeamHub is designed to be inspectable before you install it.

Documentation and source

Documentation

Installation, configuration, permission boundaries, administrator guide and the integration API.

Source code

The full application on GitHub, under AGPL-3.0.

Issue tracker

Bugs and feature requests, in public, where they stay visible.

Documentation Source on GitHub Issue tracker App Store listing

Commercial and legal documents

Published in full, so they can be read before anybody asks for a quotation rather than after.

Checking a claim on this site

Anything on these pages about defaults, labels or permission boundaries is checked against the application source before it is published, and the application decides who is right. If you find something here that the product contradicts, tell us and we will change the page rather than argue with you: sales@doekworks.eu.

A machine-readable summary of the product, for search engines and assistants, is published at llms.txt.

Something the documentation does not answer?

Technical questions about fit, scale or deployment are welcome, and usually get a quicker answer than a search does.

Discuss your use caseRead the FAQ

Open original