Nederlands

AI assistants and agents for your team

A general chatbot doesn't know your documents, your customers or your procedures. I build assistants and agents that do, with a source for every answer and clear limits on what they're allowed to do.

Tell me about your project

The problem

Knowledge sits in documents, wikis, tickets and people's heads. Finding the right answer takes time, and new colleagues keep asking the same questions.

Public chat tools are tempting, but they don't know your context, they can't tell what a user is allowed to see, and they send your data elsewhere.

How I approach it

  1. Start with the questions

    We collect real questions and tasks first, so we build for what people need.

  2. Connect the right sources

    Documents, wikis, tickets or databases, indexed so the assistant finds the relevant passages and cites them.

  3. Respect access rights

    Users only get answers from sources they're allowed to see.

  4. Agents with clear limits

    When an assistant takes actions, such as creating a ticket or updating a record, it uses a small set of well-defined tools, and anything risky needs a person's approval.

  5. Measure the answers

    A test set of questions with known answers, so quality is measured, not assumed.

What to watch out for

  • An assistant without sources is hard to trust. Every answer should show where it came from.
  • Outdated documents give outdated answers. Someone needs to own the sources.
  • An agent that can do everything is a security risk. Give it only the tools it needs.

Projects like this

A private AI workspace with specialised agents

A self-hosted chat environment with agents for different tasks, so the team can use AI without sending data to a public chat app. A separate API layer logs usage and caches answers.

  • Agents for different tasks in one chat environment.
  • An API layer between the agents and the model providers that logs usage and caches answers.
  • Everything runs on infrastructure the organisation already has.
  1. Questions and documents from the team
  2. Specialised agents
  3. Layer for logs and cache
  4. Answers inside the organisation's own environment

Local language models, only when the team needs them

Language models that run on the team's own GPUs, so no data goes to an outside provider. One API serves all models. A model starts on the first request and stops when nobody uses it, which frees the GPU for other work.

  • One OpenAI-compatible API for all local models, which team members connect their chat and coding tools to.
  • A dashboard shows which models are running, and admins can start or stop any of them.
  • Everything runs on hardware the organisation already owns.
  1. Request from a chat or coding tool
  2. Shared API
  3. Start the model if needed
  4. Answer from the local model

Frequently asked questions

Can it use ChatGPT, Claude or a local model?

Any of them. The choice depends on your data, your privacy requirements and the cost, and one gateway can combine them.

Where does it run?

In your own environment or a private cloud in the EU, connected to your existing logins.

What is MCP?

The Model Context Protocol is an open standard for connecting AI assistants to tools and data. I use it to give assistants a controlled set of actions in your systems.