Platform and Operations
Platform and Operations on the blog.
Where the models run, who picks them, and what that means for your data.
What this topic covers
Orchestration means the right model for each task and a traceable record for each call. Whether those models run in your own data center, in a private cloud, or in a mix is not a matter of taste: it is an architectural decision with consequences for privacy, cost, and availability.
These posts cover deployment options, open European models, what a model swap costs you, and when building custom software is worth it. The house position has not moved: we build only when it genuinely pays off.
The platform page shows how the platform is put together and which deployment options exist.
See the platformPosts on this topic 3 posts
Sovereign AI is not a seal · four questions decide it
Four questions decide whether an AI setup is genuinely sovereign: where computation happens, who holds the keys, who can be legally compelled, and whether you can get back out. Plus what sovereignty costs.
5 min read
We are not a software vendor · when building your own actually pays
Four tests decide whether building your own software makes sense. In most cases at least one of them fails, and that is a good outcome.
5 min read
AI orchestration for mid-sized companies · why the next tool will not fix it
Everyone who experimented with AI in 2025 is now sitting on half a dozen disconnected tools. What orchestration means, which three patterns cover most of the work, and where adoption really breaks down.
6 min read