Useful models, with controlled data flows.

Some data should not leave for an opaque API. We define the authorised flows according to your constraints: local or private hosting, access, logs and retention period. A third-party API remains possible if its transfers are accepted and governed; no architecture choice on its own guarantees the absence of leaks or GDPR compliance.

Start with one workflow

Drawing: the line of “Local AI and GDPR”, the same behaviour as on the home page.

When it helps

When documents, conversations or business data are sensitive, subject to internal constraints, or simply too strategic to leave without control.

What you can check

  • We separate real confidentiality, European hosting, on-premise and plain marketing claims.
  • Performance is tested on your cases, not on abstract benchmarks.
  • Governance is part of the work: access, logs, retention, review.

What we build

  • Controlled architecture

    A choice between local, dedicated server, private cloud or a governed API, depending on the constraints, the volume and the level of risk.

  • Open-source models

    Mistral, Llama, Qwen, local embeddings, reranking, RAG. We choose for the use case, not for the model’s name.

  • RAG and documents

    Search across your corpora, citations, context limits, source separation and control of the answers.

  • Governance

    Logs, rights management, retention, leak tests, an approval policy and documentation the teams can actually use.

Method

No long tunnel.

  1. Qualify the risk

    We look at which data circulates, who needs access, what can leave and what must stay closed.

  2. Run a test bench

    We test several options on real cases: quality, latency, compute cost, ease of operation.

  3. Deploy soberly

    We install only the infrastructure that is needed, with monitoring and rollback procedures.

  4. Document

    We leave an understandable architecture, usage rules and the known limits.

Deliverables

  1. A local prototype or target architecture
  2. Model and cost comparison
  3. A RAG pipeline if needed
  4. Security and operations documentation

Let us see if it is worth it.

Send the context, even rough. I reply with a first reading of the subject and a simple way to test it.

Start with one workflow