# Licensing

> The Telesphorepo server is AGPL-3.0 and the publisher clients are MIT. What that means if you run it, build on it or publish with it.

Source: https://docs.telesphorepo.com/reference/licensing/

Telesphorepo has two licenses. The server is **AGPL-3.0**. The publisher clients are **MIT**.

| Part                              | License                                                    | Where                                                                                                |
| --------------------------------- | ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
| Server, web UI and CLI            | [GNU AGPL-3.0](https://www.gnu.org/licenses/agpl-3.0.html) | [github.com/Telesphorepo/Telesphorepo](https://github.com/Telesphorepo/Telesphorepo), file `LICENSE` |
| Gradle plugin and Maven extension | [MIT](https://opensource.org/license/mit)                  | [github.com/Telesphorepo/clients](https://github.com/Telesphorepo/clients), file `LICENSE`           |

The clients are the Gradle settings plugin and the Maven extension, plugin and client library. They live in the separate `clients` repository and have their own releases. See [Gradle plugin](/publishing/gradle-plugin/) and [Maven extension](/publishing/maven-extension/).

> Note
>
> This page explains the licenses in plain words. It is not legal advice. The license texts are the final authority. If your company needs certainty, ask your lawyer.

## If you run the server

You can run Telesphorepo for any purpose, including inside a company and for a paid service. You do not pay a fee and you do not need to ask.

Your artifacts are yours. Storing a Maven library, a `.deb` or a tarball on the server does not put it under the AGPL. The license covers the server code, not the files you host with it.

## If you change the server

The AGPL has one rule that the plain GPL does not have. If you modify the server and let other people use it over a network, you must offer those users the source code of your modified version. The same license applies to that source.

This applies to a modified server that outside users reach, for example a hosted service. If you run an unmodified server, you have nothing to publish beyond a pointer to the source, which is the GitHub repository.

If you only change settings or use the API, you did not modify the server. Configuration is not a code change.

## If you build a program that talks to the server

A script, a CI job or a tool that calls the HTTP API or downloads artifacts from the server is a separate program. Using the API does not make your program fall under the AGPL.

If you copy server code into your own program, the AGPL applies to the result.

## If you publish with the clients

The Gradle plugin and the Maven extension use the MIT license. You can use them in any project, open source or closed, and you can copy or change them. Keep the copyright notice and the license text with any copy you distribute.

The MIT license lets you add the clients to a closed-source build with no obligation to publish your build.

## Where the clients come from

For now the clients are published to the Telesphoreo Nexus repository. Gradle Plugin Portal and Maven Central are coming soon.

| Repository | URL                                                                |
| ---------- | ------------------------------------------------------------------ |
| Releases   | `https://nexus.telesphoreo.me/repository/gradle-plugins-releases/` |
| Snapshots  | `https://nexus.telesphoreo.me/repository/gradle-plugins-snapshots` |

The group and plugin ID are `com.telesphorepo`.

## Dependencies

The server and the clients depend on open source libraries that carry their own licenses. Check the lock files and build files in each repository if you need the full list.