On-Prem AIFree calculatorPDF, Excel, Word export

ChatGPT vs On-Prem LLM TCO Calculator

Hosted APIs are cheaper at low volume, and owned GPUs are cheaper at high, steady volume. This calculator puts both on one yearly basis so you can see where the lines cross for your workload.

Your numbers

users
days
tokens
$

Weighted average of input and output list prices for your expected mix

$
4 years
kW
$/kWh
FTE

Share of one engineer for patching, monitoring, model updates and support

$
% of capex per year

Your results

Hosted API cost per year
$14,000
On-prem cost per year
$50,979
Tokens per year
4,000,000,000
Hardware depreciation per year
$15,000
Power and cooling per year
$3,679
Assumes continuous operation and a facility overhead factor of 1.4
Operations staff per year
$27,500
Support and spares per year
$4,800
Break-even tokens per year
14,565,485,714
Above this yearly volume the on-prem server is cheaper, if one server can serve it

On-prem cost is shown for one server and does not rise with users, so check capacity in the GPU sizing calculator. Excludes software, networking, redundancy, one-time integration work, model evaluation effort and data transfer. Hosted API prices change frequently.

Save results:

Annual cost vs active users

Sweeps Active users from 25 to 3000, holding your other inputs fixed.

Pressure-test your TCO case

Send your inputs and we will review the assumptions, add what is missing and compare against a benchmarked open-weight setup.

Optional. The tool and every export work without this. No spam.

How to use it

Enter your expected user count, questions per day and total tokens per question including retrieved context. Use the blended API price that matches your input and output mix. For the on-prem side, enter a server price you have quoted, its power draw and the share of an engineer who will run it. The outputs show yearly cost for each path, and the break-even token volume at which they match.

The method

API cost is tokens per year divided by one million, times the blended price. On-prem cost is straight-line depreciation plus power with a facility overhead factor, a staff allocation and annual hardware support. The two paths scale differently: API cost grows with every token, while a server has a fixed cost until you hit its capacity, then needs a second one. That is why the chart shows a flat on-prem line against a rising API line.

  • Include staff time, which is often the biggest on-prem line
  • Include a spare or second node if the assistant becomes business critical
  • Price the API on the model quality you actually need

Reading the result

With the defaults, the hosted API costs far less than the server at 400 users. The lines cross at much higher volume, which is why a pilot should almost always start on an API or a rented GPU. On-prem wins on cost mainly when usage is heavy and constant, such as agents running overnight batches. It can also win on non-cost grounds: data that may not leave your network, export control, latency inside the plant, or independence from provider pricing.

Common mistakes

Comparing the API bill with the server price alone leaves out staff, power and support, which flatters on-prem. The opposite error is ignoring agent loops, which can multiply tokens tenfold and move the break-even a long way. Do not compare a small open-weight model with a frontier API without testing quality. Re-run the numbers each year, as both token prices and GPU prices keep moving.

Frequently Asked Questions

When does on-prem become cheaper?

When yearly token volume exceeds the break-even shown and one server can handle the load. That generally means large user bases, heavy agent workloads or batch processing, rather than light chat usage by a few hundred people.

Is cost the only reason to go on-prem?

No. Data control, export-control rules, air-gapped sites, latency and vendor independence often decide it. Many companies pay more for private deployment because the data cannot be sent to a public service.

What about renting GPUs instead?

Renting converts capex to a monthly fee and suits pilots and uncertain demand. Replace depreciation with the rental cost for a quick comparison, and check that data residency and contract terms fit your needs.

Do open-weight models match ChatGPT quality?

For many ERP lookup, summarization and drafting tasks they are adequate, but results vary by task. Evaluate candidate models on your own questions before using cost as the deciding factor.

If you want the numbers checked against your own prompts and a quoted server, we can benchmark open-weight models on your workload and help you build the case.