# What it costs to run it yourself — Hanzo

> The open-source stacks people reach for, priced from the compute their own compose files reserve, and the operating work that is not a line item.

Comparison

# Buy it, or run it

Everything Hanzo does is open source, so the honest question is not whether you could run it — you could — but what that costs. These are real numbers from real compose files.

## Run it yourself, and here is the bill

The open-source stacks people reach for, priced from the compute their own compose files reserve.

Reading the stacks and what they cost from api.hanzo.ai

## And the part that is not a line item

The machines are the cheap half. This is what you are holding once they are paid for.

Upgrades

Every image above has a release cadence, and a CVE in any of them is yours to notice and roll.

Backups

Taking one is a cron. Proving a restore works is a rehearsal, and it is the half that gets skipped.

Availability

One replica of each is a single point of failure. A second is roughly twice the compute plus the state problem.

Identity

Each of these has its own users and its own idea of an admin. Joining them is a project.

On-call

Someone answers when it pages at 3am, and that person is on your payroll.

We have not costed that list, and will not: an invented engineer-hours figure would be worth less than the arithmetic you can do yourself, knowing your own team. What Hanzo replaces is the whole column — one identity, one bill, one thing that pages someone else.