Connections

Connections is where Saiku Cloud learns how to reach your data. You fill in the connection details once — host, database, 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.

Available today: PostgreSQL and MotherDuck (which also covers local DuckDB files via the same driver). Snowflake, BigQuery, and ClickHouse appear in the picker but are flagged as “driver not bundled” — the gateway has them wired but the engine container doesn’t bundle the drivers yet. Email support@saiku.bi to request — adding a new bundled driver is a quick change to the engine build, not a roadmap item.

The flow for an available dialect: fill in the connection details, click Test connection, save once it goes green.

Adding a connection

1. Click Add connection and pick your dialect.

2. Fill in the details — host, database, username, password, plus any dialect-specific fields like Snowflake’s warehouse name or BigQuery’s project ID. BigQuery is the odd one out: paste your OAuth access token into the password field, per Google’s JDBC driver convention.

3. Click Test connection. We connect to your warehouse from our servers, run a quick check query, and tell you what happened. The common problems get a plain-English label rather than a wall of error text: “auth failed” if the password is wrong, “host unreachable” if we can’t reach your database, “database not found” if the name is wrong, “timeout” if the connection took more than five seconds.

4. Once the test passes, the Save button activates. Click it and you’re done. The connection shows up 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.