Why TeamHub

Where does your team’s last decision actually live?

If the honest answer is a chat thread, a meeting somebody took notes in, or the memory of whoever was there, the problem is not that your organisation lacks tools. It is that the tools have no idea which team is responsible for what.

The starting point

A Nextcloud Team is a membership list.

It is a good one. It handles who belongs, what they can reach, and how permissions travel. What it does not do is give those people somewhere to work.

What a Team gives you today

A group you can share a folder with.
A group you can share a calendar with.
A group you can address in Talk.
A membership that other applications can read.

What it does not give you

A page that shows the state of that team's work.
A record of what the team decided, and why.
A way to see who is available next week.
A route into the team for people outside it.

Huub, the TeamHub digital assistant, presenting an idea.

Huub’s way of looking at it

Your tools are probably not the problem. The missing piece is the shared team context around them: who owns the work, what matters now and what was decided.

The rule

Where Nextcloud already meets the need, TeamHub surfaces it. Where nothing meets it, TeamHub builds it.

It never duplicates. That single rule answers the two objections this decision always raises.

Will this fragment our stack? No, because half of what follows is your existing applications shown in one place, as themselves.
Then what are we paying for? The other half, which nothing in the stack does at all.

The checklist

What an organisation needs from a team application.

Most evaluations end up working through a list like this one. Here it is with our answer to each, and the part of the product that delivers it, so both can be checked.

What you need	Our take	How it is delivered
Every team needs one place to work	One page per team, built on the Nextcloud Team you already have. Not a new container to migrate into	Team home, tab bar, widgets
Conversation has to stay with the team	Talk is the conversation. We surface it. We do not rebuild chat	Talk integration, plus Messages for announcements, questions and polls
Files belong to the team, not to a person	Files stays the source of truth. The team folder appears in the team, not as a copy	Files integration
Work has to be visible and trackable	Deck stays the source of truth for cards. We read across it and write actions back	Deck integration, Advanced Projects
Decisions have to outlive the people who made them	Chat is where decisions get made and the worst place to keep them	Decisions: propose, discuss, approve, with a recorded reason and a trail that cannot be edited
People need to know who is available	A status dot tells you about this second. An organisation needs to know about next Thursday	Presence: a working location per half day, a team week grid, synced to each person's calendar
Nobody should have to check six places	The work should come to the person rather than the person touring the channels	My Work and What’s new, across every team at once
Managers need to see whether a project is slipping	Status meetings exist because the status is not visible. Make it visible	Projects: phases, the Compass, milestones, a live health panel
People must be able to ask for things	Nobody should have to learn the organisation chart to request a laptop	Services: a catalogue, a responsible team, a response time
The organisation needs an audit trail	Governance should not depend on anybody remembering to write things down	Append-only decision history, the activity timeline, the compliance centre
Rolling it out has to be quick	Forty teams created by hand is how a migration stalls	Bulk creation from one CSV, with a dry run, and team templates
It has to bend to how you already work	Every organisation has one tool nobody will give up. Bring it in rather than fight it	Custom tabs for any URL, modules enabled per team, an open integration API

Most of that table is reassurance: yes, this covers what you expect. Three rows are the actual reason to choose it, because they are the ones nothing else in the stack does. Decisions with the reasoning kept. One personal queue across every team. Presence measured in half days rather than green dots.

Being clear about it

What TeamHub is not.

Naming the limits is the fastest way to be believed about the rest. Each of these gets asked, and an inconsistent answer costs more than a missing one.

Not a replacement for Deck or Talk

It reads across them and writes actions back to them. Nothing is copied, and turning TeamHub off leaves both exactly as they were.

Not the same as Nextcloud Teams

Nextcloud Teams is the membership feature. TeamHub is a separate application that gives those teams a workspace. The two are never interchangeable.

Not affiliated with Nextcloud GmbH

TeamHub is an independent third-party application published on the Nextcloud App Store, built by Doek Works.

Not available as a hosted service

There is no TeamHub platform to sign up to. It installs into the Nextcloud you already run, by design.

Not a workflow engine

A decision has a proposer, a category, an approver and a reason. That constraint is why people actually file one.

Not a full Microsoft 365 replacement on its own

It is one component of a Nextcloud-based replacement. The rest of the table is Nextcloud's work.

Continuity

Is it real, and will it still be here?

The strongest objection to a small open-source application is abandonment, and the only honest answer is a set of dates and a name.

Published since 20 April 2026 on the Nextcloud App Store, currently at version 4.13.0, shipping continuously.
The source is public under AGPL-3.0, on GitHub. If we stopped tomorrow, the base application would still be yours to run, read and fork.
There is a company behind it. Doek Works, registered in The Netherlands, Chamber of Commerce 42169291, with published terms and a named person on them.
Nothing depends on us staying online. The application never contacts us, for anything. No licence check, no seat count, no heartbeat.

Who is behind TeamHub

Recognise the problem?

Tell us how your teams are organised and what keeps getting lost between them. We will tell you honestly whether TeamHub is the right answer.

Discuss your use case See how it works