Skip to content

Boreon MCP Layer

It publishes only what it can prove.

The engine checks its own work. Every number on a migrated dashboard is compared with Tableau's answer through the VizQL Data Service. If one can't be matched, nothing gets published, and the agent tells you why in plain words.

Book a working session See it live at ai.boreon.com

Measured live on a real Tableau workbook: DBX Platform Latency Calls & Uptime, moved to Databricks.

3 / 3
sheets identical to Tableau
96%
fidelity score
20M
rows in the view, built in 72 s
0
SQL errors on publish

How a migration runs.

You type one line. The layer does the rest and shows its work as it goes.

  1. 01

    Read the workbook

    Shelves, filters and calculations. 3 sheets.

  2. 02

    Find the Prep flow

    The flow behind its data source. 1 flow.

  3. 03

    Turn the flow into a view

    One SQL statement, one CTE per step. 20M rows in 72 s.

  4. 04

    Prove every sheet

    Each query runs before publish. 0 SQL errors.

  5. 05

    Check the numbers

    Against Tableau's own answer. 41 of 41 rows.

  6. 06

    Publish

    A Databricks AI/BI dashboard, at 96% fidelity.

Proof comes with every migration.

Measured on your own workbooks, and shown to you before anything is published.

  • A fidelity report per sheet

    What was mapped, approximated or left out, with a score.

  • Parity with Tableau

    Each sheet's rows compared with Tableau's own answer.

  • Queries proven first

    Every sheet runs on the warehouse before anything is published.

  • A reason for anything it skips

    If it won't migrate something, it names it and says why.

Rows matched against Tableau, per sheet
SheetRows matched
Sheet 1 12 / 12
Sheet 2 5 / 5
Sheet 3 24 / 24
3 / 341 / 41

All 41 rows match · published

The rules it works by.

  1. 01 All or nothing

    A dashboard is only rebuilt on the warehouse its data already lives in. If a single sheet can't be matched, nothing is published, and you get the reason.

  2. 02 Numbers first

    Averages, distinct counts and medians stay exact under dashboard filters, and every result is checked against Tableau's answer.

  3. 03 Proven before it ships

    Every query runs on Databricks or Snowflake before publishing, so nothing opens with a SQL error.

  4. 04 Your identity, your roles

    SSO roles carry through to both warehouses, so people only see what they're allowed to see.

  5. 05 Read-only by default

    It only writes when you ask, and it logs every write.

Which Tableau dashboard would you move first?

Start there. It becomes the first thing we move, checked number by number against Tableau, and the portal it lands in stays yours.

Book a working session See it live at ai.boreon.com