Skip to content

Tools

The calculators and checklists from my articles, in one place. Put in your own numbers, then copy the link under a tool: it opens with exactly your inputs, for a colleague or for later.

Everything runs in your browser. Nothing you enter is sent anywhere; it is only in the link if you copy it.

Cloud and AI cost

Where a cloud or AI bill comes from, and the levers that cut it without anyone noticing.

Cloud bill estimate

A monthly estimate for a web app, a Kubernetes cluster or a data platform, split by what drives the cost.

Open as its own page

Interactive

What will the cloud bill be?

Start from a typical setup and change the sizes. You get a monthly estimate at Azure list prices, split by what drives it, and the lever for the biggest part.

Typical setup (example sizes)

$3,181

per month, list price

Compute

biggest cost driver

53%

of the bill

  • Compute$1,679 · 53%
  • Logs$909 · 29%
  • Database$310 · 10%
  • Data transfer$165 · 5%
  • Disks$108 · 3%
  • Object storage$9.80 · 0%

Lever for the biggest part: Compute

Size requests on real load and switch non-production off outside working hours.

Kubernetes right-sizing

Azure West Europe, pay-as-you-go list prices in USD as of 8 November 2026 (Azure Retail Prices API): compute at D4s v5 Linux, disks at Premium SSD P10, database at PostgreSQL flexible server General Purpose (compute only), data transfer via the Microsoft network after 100 GB free, logs at Log Analytics Analytics logs. Not included: reservations, licences, backup, support, taxes.

Azure Retail Prices API

AI token costs

What an AI feature costs per month on each model, and how much caching and routing save.

Open as its own page

Interactive

What does an AI feature cost per month?

Put in your traffic and prompt sizes. You get the monthly bill on your model, on all current models, and what prompt caching and routing simple requests to a small model save.

Answers can wait (batch API, −50%)

$547

per month, no caching or routing

$547

per month with your caching and routing

0%

saved by caching and routing

The same traffic on every model (with your caching, without routing)

  • Claude Haiku 5.5 Anthropic$27
  • GPT-6 Luna OpenAI$27
  • Gemini 3.5 Flash-Lite Google$112
  • GPT-6.1 Terra OpenAI$274
  • Gemini 3.8 Flash Google$410
  • Claude Sonnet 5.5 Anthropic$547
  • GPT-6.1 Sol OpenAI$547
  • Claude Opus 5.5 Anthropic$1,094
  • Gemini 4 Argon Google$1,094
  • Claude Fable 5.1 Anthropic$2,736
  • GPT-6 Astra OpenAI$2,736

Standard list prices per million tokens as of 8 November 2026. Not included: cache writes, long-context surcharges, tool and search fees, taxes. Gemini 4 Argon and 3.8 Flash show their regular prices; introductory discounts run until 30 November and 31 December 2026. Prices change: check the pricing pages before you budget.

Anthropic · OpenAI · Google

Reservation or savings plan: break-even

From which utilisation a commitment pays off, with the return rules of Azure and AWS.

Open as its own page

Interactive

Does the commitment pay off?

A reservation or savings plan is cheaper per hour, but you pay for it whether you use it or not. Here is the utilisation from which it pays off, and what is left over the term.

Commitment

Term

65%

break-even utilisation

+€1,000

net per month

+€36,000

net over the term

If plans change: Azure reservation

Exchanges are possible. Refunds too, but cancelled commitments can't exceed USD 50,000 in a rolling 12-month window per billing profile or enrollment.

Microsoft Learn

My rule: buy after right-sizing, and only for the base that has run steadily for months. Below break-even you pay for capacity you don't use.

Log retention cost

What your log volume and retention cost on Azure, AWS and Google Cloud, and which lever is bigger.

Open as its own page

Interactive

What do your logs cost?

Log volume and retention, priced on Azure, AWS and Google Cloud. Most of the time the bill comes from what you write, not from how long you keep it.

Retention

ServiceWritingKeepingPer month
Azure Log Analytics$909$77$986
AWS CloudWatch Logs$192$29$221
Google Cloud Logging$127$6.00$133

Writing is 87–95% of the cost here: logging less (debug levels, health checks, noisy services) saves more than shorter retention.

List prices in USD as of 8 November 2026: Azure Log Analytics (Analytics logs, West Europe, 31 days included), AWS CloudWatch Logs (Standard, Frankfurt; storage billed on compressed size, so this is an upper bound), Google Cloud Logging (30 days included, first 50 GiB per project and month free; GiB counted as GB). Azure and AWS free allowances, cheaper log tiers and archive options are not included.

Azure Retail Prices API · Azure Monitor Logs · AWS CloudWatch · Google Cloud

Non-production off at night

How much you save when dev and test environments only run during working hours.

Open as its own page

Try it: non-production off at night

€3,214

saved per month

€38,571

saved per year

Dev and test run 12 hours on weekdays: 60 instead of 168 hours a week. Rebuilt automatically every morning.

Interactive

How many nodes do your requests really need?

Move the sliders to your numbers. Requests decide where pods fit, so oversized requests buy nodes nobody uses.

Node size

