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

# Plaato

Brewfather integration for Plaato Airlock and Plaato Keg devices (discontinued hardware).

{% hint style="warning" %}
Plaato has been discontinued by the manufacturer. Brewfather still supports Plaato Airlock and Plaato Keg, and existing Plaato data in your batches remains accessible.

For Plaato Airlock, the recommended replacement for the original Plaato app/cloud flow is [`open-plaato-keg`](https://github.com/DarkJaeger/open-plaato-keg). See the [Airlock](/integrations/plaato/airlock.md) guide for the current Brewfather setup flow.

At the moment, Brewfather only supports **Plaato Airlock** through the `open-plaato-keg` workflow. We are looking into adding **Plaato Keg** support through `open-plaato-keg` as well.
{% endhint %}

Plaato produced two brewing devices that integrate with Brewfather:

* [**Plaato Airlock**](/integrations/plaato/airlock.md) -- A smart airlock that tracks fermentation activity by measuring CO2 bubbles, temperature, and estimated gravity. After Plaato discontinued the original service, the recommended workflow is to route the Airlock through `open-plaato-keg` and then forward it to Brewfather.
* [**Plaato Keg**](/integrations/plaato/keg.md) -- A smart keg management device that tracks remaining volume, temperature, and other keg status data. Configured via auth keys on the Devices page in Brewfather.

Both Plaato integrations are available from **Settings > Power-ups**. Since Plaato hardware has been discontinued, setup and long-term support depend on third-party replacements such as `open-plaato-keg`.

{% content-ref url="/pages/-LzmopLmDqfWXD5\_PuA8" %}
[Keg](/integrations/plaato/keg.md)
{% endcontent-ref %}

{% content-ref url="/pages/-LaXatcTmPB4Sb8ankvE" %}
[Airlock](/integrations/plaato/airlock.md)
{% endcontent-ref %}

## What is open-plaato-keg?

[`open-plaato-keg`](https://github.com/DarkJaeger/open-plaato-keg) is a reverse-engineered replacement for the original Plaato cloud service. It lets you keep using Plaato hardware locally after the Plaato cloud shutdown by routing device data through your own server instead of the Plaato app backend.

According to the upstream project, it supports:

* **Plaato Keg**
* **Plaato Airlock**
* **Generic airlocks** that can `POST` to its API
* An **Android companion app**

It can then expose that data through its own web UI and forward it to other systems, including **Brewfather**.

For Brewfather specifically, the current `open-plaato-keg` workflow on these docs only covers **Plaato Airlock**. **Plaato Keg** support through `open-plaato-keg` is something we are currently looking into.

## Related docs

* [Plaato Airlock](/integrations/plaato/airlock.md)
* [Plaato Keg](/integrations/plaato/keg.md)
* [Devices](/devices.md)


---

# 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/integrations/plaato.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.