When you're choosing open source collaboration software to self-host, the licence usually gets a two-second glance: "it's open source, fine." For a chat server, file platform or team workspace you plan to run for years, the licence tells you three things that matter:

  1. What you have to do if you modify it.
  2. What the vendor can hold back for paying customers.
  3. How likely it is that the terms will change later.

This is a practical explainer, not legal advice. Read the actual licence files linked below before you commit.

The three models in one table

Comparison table: Permissive (MIT/Apache), Copyleft (AGPL-3.0), Open core

These overlap. A project can be AGPL and open core, or MIT with a proprietary directory. Treat these as patterns to look for, not boxes.

What does "permissive" actually give you?

MIT and Apache-2.0 let you use, modify and redistribute the code, including inside proprietary products, as long as you keep the notices. Apache-2.0 adds an explicit patent grant.

Zulip is a clean example: the server is Apache-2.0. You can patch it, run your patched version for any number of users and never publish a line.

Permissive doesn't automatically mean everything is open, though. Rocket.Chat's LICENSE puts the code outside its ee/ directories under MIT, and the code inside them under a separate licence. Same repo, two regimes. Always read the licence file, not only the badge.

The catch with permissive licences: nothing stops someone (including a large cloud provider) from taking the code, building a hosted product and contributing nothing back. That pressure is what pushed several vendors towards copyleft or source-available licences.

What does the AGPL's network clause mean for self-hosters?

The GPL's obligations kick in when you distribute software. If you only run modified GPL code on your own server, you're not distributing anything, so there's nothing to share. The AGPL closes that gap.

Section 13 of the AGPL-3.0 says that if you modify the program, your modified version must offer the source to all users interacting with it remotely over a network.

In practice, for someone self-hosting a collaboration tool:

  • Running it unmodified: no extra obligation. Install, configure, use.
  • Changing config, themes or settings through the supported mechanisms: generally not a "modified version". Check the project's guidance, because some vendors spell this out.
  • Patching the source and letting people use it: you must make your modified source available to those users. That includes colleagues, clients and guests using the instance, not only the public.
  • Building a commercial hosted service on a patched fork: the same rule applies, which is exactly why vendors choose AGPL.

Collaboration tools under AGPL-3.0 include Nextcloud server, CryptPad, the Seafile server core and Drumee (source under the drumee organisation on GitHub), a files, chat, tasks and meetings workspace. For a typical self-hoster who runs these unmodified, the AGPL behaves almost exactly like a permissive licence. It only bites when you fork and expose the fork to users.

Why do some AGPL projects also sell a commercial licence?

Because the AGPL plus a CLA enables dual licensing. If one company holds the rights to all the code, it can offer the same code under AGPL to everyone and under a commercial licence to customers who don't want copyleft obligations.

Matrix's reference server is the best-documented case. In November 2023 Element moved Synapse from Apache-2.0 to AGPL-3.0, forking it into new repositories under its own GitHub organisation. Element was open about the mechanics:

  • Contributors now sign a CLA that gives Element the right to license contributions commercially.
  • Element says the sole purpose of the CLA is dual licensing, not a move to a non-OSI licence.
  • Element Server Suite customers get an enterprise licence that "supplants the AGPL requirements".

Today the Synapse README lists exactly that: AGPL-3.0 or an Element commercial licence.

CryptPad's README follows a similar pattern: AGPL for everyone, and a contact address for proprietary commercial use.

What this means for you: the AGPL code you run stays AGPL, and a published release can't be taken back. The CLA is still worth noticing, because it gives the company room to set licence terms for future code.

What is open core, and how do you spot feature-gating?

Open core means the core product is open source, but some features exist only in a commercial edition. For collaboration tools the gated features are predictable: SSO/SAML, LDAP, compliance exports, high availability, clustering and advanced admin roles.

Mattermost has one of the more layered models. Its LICENSE.txt says source you compile yourself is AGPL-3.0, compiled builds from Mattermost, Inc. are MIT, and admin tools and config files are Apache-2.0. On top of that, the editions page describes:

  • Team Edition: MIT-licensed, aimed at teams under 250 activated users, with SSO being removed.
  • Enterprise Edition: a commercial binary. Without a key it runs in a free, limited mode called Entry, and a subscription unlocks the rest.

Seafile draws the line in its manual, where features such as SAML 2.0, clustering and virus scanning are marked Pro. Pro is free for up to three users. Larger teams need a paid licence.

Nextcloud takes the opposite position. Its FAQ says the Enterprise build comes from the same open source codebase and the value is support, hardening and configuration, not closed features.

Neither approach is wrong. Open core funds development. But compare the free edition with your requirements, not the feature page. If you need SSO for 300 people, the open core edition may not be the product you're evaluating.

Can the licence change after you've deployed?

Yes, for future versions. Never retroactively for code already released under an open licence. The well-documented cases:

The pattern: relicensing is much easier when one company owns all the copyright, usually through a CLA. Projects that take contributions under the DCO with no copyright assignment are harder to relicense, because every contributor would have to agree.

Forks are your insurance. A permissive or AGPL codebase can always be forked from its last open release. Whether a fork actually survives depends on who's willing to maintain it, which is why OpenTofu and Valkey launched with named corporate backers.

Which licence model should you pick?

There's no universally right answer, so here are some rules of thumb.

Which licence model fits how you'll use it

  • You'll run it unmodified and want maximum freedom: permissive (Zulip) or AGPL (Nextcloud, Synapse, CryptPad, Drumee) are close to equivalent for you. Choose on features and operations.
  • You plan to patch the server and offer it to clients: AGPL means publishing those patches. Fine for many teams, a blocker for some. Permissive avoids it.
  • You're building a product on top of it: permissive, or an AGPL project's commercial licence.
  • You need SSO, compliance or HA: check whether these are in the free edition. In open-core tools they often aren't.
  • You worry about future relicensing: look for a foundation or neutral governance, DCO instead of a CLA, or a project with enough independent contributors that a fork would be viable.

A quick checklist before you deploy:

  1. Open the LICENSE file and look for multiple licences or ee//enterprise/ directories.
  2. Read the editions page and list which of your must-haves need a key.
  3. Check CONTRIBUTING.md for a CLA or DCO.
  4. Look at the project's licence history.

Where Drumee fits

For transparency: Drumee is AGPL-3.0 and offers both hosted plans and a self-hosted "Sovereign Node" sold through sales. Its scope is a workspace where files, chat, tasks and meetings sit together. Compared with the others here, its ecosystem is younger and smaller, its chat is less deep than Synapse, Zulip or Mattermost, and its task features are lighter than a dedicated project tool. The licence section above applies to it like any other AGPL project.

Files, chat and meetings in one workspace

If you're also comparing self-hosted collaboration platforms on features rather than licence, there's a longer overview on the Drumee blog.

Disclosure: this post is written by the Drumee team, and Drumee is one of the tools covered. We've tried to keep it fair. Corrections welcome in the comments.