5

nodes today

2

nodes after right-sizing (200m)

60%

less node capacity

CPU only, about 90% of a node is allocatable, at least 2 nodes for availability. Check memory the same way before you remove a node.

Local and private AI

Sizing hardware for your own models, and checking an isolated setup.

Which device for a local LLM?

Model size and users in, the smallest machine that holds it out: mini PC, Mac, DGX Spark, workstation or GPU server.

Open as its own page

Interactive

Which device for a local LLM?

Pick a model and how you will use it. You get the memory it needs and the smallest machines that hold it, from a mini PC to a GPU server.

Start from

Precision

Who uses it

≈ 42 GB

memory needed

128 GB

memory in the smallest setup that fits

Smallest setup that fits

Mini PC with AMD Ryzen AI Max+ 395

The cheapest route to a lot of memory: up to 128 GB of 256-bit LPDDR5x-8000 (about 256 GB/s) shared with the Radeon 8060S graphics, 45 to 120 W. Runs llama.cpp, LM Studio and Ollama.

≤ 7 tokens/s, upper limit for one user on that machine

All options, roughly from small to large investment

  • PC with GeForce RTX 5090Too small

    Fast for models that fit into 32 GB. A consumer card: loud, hot, no ECC memory, 575 W total graphics power.

  • Mini PC with AMD Ryzen AI Max+ 395Fits · 128 GB

    The cheapest route to a lot of memory: up to 128 GB of 256-bit LPDDR5x-8000 (about 256 GB/s) shared with the Radeon 8060S graphics, 45 to 120 W. Runs llama.cpp, LM Studio and Ollama.

    ≤ 7 tokens/s, upper limit for one user on that machine

  • NVIDIA DGX SparkFits · 128 GB

    GB10 superchip with 128 GB unified memory and the full CUDA stack. 273 GB/s limits large dense models; strong for mixture-of-experts models, development and fine-tuning experiments.

    ≤ 8 tokens/s, upper limit for one user on that machine

  • Mac Studio M5 MaxFits · 128 GB

    Up to 128 GB unified memory at 460 to 614 GB/s, and quiet. MLX, llama.cpp, Ollama and LM Studio run well on it.

    ≤ 13–18 tokens/s, upper limit for one user on that machine

  • Workstation or server with RTX PRO 6000 Blackwell (1–2)Fits · 96 GB

    96 GB ECC GDDR7 at 1,792 GB/s and 600 W per card: the fastest per user. One or two of them with vLLM make a server for a team.

    ≤ 51 tokens/s, upper limit for one user on that machine

  • Rack server with 2× L40SFits · 96 GB

    Two 48 GB data-center GPUs with vLLM in front: the other team setup from the article for 30B to 70B models.

  • Mac Studio M5 UltraFits · 512 GB

    Up to 512 GB unified memory at 1.2 TB/s, at most 480 W continuous: the simplest way to fit a very large model on a desk.

    ≤ 34 tokens/s, upper limit for one user on that machine

  • NVIDIA DGX Station (GB300)Fits · 748 GB

    A deskside machine with the GB300 superchip and 748 GB of coherent memory, 252 GB of it HBM3e.

  • GPU server with H200 (up to 8)Fits · 141 GB

    141 GB HBM3e at 4.8 TB/s and up to 700 W per GPU; eight of them give over a terabyte. vLLM splits the model across the GPUs.

  • NVIDIA DGX B200Fits · 1,440 GB

    Eight B200 GPUs with 1,440 GB HBM3e and 64 TB/s in total, at about 14.3 kW for the system. Power, cooling and operations become the bigger project.

Planning estimate, not a benchmark. Memory = parameters × bytes per parameter, plus about 20% for the KV cache (long documents or a few people: +50%, a team: +100%, rough factors). Unified-memory machines keep about 10% for the system. The speed limit is memory bandwidth divided by the weights read per token (only the active ones for mixture-of-experts); real numbers are lower. Device figures from the vendors' spec pages, as listed in the article (Ryzen bandwidth calculated from AMD's 256-bit LPDDR5x-8000). Before buying, test your model and prompts on rented GPUs for two weeks.

Help choosing the hardware

GPU memory for a local LLM

Which GPU, and how many, a model needs before you buy hardware.

Open as its own page

Interactive

Which GPU does your model need?

Pick a model size and precision. Weights take parameters × bytes per parameter; about 20% on top covers the KV cache for normal context lengths.

Model size (billion parameters)

Precision

≈ 19 GB

GPU memory needed

1×

fits on 24 GB (RTX 4090)

  • 1× 24 GB (RTX 4090)
  • 1× 32 GB (RTX 5090)
  • 1× 48 GB (L40S)
  • 1× 80 GB (H100)
  • 1× 96 GB (RTX PRO 6000 Blackwell)
  • 1× 141 GB (H200)

Rule of thumb for planning, not a benchmark. Long contexts and many parallel users need more KV cache; 4-bit costs a little quality.

Mixture-of-experts hosting

Why these models need the memory of a big model but compute like a small one.

Open as its own page

Interactive

What does a mixture-of-experts model cost to host?

