Skip to main content
Use this path to take a new workspace from its first sign-in to a published warehouse.

​
The golden path

  1. Choose a plan, verify your account, and subscribe. Choose Connect (249/month)orManaged(from249/month) or Managed (from 499/month), choose a Managed capacity when applicable, accept the current Terms and Privacy Policy, verify your work email, and complete Stripe Checkout. Platinur creates no workspace before payment is confirmed. If the verification message expires or never arrives, use Resend verification email on the pending screen; the response stays intentionally generic to protect account privacy.
  2. Connect your warehouse when using Connect. Configuration → Data Warehouse → enter the host, username, and password for your customer-owned ClickHouse → Test connection. A passing test binds the warehouse to the workspace for its lifetime. New to ClickHouse Cloud? Follow Bring Your Own ClickHouse Cloud step by step. Managed plans arrive with their dedicated ClickHouse already connected.
  3. Connect GitHub. Configuration → GitHub → Install on GitHub. Installing the Platinur GitHub App returns you to the portal connected — no repository setup needed; Platinur creates and initializes the governed repository automatically at your first apply. See Connecting GitHub.
  4. Connect a source. Integrations → choose a native database, file, spreadsheet, or managed SaaS connector → enter the connection → the first passing test saves it and opens the source’s page. See Source Integrations.
  5. Scan and load. On the source’s Schema tab, run a scan to discover its tables, choose the tables and refresh mode, then Run to load the data into your warehouse’s raw_<source> database.
  6. Build your models. Models → Build → start the first build. The assistant profiles your data, then interviews you — short business questions with suggested answers — and builds your staging, warehouse, and mart layers from what you tell it. See The First Build.
  7. Review Staging. The assistant validates and commits the files to Staging. Review the resulting models, dashboards, and cumulative diff in Promotions.
  8. Prepare and publish a release. When Staging looks right, press Prepare release, select the changes to publish, review automatically included dependencies and what stays in Staging, edit the pull-request name/description, validate both resulting states, and confirm. Platinur opens and merges the exact release PR when repository rules allow, reconstructs remaining Staging work, then starts the Production refresh. See Releasing to Production.

​
Readiness checks

  • Configuration shows the warehouse Connected and GitHub Connected.
  • The assistant card shows Ready (platform-supported AI is included — adding your own API key is optional).
  • Your source’s page shows a successful scan and at least one load with rows.
  • Models → Models lists your built layers; Dashboards renders with your data.