Skip to content

Your model. Your keys.

The Boreon MCP Layer lets you choose the model for every task over Tableau Server or Tableau Cloud. Keys are encrypted at rest, every change is audited, and self-hosted installs keep the keys entirely yours.

An example routing

Chat
Swiss-hosted open model
Drafts
Claude Sonnet
Escalation
Claude Opus
Classification
OpenAI GPT

Keys encrypted at rest · every change audited

The model you choose, per task

The Boreon MCP Layer holds a slot for each provider and routes every task to the model you pick.

  • Infomaniak AISwiss · the defaultOpen models such as Qwen and Gemma, hosted in Geneva.
  • AnthropicClaudeClaude Sonnet, Opus or Haiku, chosen per task.
  • OpenAIGPTGPT models, through the OpenAI-compatible slot.
  • Any compatible endpointOpenAI-compatibleAny OpenAI-compatible https endpoint, through the same slot.

Every task on its own model

Chat, drafts, escalation and classification each run on the model you choose, over Tableau Server or Tableau Cloud.

Each route is yours to set, task by task, over Tableau Server or Tableau Cloud.

Swiss-hosted open models are the default. Claude and any OpenAI-compatible endpoint are there for any task you give them.

Your Tableau. Your rules.

Run the Boreon MCP Layer on your own infrastructure or hosted in Switzerland, with the controls your security team asks for.

  • Self-hosted or Swiss-hosted. A signed offline bundle for your own cloud, or hosted by us in Switzerland.
  • Read-only by default. Tableau Server or Tableau Cloud is read through Tableau’s own APIs, read-only. The one write is a workbook you ask to publish.
  • SSO, MFA and audit. Entra ID or any OIDC provider, with every action on the record.
  • A WAF at the front door. OWASP Coraza with the Core Rule Set.

Where it runs, side by side

The same Boreon MCP Layer, on your infrastructure or ours in Switzerland.

Self-hosted and Swiss-hosted, compared
Self-hostedSwiss-hosted
Where it runsOn your own infrastructure, from a signed offline bundleHosted by Boreon in Switzerland
Model keysEntirely yoursEncrypted at rest, with every change audited
Sign-inEntra ID or any OIDC provider, with MFAEntra ID or any OIDC provider, with MFA
Access to TableauRead-only by defaultRead-only by default
Front doorA WAF with OWASP Coraza and the Core Rule SetA WAF with OWASP Coraza and the Core Rule Set

Questions about models and keys

What security and platform teams ask.

Which model is the default?
Infomaniak’s Swiss-hosted open models, such as Qwen and Gemma, hosted in Geneva.
Can each task use a different model?
Yes. Chat, drafts, escalation and classification each run on the model you choose.
Where are the keys kept?
Encrypted at rest, and every routing change is audited. Self-hosted installs keep the keys entirely yours.
Does the model change what it can read?
No. Whichever model you choose, the Boreon MCP Layer reads Tableau Server or Tableau Cloud read-only, through Tableau’s own APIs.
How do people sign in?
Through Entra ID or any OIDC provider, with MFA, and every action is on the record.

Ask your own Tableau, live.

Bring one question from your Tableau Server or Tableau Cloud site. The Boreon MCP Layer will answer it in line, on the model you choose.