All experts must sit in GPU memory, but each token only runs through the active ones. Memory scales with total parameters, speed with active parameters.

Precision

≈ 428 GB

weights in GPU memory

7

80 GB GPUs, minimum

23B

compute per token, like a dense model this size

Planning estimate: weights plus about 15% for KV cache and runtime. Real throughput depends on batch size, interconnect and the serving engine.

Air-gap check

Where an isolated environment still has gaps, as a to-do list.

Open as its own page

Interactive

Is your air gap more than a firewall rule?

Tick what your enclave already has. The gaps are where audit findings and outages usually start.

0/10 ready

Your next three steps

  1. A written threat model: what must never leave, what must never come in
  2. One defined transfer path with scan, checksum and signature check
  3. A private registry mirror that only accepts signed images
Talk about your air-gapped setup

AI in your team

From a prototype built with AI to coding agents your team can trust.

Production readiness

What is still missing before an app built with AI tools can run for real customers.

Open as its own page

Interactive

Is your AI-built app ready for production?

Tick what is already true. The gaps that are left are your to-do list, in order.

0/12 ready

Your next three steps

  1. Code lives in Git; changes go through pull requests
  2. No secret keys in the frontend; server keys only on the server
  3. Row-level security (or equivalent) on every table
Get a production-readiness review

/goal, /loop or routine

Which way of running a coding agent fits the task you want to hand over.

Open as its own page

Interactive

Which mode fits your task?

Answer three questions about the task you want the agent to take off your hands.

  1. 1.Does it have a finish line a machine can check (tests green, file exists, metric reached)?

  2. 2.Should it repeat on an interval or keep watching something?

  3. 3.Must it run while your laptop is off, or start from a schedule, an API call or a GitHub event?

Codex safety settings

The sandbox and approval settings for each situation, ready to copy.

Open as its own page

Interactive

Which Codex settings fit your task?

Pick the situation. You get the sandbox mode, the approval policy and the config to copy, using the setting names from the Codex docs (November 2026).

workspace-write

sandbox_mode

on-request

approval_policy

The docs' lower-risk automation preset: edits inside the workspace, asks before anything else.

# ~/.codex/config.toml
sandbox_mode = "workspace-write"
approval_policy = "on-request"

[sandbox_workspace_write]
network_access = false

Copilot, Claude Code or Codex

How the three coding agents differ, on the points you care about.

Open as its own page

Interactive

Compare the three side by side

Pick what matters most to you. Facts as of November 2026, from the vendors' docs and changelogs listed under sources.

GovernanceGitHub Copilot: AI controls with agent audit logs; enterprise-managed permissions for shell, files and networkClaude Code: Managed settings (file, MDM or server-managed): deny rules, no bypass mode, allowed MCP servers and modelsOpenAI Codex: requirements.toml: allowed approval policies, sandbox modes, web search, hooks and MCP servers
Best fitGitHub Copilot: Teams standardised on GitHub who want agents inside their existing reviewsClaude Code: Platform and DevOps engineers running long, autonomous workOpenAI Codex: Companies already living in ChatGPT Business or Enterprise

Claude plan finder

Which Claude plan matches how you or your team work.

Open as its own page

Interactive

Which Claude plan fits how you work?

Pick the description closest to you. Plans and prices as of the change on 30 October 2026 (USD), from Anthropic's pricing page and help center.

Max

Price
$100/month (monthly only)
Usage
5× Pro per 5 hours and per week
Also included
$100 API credits a month (API, Agent SDK, not Claude Code); Fable up to half the weekly limit

Visible in AI answers (GEO)

Whether ChatGPT, Gemini and Google's AI Overviews can find and name your brand.

GEO readiness

How ready your brand is for AI answers, with the most important gaps first.

Open as its own page

Interactive

How ready is your brand for AI answers?

Tick what is already true. What's left is your GEO to-do list, most important first.

0/10 ready

Your next three steps

  1. Brand facts are identical on the site, Google Business Profile, LinkedIn and directories
  2. Key pages answer the main question in the first paragraph
  3. Organization or LocalBusiness structured data on key pages
Get a GEO visibility check

What customers ask an AI

Example questions for your industry and city, as a starting point for prompt research.

Open as its own page

Interactive

What do your customers ask an AI?

Pick an industry and the intents you care about. These examples come from templates in your browser; real prompt research generates hundreds per page with an open model on your sitemap.

Industry

Intent

  1. What is the best restaurant in Munich?
  2. Which restaurant in Munich do locals recommend?
  3. Compare the top three restaurant options in Munich by price and reviews
  4. Your brand or another restaurant in Munich: which is better for a small team?
  5. Where can I book a restaurant in Munich for this weekend?
  6. Find a restaurant in Munich with availability tomorrow

    Get in touch

    Tell me what you're building. I'll reply within 1–2 business days.

    Dominik Heinrich
    Company
    MADO Consulting

    Available worldwide, remote. On-site on request, depending on the country.

    I reply within 1–2 business days. Free slots: see the calendar

    Opens Calendly's booking calendar here. Loading it sends data to Calendly (see Impressum).