Skip to content

SDLC projects

MVP in two weeks. Go live in one month.

Every Boreon MCP Layer rollout runs as its own software project. We scope your Tableau Server or Tableau Cloud site and your warehouses, build and test against them, and deliver it as a central MCP server inside your firewall, with your brand, your sign-in and versioned releases. Then the platform is yours.

Go live in one month

  1. Weeks 1 to 2MVPThe Boreon MCP Layer inside your firewall, with your priority dashboards moved and every number proven.
  2. Weeks 3 to 4Final deploymentThe rest of your priority workbooks, hardening, sign-off and training.
  3. Day 30Go liveYour team runs it in chat, and every future move is yours.

Five phases

From discovery to go-live

A custom SDLC project, then the platform is yours.

  1. Discover

    Scan your Tableau Server or Tableau Cloud site and pick the priority dashboards.

  2. Design

    Map Tableau fields to Snowflake and Databricks columns, and agree access.

  3. Integrate

    Stand up the Boreon MCP Layer inside your firewall, with SSO and all three platforms connected.

  4. Prove

    Move the priority dashboards to the warehouse and check every number.

  5. Launch

    Final deployment and go-live inside one month. Your team runs it from day one.

The timeline

MVP in two weeks, live in one month

Weeks one and two deliver the MVP, weeks three and four the final deployment, and on day 30 you go live.

  1. Days 1 to 5

    Kickoff

    • A scan of your Tableau Server or Tableau Cloud site
    • The Boreon MCP Layer inside your firewall
    • SSO and all three platforms connected
  2. Days 6 to 10

    MVP

    • Your priority workbooks moved
    • Their Prep flows moved
    • Every number proven
  3. Weeks 3 to 4

    Final deployment

    • The rest of your priority workbooks
    • Hardening and sign-off
    • Training for your team
  4. Day 30

    Go live

    • Your team runs it in chat
    • Your chosen support plan begins
    • Every future move is yours

Live on day 30

  • Your central LLM portal, inside your firewall
  • Your priority dashboards moved, with every number proven
  • Yours to keep, with no license fees

What we need from you

  • A Tableau site admin and warehouse service accounts
  • An SSO app registration and a server inside your firewall

Where it lives

Inside your own cloud, beside your data

The Boreon MCP Layer runs as one central MCP server in your Azure VNet or AWS VPC, in a private subnet behind your firewall.

  • Your people, your SSO. Your people reach it in a browser on your network or VPN, and sign in through Entra ID, Okta or any OIDC provider.
  • One server, three layers. A WAF edge with Caddy and OWASP Coraza rules, the MCP server for chat, migrations and fidelity, and Postgres with pgvector for knowledge, audit and secrets.
  • Your AI, your storage. AI calls go to your own OpenAI keys through Azure OpenAI or OpenAI, and backups land in your own S3 or Blob storage.
  • Your platforms. Tableau Server or Tableau Cloud over REST and VizQL, and your warehouses over Private Link.

Your cloud, your keys, your data. The platform stays with you in perpetuity.

Yours to keep

Then the platform is yours

We hand the Boreon MCP Layer over at go-live, and it stays with you.

Your central LLM portal

It stays onsite as the chat portal for your data warehouses, with Genie in every Databricks dashboard.

Inside your firewall

One central MCP server on your own infrastructure, ready to upgrade and grow with the company.

No license fees

Yours in perpetuity, for a project that typically costs about 10% of a single data warehouse migration. Maintenance, managed service and support plans are optional.

No consulting firm

Integrate the Boreon MCP Layer once, then migrate at your own pace in chat, with no deadline pressure and no bill per move.

Questions about the project

What teams ask before they start.

How long until we go live?
The MVP lands in two weeks, and final deployment and go-live follow within one month.
What do you need from us?
A Tableau site admin and warehouse service accounts, plus an SSO app registration and a server inside your firewall.
Who runs it after go-live?
Your team, from day one, in chat. Our yearly maintenance, managed service and support plans are there if you want them.
How are releases handled?
Every release after the handover is versioned and tested before it reaches your server.
What happens after the MVP?
You get a roadmap for the rest of your Tableau Server or Tableau Cloud site, and the same server grows with you.

MVP in two weeks. Go live in one month.

Tell us which dashboards on your Tableau Server or Tableau Cloud site you would move first. We scope them, stand up the Boreon MCP Layer inside your firewall and put a working MVP in front of your team in two weeks, with final deployment and go-live inside the month.