> For the complete documentation index, see [llms.txt](https://docs.brewfather.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brewfather.app/legal/3rd-party-licenses.md).

# 3rd Party Licenses

Third-party and open-source software notices for Brewfather.

**Last updated: 15 October 2026**

{% hint style="info" %}
**In short.** This summary is not part of this page and is not binding. If it differs from the full text below, the full text applies.

* Brewfather includes third-party and open-source software. Their notices and licences are in the [third-party licence notice](https://web.brewfather.app/3rdpartylicenses.txt).
  {% endhint %}

Brewfather includes third-party and open-source software. Applicable copyright notices and licence texts are available in the current [third-party licence notice](https://web.brewfather.app/3rdpartylicenses.txt).

The notice is provided for attribution and licence compliance. A third-party licence may grant rights in the relevant component in addition to the Brewfather [Terms of Service](/legal/tos.md); those component-specific rights are not restricted by the Brewfather Terms.

Mobile builds may also display notices within the application or through the operating system or app-store materials. If you believe a required notice is missing or the linked notice is unavailable, contact <hello@brewfather.app>.

**Warpkode AS** (*aksjeselskap*) · Registered in *Foretaksregisteret* · Organisation no. 921 463 146 MVA · Head office: Florø, Norway\
Revision: 20261015


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.brewfather.app/legal/3rd-party-licenses.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.