Skip to main content
Rafflesia Databases is an ordinary ClickHouse service. The REST API manages account-scoped credentials and release metadata; SQL, binds, schema inspection, joins, aggregation, and streaming use ClickHouse’s HTTPS interface directly.

Create a credential

Create a credential with POST /v1/sql-credentials. The password is returned only by create and rotate. Store it immediately; list responses never contain a password or verifier.
The response includes a username, one-time password, and a secret-free connection object:
Set the returned values in your secret manager:

Discover releases

The catalog is queryable before the first release exists and never requires ClickHouse’s internal FINAL modifier:
relation_releases.sql_backing is the exact immutable relation to put in a reproducible query. A current_sql_backing is an explicitly mutable convenience alias for exploration.

Python

HTTPS SQL

ClickHouse’s HTTP interface accepts SQL in the request body and can stream formats such as JSONEachRow, Arrow, Native, and Parquet:

Requel

Rafflesia is the provider; ClickHouse is the SQL dialect:
The DSN path must be the credential response’s default_database (production uses rafflesia_catalog; staging uses its own catalog database). The driver verifies the unqualified service view and its contract version before executing. A committed catalog.rafflesia.lock pins every released input and causes execution to refuse if its advertised bytes, schema, or SQL address move.

Access boundary

Each credential is a distinct ClickHouse user for attribution and quota accounting. The server enforces read-only queries, execution and memory limits, result and scan limits, concurrency, and an hourly quota. Credentials can read only the polished catalog and published release databases; raw ingest tables and private catalog records are not granted. Rotate with POST /v1/sql-credentials/{credential_id}/rotate and revoke with DELETE /v1/sql-credentials/{credential_id}.