> For the complete documentation index, see [llms.txt](https://docs.heisenware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heisenware.com/app-builder/build-backend/function-explorer/storage.md).

# Storage

Heisenware provides a unified approach to data. Whether you use our built-in storage or connect your own, you use the same Functional blocks to manage your data.

## Relational storage (SQL)

For structured data like user profiles, orders, or inventory, we use the [relational database](/app-builder/build-backend/function-explorer/storage/relational-database.md) class.

* **Internal (managed)**: Every account comes with a pre-configured instance called `internal-postgres`. You can start dragging CRUD Functions onto the canvas immediately. No further setup is required.
* **External (connect)**: If you have an existing SQL database (PostgreSQL, MySQL, SQLite, MSSQL), you simply use the `create` Function of the same class to establish a connection.

## Time series storage (IoT)

For high-frequency data like sensor readings or machine telemetry, we use the [time series database](/app-builder/build-backend/function-explorer/storage/timeseries-database.md) class.

* **Internal (managed)**: Use the [Recorder](/app-builder/build-backend/recorder.md) right in your flow to store millions of data points with zero configuration and the `internal-influxdb` to read and query that data.
* **External (connect)**: Use the `create` Function to point the logic toward your own InfluxDB server.

## In-memory storage

For temporary data that only needs to live during a session (and doesn't need to be saved to a disk), use our specialized utility classes:

* [**Data store**](/app-builder/build-backend/function-explorer/storage/data-store.md): For simple state management.
* [**Circular buffer**](/app-builder/build-backend/function-explorer/storage/circular-buffer.md): For "rolling" data (e.g., the last 100 values for a live chart).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.heisenware.com/app-builder/build-backend/function-explorer/storage.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.