Hosted Time-Series Database

The Collectu Hub provides fully managed, dedicated time-series database instances, allowing you to store and query your time-series data without operating your own database server.

Concept

Every instance is a dedicated database deployment, exclusively for you or your organization.

  • Each instance gets its own subdomain (e.g. <deployment_name>.tsdb.collectu.de) and is reachable on port 5432.
  • All connections are TLS encrypted.
  • You authenticate with your Collectu API access token as the password - there are no separate database passwords. Deleted tokens or removed organization members immediately lose access.

Getting Started

  1. Log in to your Collectu Hub profile and navigate to Hosted Time-series DB.
  2. Click Create Instance.
  3. Create an API access token under API Access Tokens (or use an existing one).
  4. Connect with any PostgreSQL client using the connection details shown in the instance table.

Connecting

Use the following connection parameters:

  • Host: the host shown in the instance table (e.g. <deployment_name>.tsdb.collectu.de)
  • Port: 5432
  • Database: collectu
  • Username: one of the generic roles admin, readwrite or read (see below)
  • Password: your API access token
  • SSL mode: verify-ca

Example with psql: psql "host=<deployment_name>.tsdb.collectu.de port=5432 dbname=collectu user=read password=<api access token> sslmode=verify-ca sslrootcert=/etc/ssl/certs/ca-certificates.crt"

Info
Use sslmode=verify-ca (validates the certificate chain). verify-full does not work, since the wildcard certificate does not cover the per-instance subdomains. Some clients (e.g. psql) additionally need an explicit root certificate store via sslrootcert; most tools (e.g. Grafana or JDBC based clients) use the system trust store automatically.

Roles

You connect as one of three generic database roles. The requested role is only granted if your API access token and (for organizations) your membership permissions allow it:

  • admin: owns the database. For the owner himself or organization admins with create, edit and delete permissions.
  • readwrite: full read and write access, can create tables and schemas. Requires create, edit and delete permissions.
  • read: read-only access (SELECT). Every valid token of the owner or an organization member.

Storage Limit

Every instance has a storage limit. The current usage and the limit are shown in the instance table of the Collectu Hub. Clicking an instance row additionally shows the schemas and tables of the database with their approximate number of rows.

Caution
If the storage limit of an instance is exceeded, you receive a message and the oldest data is deleted automatically until the size is sufficiently below the limit again. Make sure to regularly delete or downsample old data if you approach the limit.

Executing Queries

Besides connecting with a database client, you can execute SQL queries directly via the Collectu Hub API (POST /tsdb/query) - for example from scripts or the MCP integration. The same role mapping as for direct database connections applies.

Example queries:

  • List all schemas: SELECT schema_name FROM information_schema.schemata;
  • List all tables with their size: SELECT schemaname, relname, pg_size_pretty(pg_total_relation_size(relid)) FROM pg_catalog.pg_statio_user_tables;
  • List all hypertables: SELECT hypertable_schema, hypertable_name FROM timescaledb_information.hypertables;
  • Create a schema (requires the admin or readwrite role): CREATE SCHEMA sensors;
Previous
Vpn
Next
Introduction