License
Fileship is open source. Since version 6.6.0, the Fileship server is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0) with one additional term: the "Powered by Fileship" notice on the login page stays. Fileship for Windows, the browser extension and the shared packages are licensed under MIT.
The full details are in LICENSING.md. This page answers the common questions. It is not legal advice; the license texts decide.
Can I self-host Fileship for free?
Yes. For yourself, your family, your community or your company, with as many users as you like. Nothing changes for self-hosting compared with earlier versions, except that the login page shows a small "Powered by Fileship" link.
Can I change Fileship?
Yes. If you let other people use your changed version over a network, you must offer them its complete source code under the AGPL-3.0, for example with a link to your repository. Changes you only use yourself do not need to be published.
Can I use Fileship commercially?
Yes, including running it inside your company and offering it as a paid service to others. A service must keep the "Powered by Fileship" notice, publish its changes to Fileship as described above, and use a name of its own: it may say that it is based on Fileship, but it may not call itself Fileship. See the trademark policy.
Can I remove the "Powered by Fileship" notice?
Not under the AGPL-3.0: the notice is the one additional term of the license. You can restyle and translate it. If you need to remove it, or want to use Fileship in a closed-source product, ask about a commercial license at [email protected].
What about Fileship 6.5 and earlier?
They were released under the MIT License and stay under it. The AGPL-3.0 applies to Fileship 6.6.0 and later.
Why did Fileship change its license?
The AGPL-3.0 keeps Fileship open source while making sure that anyone who builds a service on it shares their improvements and credits the project, instead of turning it into a closed product.
Why do I have to sign a CLA to contribute?
The Contributor License Agreement lets the project offer the commercial license next to the AGPL-3.0, and change its license in the future if needed. You keep the copyright of your contribution, and every contribution that ships in a release stays available under that release's open-source license.