A team workspace for Nextcloud
Give every team one clear place to work.
TeamHub connects people, decisions, projects and the Nextcloud apps you already use in one shared team workspace, running inside the Nextcloud your organisation already controls.
- One home per team
- Runs in your Nextcloud
- Extends, does not replace
- Open source, actively built
The problem
Your teams have the tools. What they lack is shared context.
Nothing on this list is a software gap. Every one of them is what happens when the software has no idea which team is responsible for what.
- Decisions lose their reasoning. The call was made in a chat thread in March. The decision survived; why it was made did not.
- Work is spread across applications. The board is in Deck, the contract is in Files, the deadline is in someone's calendar, and no screen shows all three.
- Responsibilities depend on who remembers. When the person who held it in their head moves on, the context goes with them.
- Managers find out at the meeting. Status meetings exist because project status is not visible anywhere else, which is an expensive way to read a number.
- Employees check several places. Being useful in three teams means opening three sets of applications every morning to find out what changed.
- Internal services are hard to find. Asking for more storage, a new laptop or a contract review means first working out which team is responsible, which means understanding the organisation chart.
The argument is not that organisations lack tools. It is that the tools have nowhere to agree.
The approach
Organise work around the team responsible for it.
A Nextcloud Team is a membership and permissions construct: it says who belongs. TeamHub gives that team somewhere to work.
- Every team gets one home. A page carrying that team's messages, decisions, presence, work and the applications it uses. New members find their context by reading it rather than by being briefed.
- Existing applications stay the source of truth. Talk owns the conversation, Files owns the document, Calendar owns the event, Deck owns the card. TeamHub shows them in the context of the responsible team.
- Missing structure gets built, not duplicated. Where Nextcloud already meets a need, TeamHub surfaces it. Where nothing meets it, TeamHub builds it. Decisions, presence and a personal queue across teams exist because nothing else provides them.
- Setting a team up is one form. Naming a team provisions its chat, its folder, its calendar, its board and the modules it needs, so a rollout does not stall on forty teams created by hand.
What changes
Three levels, and each one answers the level above it.
An organisation buys the top level. It keeps the product because of the bottom one.
For the organisation
See how work is progressing.
Project health, milestones and decision history are readable without calling a meeting to collect them. Responsibility is attached to a team rather than to a memory.
For a team
Give every team a shared home.
One page instead of six applications. The conversation, the documents, the board and the decisions in the context of the team that owns them.
For a person
Let the work come to the person.
My Work lists everything waiting on somebody, across every team they are in. What’s new shows what changed while they were away. Not another place to check: a place that removes the checking.
Decisions
Chat is where decisions get made, and the worst place to keep them.
A conversation is the right tool for reaching a decision and the wrong one for holding it. Six months later somebody always asks the same question: why did we do it this way?
A decision in TeamHub carries the proposal, the impact, the category it was filed under, the person who approved it, the reason they gave, the work it is linked to and the document it came from. Filing it under Budget puts it in front of the finance lead without anybody having to chase.
The history is append-only. A settled question is superseded rather than overwritten, so the record of what was decided in March survives the decision that replaced it in September. An audit trail you can edit is not an audit trail.
It is not a workflow engine, and it is not an approval matrix. A decision has a proposer, a category, an approver and a reason. That constraint is the feature: it is the reason people actually file one.
Internal services
Employees should not have to learn the organisation chart to ask for something.
Asking for more storage, a contract review or a new starter account normally begins with a harder question: whose job is this?
- People pick what they need. A catalogue of what the organisation actually offers, written in the words the requester would use.
- The responsible team is visible. Each service names the team that answers it, so the request goes to a desk rather than to whoever was asked last time.
- The expected response time is on the card. Before the request is sent, not after somebody chases it.
- Every request follows the same route. Submitted, claimed, answered, closed. The requester can see which step it is on.
A service team holds a bundle of services and answers requests from the rest of the organisation. A request lands in that team's queue and in the requester's own My Work, so neither side has to remember to look.
The point is not the form. It is that the requester never needs to know which department owns the thing they are asking for.
How it fits
TeamHub extends Nextcloud. It does not rebuild it.
The fastest way to stall a rollout is to ask people to move their work into a new container. Nothing moves.
- A Deck card stays a Deck card. It also appears on the team's page, and in My Work for whoever it is assigned to. Acting on it there writes back to Deck.
- Talk stays the conversation. TeamHub surfaces the team's room rather than building a second chat for people to miss messages in.
- Files stays the document. The team folder appears in the team, as itself, not as a copy.
- Calendar stays the event. Presence writes each person's working location to their own Nextcloud calendar.
TeamHub is an independent third-party Nextcloud app, installed from the App Store into the Nextcloud an organisation already runs. There is no hosted TeamHub and no separate platform, by design.
Team content stays inside the Nextcloud environment the organisation controls. The open-source base is published under AGPL-3.0, so the code can be read, kept and audited independently of any commercial relationship.
Adoption
The question underneath every other question: will people use it?
A replacement nobody adopts is how work leaks back out into private chats and personal cloud folders. The personal layer exists to remove that risk, which is why it is the last argument on this page rather than the first.
- My Work lists everything waiting on one person, gathered from every team they belong to, with the reason each item is on the list. A decision needing their approval, a review, a task, a service request. Acting on a row writes straight back to the Deck card, the file or the decision it came from.
- What’s new shows what changed while they were away, across every team at once, so Monday morning is one screen rather than six.
Neither is another place to check. Both exist to remove the checking.
Where it lands
Four ways organisations put TeamHub to work.
Team coordination
Give standing teams one page: their conversation, their documents, their decisions and who is in this week.
Read the use caseInternal services
Publish what the organisation offers, route requests to the team that answers them, and show the expected response time.
Read the use caseProject delivery
Phases, milestones, budget and a health signal that surfaces slippage when it happens rather than at the review.
Read the use caseMicrosoft 365 replacement
Nextcloud covers mail, files, documents and boards. This is the row it does not cover on its own.
Read the use caseWhat it costs
Free to develop with. Licensed to run.
The product is the same in every pack. The pack sets the seat band and the billing, nothing else. Community is a genuine full base app under AGPL-3.0, with no seat limit, and in exchange it carries in-app prompts, TeamHub branding, one anonymous daily usage aggregate and the gated modules locked.
Starter
1 – 50 seats
€450
per year
Business
51 – 100 seats
€850
per year
Enterprise
101 seats and above
From €6.96
per seat, per year
All prices exclude VAT and any applicable taxes. One seat is one unique active Nextcloud account that belongs to at least one Team on the licensed instance. Somebody in five teams counts once. An account in no team counts nothing.
Give your teams a clearer place to work.
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.