---
title: Integrate LibreDB Studio with Tiger Cloud | Tiger Data Docs
description: Query, browse, and administer your database from a web-based, multi-engine database editor
---

[LibreDB Studio](https://github.com/libredb/libredb-studio) is an open source, web-based database editor that runs as a self-hosted server or a local CLI (`npx @libredb/studio`), with a query editor, an object browser, and a monitoring dashboard shared across PostgreSQL and more than a dozen other database engines.

This page explains how to integrate LibreDB Studio with your Tiger Cloud service.

In this integration guide, you:

- Connect LibreDB Studio to your service over the standard PostgreSQL wire protocol.
- Browse your schema and run queries from the LibreDB Studio editor.
- Review what LibreDB Studio's object browser and monitoring dashboard show for a hypertable, and where those views diverge from a plain table.

## Prerequisites for this integration guide

To follow these steps, you'll need:

- A [Tiger Cloud service](/docs/get-started/quickstart/create-service/index.md).

  These steps use Tiger Cloud, but the same approach applies to a [self-hosted TimescaleDB](/docs/get-started/choose-your-path/install-timescaledb/index.md) instance.

* Your [connection details](/docs/integrate/find-connection-details/index.md).

- LibreDB Studio installed. Run it locally with `npx @libredb/studio`, or deploy the [Docker image or Helm chart](https://github.com/libredb/libredb-studio#-quick-start) to a server you control.

## Connect LibreDB Studio to your service

To connect to Tiger Cloud:

1. **Start LibreDB Studio and sign in**

   Open LibreDB Studio in your browser and sign in with the admin or user account configured for your instance. On the first local run, `npx @libredb/studio` prints a generated admin email and password in the terminal.

   An admin account lands on the `Admin Dashboard`. Click `Editor` in the top-right corner to open the query editor.

2. **Open the connection dialog**

   Click the `+` button next to the LibreDB Studio logo in the sidebar to open the `New Connection` dialog.

3. **Select PostgreSQL as the connection type**

   LibreDB Studio has no separate TimescaleDB connection type: TimescaleDB is a PostgreSQL extension, so the `PostgreSQL` driver is the correct choice and connects over the same wire protocol.

4. **Configure the connection**

   Fill in the connection name and use your [connection details](/docs/integrate/find-connection-details/index.md) for the host, port, database name, username, and password. Enable `SSL / TLS` if your service requires it.

5. **Click `Test Connection`, then `Establish Connection`**

   A successful test reports the round-trip time, for example `Connected successfully (26ms)`. `Establish Connection` saves the connection and opens it in the editor, with the object browser populated on the left.

   ![LibreDB Studio query editor right after establishing the connection, with the object browser on the left showing the public schema expanded to the sensor\_readings table and its four columns and types; no chunks or internal TimescaleDB schemas are listed](/docs/_astro/integrations-libredb-studio-object-browser.RZTc1LIP_pgcTm.webp)

You have successfully integrated LibreDB Studio with Tiger Cloud.

## Verify the integration

1. **Run a query against a hypertable**

   In the query editor, run a `SELECT` against one of your hypertables, for example:

   ```
   SELECT sensor_id, count(*) AS readings
   FROM sensor_readings
   WHERE time > now() - interval '7 days'
   GROUP BY sensor_id
   ORDER BY sensor_id;
   ```

   The results grid renders the rows, with the row count and execution time shown above the grid.

   ![LibreDB Studio query editor with the grouped aggregate query against the sensor\_readings hypertable and an 11-row results grid below it showing a reading count per sensor, with the row count and execution time shown above the grid](/docs/_astro/integrations-libredb-studio-query-results.Bfdr00bR_ZSjQrY.webp)

2. **Browse the schema**

   In the object browser, expand your schema, then `Tables`. Your hypertable is listed as a single table, the same way a regular table is: its chunks and the internal `_timescaledb_*` schemas are not shown. Expand the hypertable to see its columns and their types. Indexes aren't listed in the tree; their size appears in the `Index` column of the `Monitoring` > `Tables` view.

   To find a table by name, press `Cmd+K` on macOS or `Ctrl+K` on Linux and Windows to open the command palette, and type the name. The object browser has no search box of its own.

## Limitations

TimescaleDB stores a hypertable's rows in per-interval child tables (chunks) and keeps the parent table itself empty. LibreDB Studio's object browser and monitoring dashboard read table size and row count from PostgreSQL's own catalog statistics, the same source a plain PostgreSQL client would use, and that catalog describes the empty parent, not the chunks underneath it. Measured against a hypertable with 8,641 real rows across 31 chunks:

- **The `Table Statistics` view reads 0 rows and 0 bytes for the hypertable.** Open it from `Monitoring` > `Tables`. The index is not affected: it reports a non-zero size. The hypertable's row count next to its name in the object browser is also missing until the table is analyzed, and reads 0 afterwards.

  ![LibreDB Studio's Monitoring > Tables view filtered to sensor\_readings, with Table Statistics showing 0 rows and 0 bytes for the hypertable while its index correctly shows 8192 bytes](/docs/_astro/integrations-libredb-studio-hypertable-zero-rows.C78pG2dA_1eEkqH.webp)

- **A direct query or `Profile Table` reports the true row count.** A `SELECT count(*)` run in the query editor returns the real number. So does `Profile Table`, in the `⋮` menu next to the table's name in the object browser, because it runs its own scan rather than reading catalog statistics.

  ![LibreDB Studio's Data Profiler dialog for public.sensor\_readings reporting the correct Total Rows count of 8,641 across 4 columns](/docs/_astro/integrations-libredb-studio-profile-table-correct-count.CF4Sg-to_1fjzoB.webp)

- **The overview and monitoring pages show the PostgreSQL version, not the TimescaleDB extension version.** A service running `TimescaleDB 2.30.2 on PostgreSQL 17.11` shows only the `PostgreSQL 17.11` version string.

None of this blocks querying or browsing a hypertable, an ordinary `SELECT` returns real data and real row counts either way, but the passive statistics shown in the browser and dashboard undercount a hypertable specifically. Query directly (`count(*)`, `hypertable_size()`, or `Profile Table`) when you need an accurate number.

## Next steps

[DBeaver](/docs/integrate/query-administration/dbeaver/index.md)

[Manage and query your data with a cross-platform SQL editor and administration tool](/docs/integrate/query-administration/dbeaver/index.md)

[pgAdmin](/docs/integrate/query-administration/pgadmin/index.md)

[Query, visualize, and manage your database with an open-source administration tool](/docs/integrate/query-administration/pgadmin/index.md)

[Understand hypertables](/docs/learn/hypertables/understand-hypertables/index.md)

[Learn how TimescaleDB partitions a hypertable into chunks](/docs/learn/hypertables/understand-hypertables/index.md)