Setting up your own AI environment: from first process to production
Short answer
An AI environment of your own has four components: a node where the models run, open-weight models you own, your own documents as sources and a layer for roles, sources and logging. Setting it up takes eight steps, from one concrete process and a data inventory to a pilot with real users and the extension afterwards. The biggest choices are where the node stands and who manages it. Most failures come from starting without a process and without an owner, not from technology.
The four components
| Component | What it is | What matters |
|---|---|---|
| Node | A server with GPUs where the models run, in your server room or as a dedicated node in a datacentre | Yours alone, never shared |
| Models | Open-weight language models as files you own and swap | No provider in the chain, no training on your data |
| Sources | Your documents, procedures and systems, connected so the model quotes from them | Answers with references instead of from the model’s memory |
| Control | Roles per team, sources per role, audit log, model management | Accountability for the GDPR, the AI Act and your supervisor |
See What is private AI? for the concepts and AI on your own documents for how sources work.
Eight steps
- Choose one process. Not “AI for everyone”, but for example incoming mail, summarising files or the knowledge base for customer contact. With an owner and a measurable goal.
- Inventory the data. Which documents and systems belong to that process, who may see them, and what is sensitive about them.
- Choose where the node stands. Your own server room if you have and manage one; otherwise a dedicated node in a Dutch datacentre. See AI server hardware for what a node is.
- Choose the management. Your own IT managing the node, or management outsourced under a contract that covers notification deadlines, updates and exit.
- Choose the models. A large model for writing and reasoning, a smaller one for classifying and summarising. Test them on your own questions before choosing.
- Connect the sources. Start with the documents of the chosen process. Access per role from day one; narrowing permissions afterwards is painful.
- Run a pilot. One team, real documents, four to six weeks. Measure the correction rate, the time saved and the errors users report.
- Evaluate and extend. Revise the risk assessment, record the results and take the next process.
The choices that make the difference
- Server room or datacentre. In your own building you control everything, including during a connection outage. In a datacentre power, cooling and physical security are taken care of, but you ask for a locked rack that is yours alone.
- Manage it yourself or have it managed. Managing it yourself needs people who know GPUs, models and updates. Having it managed needs a contract that says what the operator sees and when they notify.
- One environment or one per department. One environment with roles is almost always better: one audit log, one operation, and the sources stay separated anyway.
- When to switch models. When you decide, not the provider. Every switch is a re-check on your own test set.
Common mistakes
- Starting with the hardware. A server without a process becomes a server without users.
- Connecting everything at once. Then the assistant sees more than the employee may see, and the pilot is a data breach from day one.
- No alternative to public tools. As long as your own environment is slower or dumber than ChatGPT, shadow use continues.
- No measurement. Without correction rate and time saved, the extension is a guess.
How werqly fits in
werqly supplies the four components as one whole: a werqly Node in your server room or as a dedicated node in werqly Cloud, open-weight models, the connection of your sources and werqly AI Control for roles, sources and the audit log. You manage it yourself or leave it to werqly. The roll-out for a first process takes weeks, not quarters. Calculate below what the set-up looks like for your organisation.
Frequently asked questions
Questions on this topic
How long does setting up an AI environment take?
A first process usually runs within a few weeks of choosing a node: placing hardware or activating a node in the datacentre, loading models, connecting the sources of the process and setting the roles. The pilot itself takes four to six weeks.
Do we need our own server room?
No. Without a server room the node stands in a locked rack in a datacentre, for your organisation alone. That is different from a shared cloud service: the hardware and the models are still yours.
Which models run in an environment of your own?
Open-weight models such as Llama, Mistral and Qwen, in the size that fits your node and your tasks. Often a large model for writing and a smaller one for classifying. Choose on the basis of a test set with your own questions.
What does an AI environment of your own cost?
That depends on the number of employees, the choice between your own server room and a datacentre, and who does the management. The calculator on this page shows four set-ups for your organisation; the quote after that is binding.
Sources
This article is general information, not legal advice. Rules and guidance change; check the sources listed or ask your lawyer or DPO if in doubt.