---
title: "Does Fluxer have a CLA?"
description: "No. Fluxer has no CLA, and you keep the copyright in your contributions. Each commit needs a Developer Certificate of Origin sign-off under the AGPL."
url: "https://canary.fluxer.com/help/cla"
language: "en"
last_updated: "2026-11-01"
category: "About Fluxer"
---

> Index of Fluxer's official pages for AI agents: https://canary.fluxer.com/llms.txt
> Links to Fluxer pages go to their Markdown versions when they have one. For other Fluxer help, policy or blog links, remove any #section part and add .md to the end.

# Does Fluxer have a CLA?

No. Fluxer has no CLA, and you keep the copyright in your contributions. Each commit needs a Developer Certificate of Origin sign-off under the AGPL.

No. Fluxer doesn't ask contributors to sign a contributor license agreement (CLA), and you keep the copyright in your work. Fluxer is licensed under the [GNU AGPL, version 3.0 or later](https://github.com/fluxerapp/fluxer/blob/main/LICENSE), and your contributions are licensed under that same license.

Fluxer Platform AB can't relicense your work under any license other than the AGPL without your permission. The only exception is work sent before February 18, 2026 by contributors who signed the CLA that Fluxer had from January 5, 2026 until that day. Relicensing can't take the AGPL away from any version of Fluxer that has been published, and anyone can keep running and forking that code, as [the open source article](https://canary.fluxer.com/help/open-source.md) explains.

## What you agree to when you contribute

Each commit you send needs a [Developer Certificate of Origin](https://developercertificate.org) sign-off, which you add with `git commit -s`. The sign-off confirms that you have the right to submit your change under the AGPL. The [contributing guidelines](https://github.com/fluxerapp/fluxer/blob/main/.github/CONTRIBUTING.md) list what else a pull request needs.

## Why Fluxer had a CLA at first

When we opened fluxer.com to everyone on January 2, 2026, we didn't know yet whether Fluxer could fund itself. We wanted to keep the option of also offering Fluxer under a commercial license to organizations that couldn't follow the AGPL. To do that, we needed the right to relicense every contribution, so we added a CLA on January 5, 2026.

On February 9, 2026, a product decision by another chat app [changed Fluxer's scope overnight](https://canary.fluxer.com/blog/how-i-built-fluxer.md), and it became clear that Fluxer could fund itself without a second license. People on Reddit also said that the CLA asked too much of contributors, and Hampus removed it on February 18, 2026, about six weeks after it had been added.

---

Canonical page: https://canary.fluxer.com/help/cla

Last updated on November 1, 2026