> 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/beta.md).

# Public Beta

Learn how Brewfather public beta access works and check whether a beta is currently available.

Brewfather 3.1.0 completed public testing and was released on **31 August 2026**. There is currently no active public beta.

{% hint style="info" %}
See the [Changelog](/changelog.md) for the stable 3.1.0 features, improvements, and fixes.
{% endhint %}

## When a public beta is available

Public betas let you try selected features and improvements before they move to the stable release. New beta availability is announced through the [Brewfather Discord](https://discord.gg/WwBXhrUVeK).

Beta software can contain bugs, incomplete behavior, or changes that are not yet reflected in the stable app. A beta uses your regular Brewfather account and data, so changes you make are live account changes. [Export a current backup](/data-safety.md#id-1-export-a-full-backup-web) before testing workflows that modify important data.

## Use a beta on the web

When a web beta is announced:

1. Open [beta.brewfather.app](https://beta.brewfather.app/).
2. Sign in with your regular Brewfather account.
3. Confirm the app version from **About** when reporting an issue.
4. To return to the stable web app, open [web.brewfather.app](https://web.brewfather.app/).

The web beta updates automatically. If a newly announced change does not appear, use **Settings → Application → Reload Application**.

## Join an iOS or Android beta

Mobile beta access and current installation instructions are coordinated through the Brewfather Discord community:

1. Join the [Brewfather Discord](https://discord.gg/WwBXhrUVeK).
2. Open the **#join-public-beta** channel when beta enrollment is announced.
3. Follow the current instructions for the iOS or Android beta.
4. Install the beta, sign in, and confirm the version from **About** before testing.

Use **#join-public-beta** for current enrollment information because TestFlight and Google Play testing instructions can change. After joining an active public beta, follow **#public-beta-updates** for the latest beta changelog.

## Send beta feedback

When a public beta is active, send feedback to <hello@brewfather.app> or through the [Brewfather Discord](https://discord.gg/WwBXhrUVeK):

* Use **#public-beta-chat** for beta discussion and questions.
* Use **#public-beta-feedback** to report beta feedback and issues.

When sending feedback, include:

* Brewfather version and build from **About**
* Web, iOS, or Android and the device/browser version
* Steps that reproduce the problem
* What you expected and what happened instead
* Screenshots or a short screen recording when useful

Do not post API keys, passwords, payment details, or private recipe/account data in a public Discord channel.


---

# 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/beta.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.