docs(experimentation): add Databricks bring-your-own-warehouse guide

[Zaimwa9]

Thanks for submitting a PR! Please check the boxes below:

• I have read the Contributing Guide.
• I have added information to docs/ if required so people know about the feature.
• I have filled in the "Changes" section below.
• I have filled in the "How did you test this code" section below.

Changes

Contributes to the Databricks bring-your-own-warehouse series: #8700, #8703, Flagsmith/warehouse-delivery#16 and the
Databricks frontend PR (not yet open).

• New experimentation/connect-databricks page: requirements, setup steps, secret rotation and troubleshooting.
• connect-a-warehouse: results now come from the connected ClickHouse (since feat(experimentation): read experiment results and exposures through the environment's warehouse #8683), a Databricks section links to the
  new page, and Databricks is out of "Coming soon".
• index: mentions bringing your own ClickHouse or Databricks.
• create-metrics: at-least-once delivery note.
• Docs parity test for the Databricks setup SQL. It depends on the frontend PR's databricksSetupSql.ts, so the frontend PR must merge first.
• Screenshot placeholder for the Databricks form (warehouse-databricks-form.png), to be captured.

Open points:

• Only Can use on the SQL warehouse is documented, as in the guide. Nobody has checked it's sufficient; QA's service
  principal probably had Can manage.
• Workspaces with IP access lists enabled will block Flagsmith until our outbound IPs are allowed; we don't publish them
  yet. Follow-up: confirm the static egress IPs for the API task processor and warehouse-delivery, publish them, then
  document IP allow-listing for ClickHouse and Databricks.
• Private Link-only workspaces: not supported or tested. We call the public Statement Execution and Zerobus endpoints.
  Follow-up: confirm the behaviour and either support it or document it.

Merge only when API #8703, warehouse-delivery feat/databricks-delivery and the frontend PR are deployed to production, and
databricks_warehouse exists in production and is on for at least one organisation.

How did you test this code?

• make lint in docs/: changed files pass prettier (166 untouched files already fail on main); build passes.
• Every error message in the troubleshooting table checked against the API and warehouse-delivery code.
• Setup SQL on the page checked against getDatabricksSetupSql(); the parity test enforces it once the frontend PR is merged.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Oct 9, 2026 8:38am UTC
flagsmith-frontend-preview	Ready	Preview	Oct 9, 2026 8:38am UTC
flagsmith-frontend-staging	Ready	Preview	Oct 9, 2026 8:38am UTC

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

---

_{Comment @coderabbitai help to get the list of available commands.}