Local AI
Language models in your own house.
Open models are good enough for real work — chat, searching documents, code. The difference from cloud AI: your data stays where it belongs. With you.
Local AI means running open language models like Llama, Qwen or Kimi with tools like Ollama, Open WebUI and RAGFlow on your own hardware or EU servers — prompts and documents never leave the company.
What I build
- Model and hardware advice: what your use case actually needs — from a workstation to a GPU server
- Chat and assistance with Ollama and Open WebUI, usable across the team
- RAG over your own documents with RAGFlow: answers from your knowledge, not the internet
- Coding assistance with local models (Llama, Qwen, Kimi & co.)
- GDPR embedding: local AI does not replace the process — it makes it easier
- Operations, updates and model maintenance afterwards
How it works
First call
Free: which use case, which data, which expectations?
Pilot
One use case, real data, a clear success criterion — before you invest.
Rollout
From pilot to team tool: permissions, interface, integrations.
Operations
Updates, model changes, monitoring — AI is software, it wants maintenance.
Who this is for
For companies that want to use AI without sending customer data to US providers — and for everyone who first wants a manageable pilot to see what local models can really do.
Frequently asked questions
Is local AI good enough? +
For many tasks, yes: text, summaries, search over your own documents, coding assistance. Whether it is enough for your case, a pilot with real data shows faster than any slide deck.
What hardware do we need? +
That depends on the model and the number of users — from a single workstation to a dedicated GPU server. Sizing is part of the advice; you buy once the need is clear.
Are we automatically GDPR-compliant with local AI? +
No — local AI solves the transfer problem but does not replace the process: purposes, legal bases and deletion concepts are still required. The advantage: with data in-house, that process gets much simpler.
What does getting started cost? +
The pilot is deliberately cut small and gets a clear effort estimate up front — after the free first call you know what to expect.
From the blog
CLOUD Act in the EU region: not sovereignty
The CLOUD Act reaches AWS servers in Frankfurt too: US authorities can access data in any EU region. Why EU servers alone are not sovereignty.
Local AI for your business: your models, not the cloud
Local AI instead of ChatGPT: when customer data belongs on your own models, what cloud AI may handle, and how data protection stays practical.
GDPR-Compliant AI Is a Process, Not a Place
“Runs in the EU, so it's compliant” is too short. What actually makes AI privacy-compliant — and a simple matrix for which data goes where.
AI yes — but without the data leak?
In a free first call we find the use case worth piloting.