Connections

Connections is where Saiku Cloud learns how to reach your data. You fill in the connection details once — URL, username, password — and from then on the Schema designer can sample tables, your cubes can read your warehouse, and your queries return live results without you re-entering anything.

Supported warehouses

All seven dialects below are fully bundled in the engine container. Each has its own walkthrough — click the dialect you want to connect:

PostgreSQL Any Postgres 12+, including Aurora / Cloud SQL / Supabase. SSL recommended.

MySQL / MariaDB MySQL 5.7+ or MariaDB 10+. Single driver (MariaDB Connector/J) speaks both wires.

ClickHouse ClickHouse Cloud or self-hosted. HTTP-based JDBC, no native-protocol headache.

Snowflake Account, warehouse, database, schema. Username + password or key-pair auth.

Google BigQuery Service-account JSON key. No password — auth lives in the JDBC URL.

MotherDuck Cloud DuckDB. Token-based auth; one JDBC driver covers MotherDuck and local DuckDB files.

DuckDB (file) Local DuckDB files uploaded via the Files dashboard. Same driver as MotherDuck.

Want to test Saiku Cloud before connecting your warehouse?

Each guide includes a FoodMart download — the classic OLAP sample dataset (5 years of fictional grocery-store sales, ~10 MB on disk, 37 tables) pre-packaged for that dialect. Load it into your test instance and follow the Sign up & first cube walkthrough end-to-end in under an hour. No warehouse migration required.

The connect flow (any dialect)

1. Click Add connection and pick your dialect.

2. Fill in the JDBC URL, username, and password (or per-dialect auth — see your dialect’s guide). Each field has a placeholder showing the expected shape.

3. Click Test connection. Saiku Cloud opens a short-timeout connection from our servers (egress IP 87.99.153.244), runs a SELECT 1, and reports back. Common problems get plain-English labels: “auth failed”, “host unreachable”, “database not found”, “timeout”.

4. Once the test passes, the Save button activates. Click it and the connection appears in the list.

Caution

Re-enter the password to save. Once you’ve tested a connection, we don’t send the password back to your browser — leaving it sitting in the page is a small but real security risk. So the test form and the save form each ask for the password separately. Type or paste it twice per save.

Allowlisting our IP

If your warehouse sits behind a firewall, add 87.99.153.244 to the allowlist. All connections from Saiku Cloud to your warehouse come from that one IP address.

What we store and what we don’t

Your password is encrypted before it lands in our database, using a key we keep separate from the database itself. The plaintext only exists for a few milliseconds at a time, when we’re actively opening a connection to your warehouse. Once the connection’s done, it’s gone. Even if somebody had a full copy of our database, your password would be unreadable without the encryption key.

For the broader picture, see Tenant isolation.

Editing and deleting

Click a connection name to edit the non-password fields. To change the password, re-enter it in the test step and re-save. Click the trash icon to delete — deletion is idempotent, so a stale refresh clicking twice won’t 404.

Related

• Schema designer — uses your connections to profile tables.
• Files — upload data directly when you don’t have a warehouse handy.
• FoodMart sample datasets — pre-packaged test data for every supported dialect.