Skip to content
Models and deployment

You choose where your AI runs. Department by department.

The neuland.ai HUB runs in the EU cloud, in Schwarz Digits Cloud (STACKIT), in your data center or hybrid. You switch models without rebuilding and run your own model alongside them.

Muster AG · Location per department

Not every task can run just anywhere. Protection needs determine the location.

Confidential documents need more protection than ad copy. In the neuland.ai HUB, you choose the deployment model and approved models per department, from the EU cloud to your own data center.

Deployment models

One deployment model per department. Confidential in-house, everyday in the cloud.

Four deployment models, freely combinable: for the whole enterprise or per department, matching how your information security classifies documents.

  • The neuland.ai HUB runs in EU data centers, for example on Microsoft Azure or Google Cloud depending on requirements; processing takes place primarily in Germany and the EU. All subprocessors are named in the DPA. The fastest start, for example for Sales and HR: quote letters, job ads, announcements to staff.

Model choice

Auto mode picks the right model for each message. Only from the models admins approve.

In Auto mode, each message goes to a suitable model based on its complexity: a quick follow-up question to a fast one, the summary of a 40-page customer contract to a strong one. Anyone who wants to can choose for themselves, even mid-chat. Existing contracts with model providers plug in via Bring Your Own Key (BYOK). All models compared

Model choice today
TimeWhoActionModelStatus
09:41:07LegalCustomer contract summarizedStrong · in‑houseAuto
09:43:52LegalLiability cap question answeredFast · in‑houseAuto
10:04:12ProcurementQuotes for cast housings comparedStandard · Schwarz Digits CloudAuto
10:18:45HRJob ad draftedStandard · EU cloudAuto
10:31:02LegalLiability clause drafted to company standardCustom model · in‑housemanual
09:41:07Strong · in‑houseAuto

Legal · Customer contract summarized

09:43:52Fast · in‑houseAuto

Legal · Liability cap question answered

10:04:12Standard · Schwarz Digits CloudAuto

Procurement · Quotes for cast housings compared

10:18:45Standard · EU cloudAuto

HR · Job ad drafted

10:31:02Custom model · in‑housemanual

Legal · Liability clause drafted to company standard

  1. Legal and Engineering can only choose models in the corporate data center.

Model benchmark

Which model for what? Measured independently.

How strong, how fast and how expensive common models are, measured by Artificial Analysis, plus which ones can run in your own data center. Go to the model benchmark

For example, these models, proprietary and open

  • OpenAI
  • Claude
  • Gemini
  • Llama
  • Mistral
  • DeepSeek
  • Qwen
  • Kimi
  • GLM
  • Cohere
  • Aleph Alpha

Model switch

Switching models is a setting, not a project.

Agents, knowledge and orchestrations are not tied to one model. An example from Procurement: Monday to Friday, without anyone rebuilding anything.

Control

The same protection rules at every location. And no model learns from your data.

The rules travel with you, wherever the computing happens: switching the model does not switch the protection.

LocationYou choose per departmentEU cloud, Schwarz Digits Cloud, corporate data center or hybrid. You decide, not the model provider.
TrainingExcludedYour data, from customer contracts to engineering reports, is never used to train language models.
PermissionsPer roleLegal sees no HR files, HR sees no contracts, even in chat.
LogCompleteAccess and events are logged by the same rules at every location, even after a model switch.

FAQ

What information security asks first.

  • No, the automatic choice is based on the complexity of a message. But it only uses models that admins have approved for the respective group. If only models in your own data center are approved for Legal and Engineering, every request stays there.

Which department runs where? We define it with you.

You bring your departments; we assign each one a deployment model and its approved models, as the basis for your onboarding plan.

Page footer