Skip to main content

​
Datasites: Your Own URL and Custom Domains

Published datasites now live at their own address instead of a shared path.
  • Every datasite gets its own subdomain the first time you publish it, named after the datasite — something like revenue-overview-x7k2p.supaboard.live. Embed links and the publish popover use this address from now on.
  • You can also serve a datasite from a domain you own, like dashboards.yourcompany.com. Add the hostname in the publish popover, create the one CNAME record it shows you, and the certificate is issued automatically — no support ticket, no verification step.
  • The popover shows the exact DNS record to create, with every cell copyable, and a live status dot per domain that tells you whether DNS has propagated, whether the certificate is up, and what to fix if something answers but isn’t your datasite.
One thing to watch: the DNS record must be plain DNS. A CDN-proxied (“orange cloud”) record terminates TLS at the CDN, so a certificate can never be issued for it. Read the full setup guide here.

​
Datasite Variables

Datasites can now hold API keys and configuration values — an analytics key, a maps token, a private API credential — without hardcoding them into the page.
  • New Variables manager in the datasite editor toolbar (the key icon)
  • Public variables ship inside the page, for publishable keys like analytics or maps. Code reads them with sbEnv("NAME"), and rotating a value takes effect on the next page load with no rebuild.
  • Secret variables never reach the browser. The page calls sbApi("NAME", ...) and the server makes the request on its behalf — and only to the API host you pinned when you created the variable.
  • Values are write-only. After saving, no one sees a value again: not the form, not the AI, not any API. A last-4 preview helps you tell keys apart.
  • The AI sees variable names and descriptions, never values. It can also request a variable it needs, which appears as a “Needs a value” slot and lights a badge on the toolbar button.
Read more about variables here.

​
Sign In to Private Datasites with Google or Microsoft

The sign-in page on private datasites now offers Continue with Google and Continue with Microsoft alongside email and password.
  • Access rules are unchanged: the account must belong to your workspace. There is no self-registration through these buttons.
  • Works on the datasite’s own subdomain and on custom domains.

​
Conversation Threads in the Datasite Analyst

The analyst panel now keeps separate conversations, the way the automations copilot does.
  • A thread switcher sits at the top of the panel — start a new conversation, rename one, or delete one
  • New threads are named automatically from your first message
  • Reopening a datasite drops you into your most recent thread, and a thread you leave mid-turn keeps working and re-attaches when you come back
  • Chats from before this release are preserved in a single thread

​
Query Builder: History and Undo

The Query Builder now records versions of your query and lets you move between them.
  • New History panel in the right rail, next to Schema and Assistant
  • A version is recorded every time you load, run, or save a query, and every time you accept an AI edit — each tagged with its source and a +N −N diff count
  • Hover a version to preview it as a diff in the editor; click to apply it
  • Undo and redo with ⌘Z / ⇧⌘Z (Ctrl+Z / Ctrl+Y on Windows and Linux), and the history survives a page reload
  • Also fixed: collapsing the assistant panel no longer kills a reply that’s still being written

​
IPsec VPN for All Self-Hosted Databases

Site-to-site IPsec VPN, previously limited to a subset of connectors, now covers every self-hosted database: Postgres, MySQL, Microsoft SQL Server, Oracle, MongoDB, ClickHouse, and Redshift. Connect databases that live entirely inside a private network — no public IP, no bastion host. Setup instructions are in the IPsec VPN guide.

​
Partial Filters: The Marker Is Now $$

The marker that keeps a table reference out of dashboard filtering has changed from $ to $$, and it now works as a strict prefix: $$ORDERS. If you use $ in existing queries, update them. A single $ is now treated as a normal reference and gets filtered like everything else. The old suffix and mid-word placements (ORDERS$, ORD$ERS) are gone too — only the $$ prefix opts a reference out. The Partial Filters guide has been updated for the new marker.

​
Connect Supaboard to Slack

Ask your agents from Slack. Mention @Supaboard in a channel — or message it directly — and the answer lands back in the same thread: charts as images, tables and KPIs as native Slack blocks.
  • A workspace admin installs the app once; each person links their own Supaboard account with /supaboard link
  • Slash commands switch your workspace and agent, list dashboards, and show your link status
  • The Slack surface is read-only — it can ask and list, never change your data
Setup instructions are in Connect Supaboard to Slack.

​
Fixes and Improvements

  • Ask AI on dashboards can now read the files you attach to the conversation
  • Fixed a bug where a widget could silently query the wrong database and chart zeros
  • People are shown by their real names across the app, instead of usernames and workspace handles
  • The agent tuning copilot shows a recent-activity feed and accepts attachments
  • Fixed branch-node writes that could stall the automations copilot
Thank you for using Supaboard. We’re continuously improving the platform to help you explore, understand, and act on your data faster.
Last modified on October 1, 2026