AI Infrastructure Calculator
The AI servers needed by your company
Eight key figures, three paths compared. The calculator shows GPU, power, staff and costs for AI in your own company and discloses every assumption.
- The calculation runs only in your browser. Nothing is stored until you request the report.
- Recommended path and key figures straight away, without a form.
- All assumptions with their sources in the methodology.
How the calculator works
Every figure in the result follows from your key figures and the assumptions next to them. The assumptions are kept in a single file and maintained with a date.
- Active users are employees times share of knowledge work times usage in the first year.
- Concurrent requests at peak are active users times the share of concurrent use. The share falls as the number of users grows, and with several shifts the busiest shift counts.
- Tokens per day are active users times tokens per application, weighted by the share of users per application.
- Peak throughput follows from concurrent requests and the target speed per request.
- The model class follows from the applications. Agents and programming need larger models than writing and questions.
- The number of GPU is the higher value from memory requirement and throughput, plus one model instance as a reserve for failure.
- Connected load is GPU power plus server base load, times the PUE. The PUE depends on the data centre, and without your own server room colocation applies. Power per year at average utilisation.
- Staff follows from path, number of users and number of GPU.
- Costs over three years are purchase plus three times running costs. Excluding the OneMachine licence and implementation.
- The recommendation follows from protection needs, existing server room, free capacity in the IT team and costs over three years.
| Assumption | Value | Source | Type |
|---|---|---|---|
| Usage | |||
| Usage in the first year, low | 20 % | ZEW 2026, Bitkom 2026 | Survey |
| Usage in the first year, medium | 40 % | UK Government 2025, ZEW 2026 | Survey |
| Usage in the first year, high | 60 % | UK Government 2025, ZEW 2026 | Survey |
| Concurrent at peak, from 1 active users | 8.5 % | Microsoft Azure LLM Inference Trace 2024 | Defined value |
| Concurrent at peak, from 50 active users | 6 % | Microsoft Azure LLM Inference Trace 2024 | Defined value |
| Concurrent at peak, from 100 active users | 4.7 % | Microsoft Azure LLM Inference Trace 2024 | Defined value |
| Concurrent at peak, from 500 active users | 3.1 % | Microsoft Azure LLM Inference Trace 2024 | Defined value |
| Concurrent at peak, from 1,000 active users | 2.7 % | Microsoft Azure LLM Inference Trace 2024 | Defined value |
| Several shifts, users in the busiest shift | 60 % | MindsMachines 2026 | Defined value |
| Working days per year, one shift | 205 | IAB Arbeitszeitrechnung 2025 | measured |
| Working days per year, several shifts | 300 | IAB Arbeitszeitrechnung 2025 | Defined value |
| Tokens per day, Writing and questions | 20,000, 100 % of users | Microsoft Azure LLM Inference Trace 2024 | Defined value |
| Tokens per day, Document search | 60,000, 60 % of users | Microsoft Learn, Azure OpenAI On Your Data 2026 | per vendor |
| Tokens per day, Agents and automation | 200,000, 30 % of users | Anthropic 2025 | per vendor |
| Tokens per day, Programming | 150,000, 10 % of users | Ziegler et al. (GitHub) 2022 | measured |
| Tokens per day, Coding agents | 1,000,000, 5 % of users | Anthropic, Claude Code 2026 | per vendor |
| Target speed per request | 30 tokens per second | Brysbaert 2019, MLCommons 2025 | Defined value |
| Models | |||
| small open model, around 8 billion parameters | 8 GB, 2,500 tokens per second per GPU | Meta Llama 3.1, NVIDIA NIM | per vendor |
| medium open model, 30 to 70 billion parameters | 70 GB, 250 tokens per second per GPU | SemiAnalysis InferenceX 2025 | measured |
| large mixture of experts model, over 100 billion parameters | 400 GB, 250 tokens per second per GPU | SemiAnalysis InferenceX 2026 | measured |
| Large model from this number of active users | 1,500 | MindsMachines 2026 | Defined value |
| GPU, power and prices | |||
| Memory per GPU | 141 GB | NVIDIA H200 | per vendor |
| Power per GPU | 700 W | NVIDIA H200 | per vendor |
| Base load per server | 2,500 W | Lawrence Berkeley National Laboratory 2024 | measured |
| Purchase per GPU including server share | 40,000 euros | Lenovo 2026, Supermicro 2026 | per vendor |
| Network and storage, one-time | 50,000 euros | DELTA Computer 2026, Geizhals 2026 | per vendor |
| Maintenance per year | 10 % of purchase | Lenovo 2026 | Defined value |
| PUE, own data centre | 1.5 | EnEfG § 11 | Legal standard |
| PUE, colocation | 1.4 | Bitkom 2025 | Forecast |
| Average utilisation | 45 % | Patel et al. 2024, Wilkins et al. 2026 | Defined value |
| Industrial electricity price | 21 cents per kWh | Eurostat 2026 | measured |
| Path A, per 1 million tokens | 3 euros | Azure, AWS, Google, Mistral 2026 | per vendor |
| Path B, per GPU hour | 2.75 euros | Open Telekom Cloud 2026 | per vendor |
| Staff | |||
| Path A, positions | 0.3 plus 0.2 per 1,000 users plus 0 per GPU | MindsMachines 2026 | Defined value |
| Path B, positions | 1 plus 0.2 per 1,000 users plus 0.03 per GPU | MindsMachines 2026 | Defined value |
| Path C, positions | 2 plus 0.2 per 1,000 users plus 0.06 per GPU | MindsMachines 2026 | Defined value |
| Cost per full-time position | 93,000 euros | Destatis 2025, Hessisches Statistisches Landesamt 2025 | measured |
| Freely available share of the IT team | 10 % | MindsMachines 2026 | Defined value |
Assumptions as of 26.10.2026.
OneMachine
A tailored solution on each of the three paths
The tailored solution runs in your tenant or data centre, with your roles, with logging and without vendor access to content. Updates, monitoring and security patches are included in the licence.
The documented operating path is Microsoft Azure, other environments are supported. You clarify which path fits your company in the Architecture and Security Call.
Models via EU API
OneMachine in your environment, models hosted in the EU with a data processing agreement.
GPU in a German cloud
Dedicated GPU from a provider in Germany, open models.
GPU in your own data centre
Your own GPU servers on premises, full control over hardware and models.
Your next step
Go through your result with an architect
In the Architecture and Security Call, you check your calculation result against your environment. The outcome is clarity on operation in your own tenant, access model, roles and logging.
- Architecture and Security Call, 30 minutes, online
- Operation in your own tenant or data centre
- Access model, roles and logging
The platform
OneMachine runs in your tenant
Data and logs stay in your environment, on paths B and C the models as well. MindsMachines has no access to content.
