What is an AI platform?

The software your team uses for AI day to day: the interface for chat and agents, the connection to your documents (RAG), user management and administration. The platform sits above the model and the infrastructure, and is the layer where your chats, files, prompts and knowledge live.

Which AI platform is right for a business?

It depends on the need. For most companies, a general-purpose platform such as Open WebUI, LibreChat or a turnkey Swiss service is enough. Individual industries with particular documents and regulations have specialised platforms. Beyond the features, what matters is the ecosystem, the operations model and the exit path.

Why does the platform bind you more than the model?

Because the model is interchangeable, but the platform holds your data: chat history, uploaded files, prompts, memory and, above all, the curated knowledge base. The more you invest in that knowledge base, the more expensive a switch becomes. That is why platforms differ from each other far more than the models underneath them.

Can an AI platform be operated sovereignly in Switzerland?

Yes. You can run an open platform such as Open WebUI yourself on your own hardware, or choose a Swiss provider that hosts and operates it on Swiss infrastructure. Platform, host and operations are three separable roles here: you can take on all three yourself, hand them to a provider, or mix them.

Open WebUI or an industry platform?

Open WebUI and similar general-purpose platforms suit most companies and can be operated sovereignly. An industry platform, for law, finance or medicine, say, pays off when your core business depends on domain-specific documents, citation requirements and regulation. Important: an industry platform is not automatically sovereign; its hosting has to be checked case by case.

Sovereign AI platform: why it binds more than the model

The model is easy to swap. The platform holds your chats, files and knowledge, and that is what binds you longest. How to choose platform, host and operations separately, and sovereignly.

What the platform is in AI

The platform is the AI decision that stays longest, because your data lives inside it. This means the software your team uses for AI day to day: the interface for chat and agents, the connection to your documents and user management. Because chats, prompts and the knowledge base built up over months live there, the platform choice weighs more heavily than the choice of model.

In brief

Invest in the knowledge base, and you bind yourself. The more it holds, the more expensive a switch becomes, while the model underneath stays easy to replace.
Choose a model from OpenAI, Microsoft or Google, and you have already decided the platform along with it. Only with open models does the choice stay free.
You do not have to operate everything yourself. Platform, host and operations are three separable roles that you can assign individually.
Look for an open ecosystem. Most niche functions come from there, and only there can you inspect and take them with you.

The public debate revolves around models. In practice, the platform decides more. Let us start there, before turning to individual products.

This is the fourth part of our series on sovereign AI. After infrastructure, it is time for the layer where your team works every day and where your data lives.

Why the platform decides more than the model

In our article on infrastructure, we showed that the language model is the most easily replaceable component. With the platform, it is the other way around. It holds the chat history, the uploaded files, the prompts, the memory and, above all, the curated knowledge base your answers are drawn from. All of this builds up over months and grows with every day of use.

That is why two open platforms pointed at the exact same model are still very different decisions. What separates them is not the model, but how they store your data, how they manage rights and users, which ecosystem they bring, and how easily you can get out again. Checking exactly these things pays off more, before choosing a platform, than comparing the models.

Three roles: platform, host, operations

A clean decision separates three roles that are often bundled into one offer, but remain independently assignable. The platform is the software. The host is the infrastructure on which the model and platform run. Operations is the responsibility for updates, monitoring and security day to day.

These three roles combine freely. You can keep all three yourself, hand all three to a single provider, or mix them, for instance running an open platform through a Swiss partner on Swiss infrastructure. Choosing the software therefore does not yet decide where your data lives and who has access.

Self-operated

Full control, full effort

Platform You

The software freely selectable

Hoster You

The infrastructure your own hardware

Operations You

The ongoing operations your own team

Managed Open Source

You choose, a Swiss partner operates

Platform You

The software open source

Hoster Provider

The infrastructure Swiss cloud

Operations Provider

The ongoing operations Swiss operator

Turnkey

One provider, everything from a single source

Platform Provider

The software ready-made product

Hoster Provider

The infrastructure Swiss cloud

Operations Provider

The ongoing operations included

Platform, host and operations are separable. Take them on yourself, and you keep full control and carry the full effort. Hand them to a Swiss provider, and you stay sovereign, provided jurisdiction and access are right. Most companies end up in the middle.

For sovereignty, the middle is often the right choice: an open platform, hosted in Switzerland and run by a Swiss operator under Swiss law. That keeps control over the data intact, without your team having to carry the entire technology stack itself. What matters then is whom you entrust with hosting and operations, since that partner has technical access to the running system.

Platform given or chosen

Whether you can choose the platform at all depends on an earlier decision.

Whoever commits to a model from OpenAI, Microsoft or Google usually gets the platform delivered along with it: ChatGPT, Microsoft 365 Copilot or Gemini, complete with features for building your own agents (GPTs, Copilot agents, Gems). That is convenient, but it is a closed environment. Your chats, your own agents and your files live inside it, and the provider sets the rules. How firm that lock-in is, OpenAI shows itself: the older Assistants interface is being shut down in August 2026 and replaced with a new one, and organisations’ own GPTs are being moved to a new format. What you build inside a closed platform is never lastingly your own.

Mistral is the European exception here, with its own appeal: Le Chat and the Studio platform come with agents, connectors and a knowledge base, and can be run in your own data centre on request. The distinction matters: many Mistral models are open, the platform itself is not. Open model weights do not automatically mean an open platform.

