AI Models

How to choose the AI model for each chat in Kasimir and how admins govern models, the default model and EU data residency.

Kasimir is a multi-LLM platform: you don't chat with a single fixed model — you choose, per conversation, which AI model answers. The default model is hosted by Kasimir itself, on its own servers in the EU, making it the most GDPR-sovereign option. Stronger cloud models can be added, while it always stays transparent where your data is processed. This page explains how to switch models in chat, what the badges and hints mean, and how administrators govern the available models for the whole company.

Choosing the model in chat

Every conversation uses exactly one model. The model switcher sits in the composer at the bottom of the chat: a button with a colored dot and the model name (e.g. Llama 3.3 70B (EU)). Clicking it opens the list of models enabled for your company.

• Pick a model from the list — from the next message on, that model answers.

• Your most recently used model is remembered in the browser and pre-selected the next time you start a new chat.

• If your administration has set a default model, it is pre-selected in new chats. You can still switch at any time.

EU and Non-EU badge

Each model in the list carries a badge that shows at a glance where processing happens:

The detail panel (hover)

On desktop, hovering over a model in the list reveals a small info panel showing:

• the provider (e.g. Kasimir, Microsoft Azure, xAI),

• a short description of the model,

• Context — the size of the context window (e.g. 128k tokens),

• Image understanding — whether the model can "see" images or PDFs (yes / no),

• Data processing — where your inputs are processed.

For Data processing, three tiers are distinguished:

• Processed on Kasimir's own servers in the EU — the most sovereign option (default model).

• Processed in the EU · Azure AI Foundry (Microsoft) — EU region, but via a third-party processor.

• Processed outside the EU – data leaves the EU — only for Non-EU models.

Data-processing hint below the input

When you pick a model that does not run on Kasimir's own EU infrastructure, a hint appears directly under the input field — so you know where your data goes before you send:

• EU cloud: Processed in the EU via Azure Foundry (Microsoft) (neutral hint).

• Non-EU: Note: processed outside the EU – data leaves the EU (amber warning).

For the self-hosted default model no hint is shown — here data never leaves Kasimir.

"Coming soon"

At the bottom of the model list there's a Coming soon section with further frontier models (e.g. GPT-5.2, Claude Opus 4.8, Gemini 3.1 Pro). These are greyed out and not yet selectable — they preview the planned expansion of the model catalogue.

Managing models for the company (Administration)

Owners and administrators control which models are available to members under Administration. Two areas matter here.

AI Models — turn models on and off

The Administration → AI Models page lists every chat model available to the company. Each row shows the model name, the provider, whether it runs Self-hosted or Cloud, and — if paid — the cost per 1k tokens (input/output).

The toggle on the right enables or disables a model for the entire company. Disabled models no longer appear in anyone's chat model switcher. Changes only take effect on Save; Discard resets them.

Chat settings — default model and the EU gate

The Administration → Chat settings page sets the default chat behaviour for all members. Two options matter for models:

• Default model — the model pre-selected in new chats. Choosing (no default — users pick themselves) leaves the choice to members. Users can always override the default.

• Allow non-EU models — the data-residency gate (see below).

The page also controls other chat defaults such as web search, file uploads and a company-wide system-prompt addendum.

The EU / GDPR gate for non-EU models

Kasimir's core advantage is EU-sovereign hosting. Stronger external models (e.g. Grok/xAI from the US, DeepSeek from China) can be offered, but are off by default — so privacy-sensitive companies never even see models that would process data outside the EU.

Only when the administration enables Allow non-EU models under Chat settings do these models (with an amber Non-EU badge) appear in the model switcher. While the gate is off, they are hidden everywhere — in the chat switcher as well as via the API.