Use AI. Keep control of confidential data. Private AI on your servers or with our hosting partners.

You want to work with internal documents without uploading them to arbitrary AI services. We establish what the system needs to do, select appropriate infrastructure and set up the workspace: on-site, on dedicated servers or with carefully controlled cloud access.

Your team already uses AI. Where does your business data go?

One person summarises a customer email in a personal account; another uploads a document to try a new tool. Without a shared workspace, it is difficult to know what is being processed where.

We start with the tasks and data involved. Some can use an approved business AI service. Confidential documents may need a private environment with defined permissions and clear rules for external connections.

Three ways to run private AI

On your own hardware

Documents are processed inside your environment. A compact machine such as a Mac Studio may suit limited tasks; larger models or concurrent usage may call for a GPU server, for example with NVIDIA hardware. We assess the requirement before recommending a purchase.

Dedicated hosting

A separate server environment avoids running hardware in your office. We work with ISO 27001-certified hosting partners and agree location, access, responsibilities and recurring costs in the proposal.

Hybrid, with controlled release

Protected processing stays in the private environment. A powerful cloud model can assist with selected tasks using content approved for that purpose. The boundary is deliberately configured, rather than left to individual judgement each time.

Choose the task before the hardware

  1. 01

    Define tasks and data

    Should the system search, draft, classify or automate a step? We identify source documents, confidentiality requirements and who will check the results.

  2. 02

    Size the system

    Model requirements, document volume, response time and simultaneous users affect capacity. We compare local hardware with dedicated hosting, including operating costs.

  3. 03

    Configure and test

    We connect the agreed sources, set permissions and test real tasks with your team. Training covers how to use the application, check answers and open the supporting material.

  4. 04

    Agree ongoing operation

    Updates, maintenance, backups and support can be added as needed. Responsibilities are assigned explicitly between you, us and any hosting partner.

What a private environment can support

  1. Find internal knowledge

    Ask questions about approved manuals, policies or project material. The application shows supporting sources and applies the agreed access rules.

  2. Prepare documents

    Summarise lengthy material, locate relevant passages and prepare drafts. Your team checks the output before using it.

  3. Automate repeat work

    Smaller local models may be enough to classify documents or prepare responses. The workflow includes reviews and a route for cases the system cannot handle.

  4. Use cloud AI selectively

    Complex work without confidential inputs can still use a cloud model. A hybrid setup keeps that work separate from tasks that must remain internal.

Privacy depends on the whole setup

Running a model locally does not by itself settle privacy and professional confidentiality requirements. Access rights, logs, retention, external connections and maintenance access also need to be considered. Your organisation’s requirements inform the design.

Removing names is not always enough to make a document anonymous. In hybrid setups, we agree which content may leave the private environment. A task that must stay internal is configured without forwarding its content to a cloud model.

A hosting partner’s ISO 27001 certification applies to its certified scope. It does not replace assessment of your specific application.

An example: private customer enquiry, general cloud template

  1. 01

    Keep the confidential enquiry internal

    A local model reads the approved message and finds relevant internal material. Customer names, contract details and attachments remain inside that environment.

  2. 02

    Give the cloud a separate, approved task

    A cloud model might draft a general checklist for structuring a response. It does not need the original message or customer details. This handover is a defined part of the workflow.

  3. 03

    Review the actual response

    The template is combined with the required details inside the private environment. A responsible person checks content and recipient before sending. If the task cannot be completed without confidential context, that step also stays internal.

Questions about private AI

What does on-premise mean?

The AI system runs on infrastructure you control. It can process documents without sending them to an external model provider. We clarify whether updates, support or other features need external connections.

Do we need a large server?

Not necessarily. A focused application for a few people needs different capacity from a system serving many simultaneous requests. We size the hardware around the intended work.

What does private AI cost?

Simple internal chatbots can start at €2,000 excluding VAT. On-premise deployment may add hardware and operational setup; hosting introduces recurring costs. The proposal separates development, infrastructure and optional support.

Can we still use ChatGPT, Copilot or Claude?

Yes. A suitable business version can remain available for approved work. We configure the workspace and train your team on which information may be used with each tool.

Can you maintain the system?

Yes. We or our partners can provide the agreed service and support. Scope, responsibilities and costs are agreed before work begins.

Which information needs to stay private?

Describe your tasks and requirements in a free first call. We will help identify a suitable starting point.

Book a first call