pricing
Husk costs nothing.
Not a free tier, not a trial, not a community edition. The whole product is Apache-2.0 and runs on hardware you already own.
npx -y @husk-ai/cli doctorWhy there is no paid tier yet.
Husk is a runtime that turns a machine you already own into something an agent can drive. Nobody has to pay for that, because nobody is paying for the machine twice. The local provider is the primitive and every hosted provider is a plugin behind the same interface, so there is no code path that requires an account — which means there is nothing to gate.
Charging for a runtime with no server in it would mean building one artificially: a licence check, a seat count, a thing that phones home to ask whether you are allowed. That is a server we do not want to run and a network call we have promised is not there.
It also breaks the way people evaluate a tool like this. The claim on the homepage is meant to be checked in ten seconds on the reader’s own laptop. A signup between the claim and the check is not a business model, it is friction charged to the one person who was going to verify us.
what you pay for, if anything
- Husknothing, ever, on any provider
- local modelsnothing — Ollama runs gemma, qwen or llama on your machine
- hosted modelswhatever Anthropic, OpenAI, Google or Groq charge you directly. Husk never sits in that transaction
- flyFly’s metered machine time, billed by Fly, with your own token
- sshwhatever your box costs, which for an Oracle Always Free ARM instance is nothing
What a hosted tier would have to add.
If Husk is ever charged for, it will be for work that genuinely costs someone money to do, and it will sit beside the free path rather than on top of it. Four things would qualify, and none of them exists today:
- a control planemore than one person sharing husks, with roles, an audit log and revocable credentials. v1 is single-user by design and says so
- always-on triggersa cron husk that keeps running when your laptop is shut. That is somebody’s server, and somebody has to pay for it
- managed computepooled warm machines with faster cold starts than a local Docker daemon can give you
- supporta contract, a response time, and someone whose job it is to answer. That is a real cost and an honest thing to sell
The commitment that constrains all of it: the free path always works. No feature ships that makes the no-account, no-key, no-Docker path worse. The same husk.yaml that runs on your laptop today runs on someone else’s machine later without being rewritten, and the day that stops being true is the day the promise has been broken.
not on the roadmapA paid feature that removes a limit Husk invented in order to sell removing it. Step, cost and token ceilings exist because a loop that spends your money unattended is a bug; they are not a meter.
The licence is the whole agreement.
Apache-2.0. Fork it, ship it, run it inside your company, put it in a product you sell. There is no contributor licence assignment that quietly makes it someone else’s, and no clause that turns into a licence fee at a headcount.
Read the source — or start with why any of this is shaped this way.