Skip to contentForbesElevon in Forbes

    Blog

    Local AI Is an Architecture Problem, Not a Model Problem

    Can part of a company's AI work run on a normal laptop, with data that never leaves the company? Our research so far shows that a small model alone is not enough. Four things around it decide whether it is usable.

    2 min read

    Can part of the AI work a company does run on a normal laptop, with data that never leaves the company? That is the question behind our current research. One thing is already clear: a small model alone is not enough. What decides whether local AI is usable is the architecture around it.

    Why local AI matters

    Sending every document to a cloud model is not always possible. Contracts, client data and internal reports are often exactly the documents a company would rather keep on its own devices. If part of the work can run locally and reliably, the data stays where it is, and the cloud is used only where it really adds something.

    How we test it

    Answering the question means testing many combinations of small models, quantisations and prompts on the same data. We run this work on the Discoverer supercomputer (PetaSC, Sofia) through the EuroHPC AI Factories Playground. Its H200 GPUs let us run dozens of configurations in parallel and measure them under identical conditions. We work only with synthetic data.

    Four things that decide whether a small model is usable

    A deterministic layer. The model returns structured output defined by a JSON schema. Every output is validated and every citation is checked against its source. What the model produces is not trusted until it passes these checks.

    Short, closed questions. Instead of one large prompt, the work is broken into small, well-defined steps. Each step asks one question with a clear answer.

    Calibrated decision models. Where a decision is sensitive, it is made by a model calibrated for that decision, not by a general one.

    Our own evaluation. We measure on our own test harness with synthetic Slovak, Czech and English data, not on public leaderboards. What matters is how a model performs on the kind of documents and languages it will actually handle.

    Local where it fits, cloud where it makes sense

    The goal is simple: AI that runs locally and reliably where it should, and cloud where it makes sense. The model can change. The architecture around it is what makes the result something a company can rely on.

    If you are working on local models or evaluation, get in touch. We are happy to compare notes.

    Sources

    • EuroHPC JU: AI Factories Access Modes (eurohpc-ju.europa.eu/ai-factories/ai-factories-access-modes_en)

    Read next

    Two articles that continue this topic.

    • From 1 December, the Same AI Work Costs Twice as Much. Who Planned for It?

      Google is doubling the price of Gemini 4 Argon on 1 December. For companies running agents in production, it is a reminder that the biggest variable in an AI budget is set outside the company, and that the ability to switch models is an operational capability.

      Read the article
    • What Is an Enterprise Agent Inventory and Why Is It Essential for AI Governance?

      An enterprise agent inventory is an up-to-date record of the AI agents operating within an organization. It captures each agent’s purpose, accountable owner, permissions, connected systems and review status. The record helps teams understand what agents can do, investigate incidents and maintain operational control.

      Read the article

    Next step

    Pick one process and see how it runs in your environment.

    A 30-minute call with one of the founders. We say honestly whether the platform fits and what a first run would take.

    We use essential and analytics cookies by default to ensure proper functionality and understand site usage. Marketing cookies are off unless you opt in. Privacy Policy