Whoever stays independent on models instead, choosing open weights, chooses the platform freely. For general use, several mature, open-source interfaces are available: Open WebUI (the most feature-rich, with genuine user management and the largest ecosystem), LibreChat (agent-centred, with MCP and an open licence), LobeChat (a strong interface, but weaker administration) and RAGFlow (specialised in the high-quality processing of difficult documents). For more specialised tasks there are also standalone platforms, such as coding agents like OpenCode or Cline, which orchestrate models, tools and context. These open platforms often bring more functionality than the closed ones, but demand setup and operations in return.

The lock-in sits in the data

The reason the platform choice weighs more heavily than the model choice is the volume and value of the data that accumulates inside it. A plain chat history is still easy to migrate. A knowledge base curated over months, in which your documents have been ingested, chunked, embedded and assigned rights, is not.

That data also sits in the platform’s own particular structure, not in a neutral format. Check the exit before you choose, then: does the platform store data in open, exportable formats? Can you take chats, knowledge bases and configuration with you in full? With open-source platforms, the data sits in standard databases and can be extracted; with closed services, the exit depends on the provider. Sovereignty here means not only where the data lives today, but whether you can bring it home if it ever comes to that.

The ecosystem decides the niches

A platform’s basic functions converge quickly. The difference in daily use comes from the niches, and those mostly come from the ecosystem, not from the core. OpenAI has its GPT Store for this, Open WebUI has server-side functions and tools plus a community catalogue, others rely on extensions and the open MCP standard, through which any internal system can be connected.

For sovereignty, what matters is less the size of the catalogue than its nature. An open ecosystem can be inspected, adapted and self-hosted; a closed extension you have to take as it comes. For a narrow, regulated, Switzerland-specific requirement, a tool you can read and host yourself is often worth more than the larger but locked catalogue. How far a platform can be opened up for your own applications leads to the next layer, integration, which we cover in the final article of the series.

What the platform delivers that the model does not

Some capabilities do not come from the model at all; they come from the platform. Each of them calls for its own check, because each can create its own path for data to leave.

User management is the biggest difference between platforms: roles, groups, sign-in through your corporate directory and fine-grained permissions separate a serious enterprise platform from a plain interface. Open WebUI and LibreChat are strong here, others markedly weaker.

Web search is more delicate than it looks: for the AI to search the web, the platform sends the search query to an external search service. That query can be sensitive, and it leaves your environment even when the model itself runs locally. A self-hosted metasearch tool such as SearXNG softens this, because the query goes out depersonalised and bundled; it cannot be avoided entirely as long as the open web is to be searched.

Code execution, which the AI uses to analyse data for instance, poses a clear choice. Run locally, the data stays sovereign, but you are executing code generated by the model and need genuine isolation (a container or microVM). Bought in as a ready-made cloud service, security is solved, but code and data then run at a third party. For sensitive data, the sovereign answer is to execute locally and in isolation.

General-purpose or industry platform

Most companies are well served by a general-purpose platform. For individual industries, though, there are platforms tailored to their documents, workflows and regulations, and they hold a genuine edge there. In law, tools such as Zurich’s DeepJudge or the European Noxtua search and understand legal holdings, complete with citations and matter logic. In finance, Zurich’s Unique covers typical workflows from research through to compliance. In medicine, services such as Lausanne’s DOCumenter write reports directly from the consultation, with processing exclusively in Switzerland.

The advantage of such platforms is depth in one domain: fitting document understanding, built-in citations and review steps, ready-made specialist workflows. The price for that is twofold. First, they are mostly closed products with their own lock-in and higher licence costs. Second, and this is often overlooked: an industry platform is not automatically sovereign. Several well-known providers run on US cloud infrastructure, even where the data sits in Europe. Whether a specialised platform is the better choice is decided by your core business, and its sovereignty has to be checked case by case, behind the marketing.

The path to a sovereign platform

A fully-fledged sovereign platform is considerably more than an installed copy of Open WebUI. It takes user management and sign-in, a clean knowledge base, observability (monitoring and traceability of operations), the protection of sensitive data, and reliable operations with updates. There are three answers for the path there, from the greatest control to the greatest convenience.

First, self-operation: you host and run the open platform entirely yourself. That offers maximum control at maximum effort. Second, managed operation through a Swiss partner: providers such as Begasoft, Swisscom, Infomaniak, AlpineAI or kvant run a platform on Swiss infrastructure for you. Sovereignty is preserved provided jurisdiction and access are right, since the partner has access to the system. Third, preconfigured bundles, which bring the entire sovereign build as one package.

Key figure

6 cantons, over 100 municipalities

Begasoft builds and operates a sovereign AI platform on open models and Swiss infrastructure for the Swiss association for municipal and cantonal IT (SSGI), revFADP-compliant, with rollout from 2026. Sovereign platforms are already running in production in Switzerland.

Source: Begasoft, SSGI mandate 2026

One example of such a bundle is the Swiss AI Hub, an open-source project that brings a whole sovereign platform (chat, model access, knowledge base, sign-in, observability) together as one combined package of components, and can be run in your own data centre or a Swiss one. A project like this takes a lot of the build-out off your hands, but is itself demanding to operate and keep current.

Disclosure: I helped shape the Swiss AI Hub as an architect. This is not a recommendation, and the AI Hub is not the right solution for every case. For many companies, a single Open WebUI instance or a turnkey managed service is the lighter, better-suited path.

What this means for your company

The platform is the decision that stays longest, because it holds your data. Choose it, then, for more than its features: for the ecosystem behind your niches, for the exit path, and for the question of who hosts and operates it. And do not let the model choice quietly predetermine the platform for you.

What remains is the top layer, where AI starts acting inside your systems. The final part of the series belongs to it.