> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/changelog/january-2026/january30-cloud-release-notes.md).

# Jan 30, 2026 - Cloud

## New features

### Growth plan: usage and billing improvements

* Clearer billing breakdown showing your estimated charges, included usage, and overage costs broken down by logs, metrics, traces, and agents.
* Learn more about the Growth Plan [here](https://docs.bindplane.com/plans-and-pricing/growth).

### Generic REST API source

* Collect data from any REST API endpoint using a flexible, configurable source.
* [See more.](https://docs.bindplane.com/integrations/sources/generic-rest-api)

### New persistent queue storage options

* New storage backend (Pebble) for the persistent queue, improving reliability and performance for buffered data.
* [See more.](https://docs.bindplane.com/configuration/bindplane-otel-collector/persistent-queue)

### Permalinks

* Shareable deep links to specific resources and pages within Bindplane, making it easy to reference and share configurations with your team.

### Improved rollout options

* More granular control over how configuration changes are rolled out to agents.
* [See more.](https://docs.bindplane.com/core-concepts/rollouts)

<details>

<summary>Other Improvements</summary>

* Org admins now automatically receive project admin privileges. [See more.](https://docs.bindplane.com/feature-guides/role-based-access-control-rbac)
* Replaced modals with drawers on Agents, Configurations, and Fleets pages for a smoother, less disruptive workflow.
* SQL query source now properly handles null values. [See more.](https://docs.bindplane.com/integrations/sources/sql-query)

</details>


---

# 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.bindplane.com/changelog/january-2026/january30-cloud-release-notes.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.