Connect Your Data Warehouse

​

Choose at signup

The $249/month Connect plan uses an analytical database your organization owns and pays for. Platinur stores only the connection needed to operate its governed schemas. Open Configuration → Data Warehouse, enter the connection, and press Test connection. A successful test binds that warehouse to the workspace for its lifetime. The Managed plan starts at $499/month. During signup, choose Small or Standard; Platinur provisions that exact server-controlled capacity profile and binds it before your portal is marked ready. There is no warehouse form to complete on first use. Platinur manages the provider resource; an analyst read-only credential can be rotated from the bound warehouse view. Until a warehouse is bound, source loading and modeling are unavailable.

​

The connection form

The common path is three fields; ClickHouse Cloud needs nothing more. Under Advanced: Credentials are stored as secret references inside Platinur’s secret store, never written to YAML or logs. After binding, the password field reads Stored securely — Platinur never echoes it back. To update it (say, after resetting it in ClickHouse Cloud), type the new password and press Test & save connection; leaving it blank keeps the stored one. Permissions. The connecting user needs CREATE DATABASE on the server and full DDL/DML on Platinur’s output databases (raw_*, stg_*, prod_*, and *_validation), plus SELECT on any source databases it should model from. The ClickHouse Cloud default user has all of this. For source data loaded outside Platinur, see External Source Schemas. Network access. If your cluster sits behind a firewall or IP allowlist, allowlist Platinur’s egress IP (available from support) on both configured ports. ClickHouse Cloud services allow connections from anywhere unless you restricted their IP access list. Idling services. ClickHouse Cloud services idle when unused, and the first connection after a quiet period wakes them — expect the first Test connection (or the first query of the day) to take up to ~30 seconds. Platinur retries through the wake automatically and keeps the last-known warehouse state through brief blips, so an idling service never looks like a broken one.

​

Binding is a one-time decision

Once a successful test binds the warehouse, it is fixed for that workspace. Attempting to save a different engine kind returns HTTP 409. If you need a different warehouse, delete the workspace and create a new paid workspace with the intended plan. The connection details and credentials for the bound warehouse remain editable at any time — change a hostname or rotate a password without affecting the binding.

​

Output namespaces

Output databases follow one fixed convention: {stg|prod}_{layer} — stg_staging, stg_dw, stg_marts for staging and prod_staging, prod_dw, prod_marts for production. Platinur creates and manages these databases; they must not be modified outside Platinur, and they are not configurable. The same convention applies to source data: each configured or externally loaded source lands in its own raw_<source> database. See External Source Schemas and Refresh Modes. A throwaway *_validation sandbox is created and dropped automatically for each validation run — do not depend on it persisting.

​

Starting over

V1 does not reset models or unbind a warehouse in place. That compromise keeps GitHub, Staging, Production, Promotions, Monitoring, models, dashboards, and warehouse state under one simple lifecycle. The legacy POST /api/models/reset and POST /api/account/reset endpoints return 410 Gone. To start over, an Owner permanently deletes the workspace from Settings → Delete account and creates a new paid workspace. Deletion requires the exact workspace name, an explicit acknowledgment, and the Owner’s current password. It removes the Platinur account stack and its stored connection credentials, but it does not delete or alter the customer-owned ClickHouse service. Follow the confirmation screen carefully because the Platinur workspace deletion cannot be undone. Managed-plan deletion also cancels its Stripe subscription and removes its dedicated database service; a customer-owned database under Connect is never deleted.

​

Analyst access

Platinur does not create or rotate warehouse users for BYO services. If analysts or BI tools need direct access, create a separate read-only principal in ClickHouse and scope it to the governed serving layers (prod_marts, prod_dw, stg_marts, stg_dw). Do not share the write-capable credential used by Platinur.