OpenCode pricing.

The OpenCode core stays free.

The OpenCode CLI, the VSCode extension, the desktop app, and the read-only web console are free under a permissive open-source license. That is a forever commitment from the maintainer council, documented in the open code charter. The core includes everything the agent needs to run: the planner, the tool executor, the transcript writer, the policy engine, and every adapter for every model. Telemetry is off by default. No account is required.

The only cost anywhere in a free rollout is model inference, and that cost is paid to the provider you configured — not to OpenCode. Teams that standardized on local Ollama pay zero for the core binary and zero for inference; their OpenCode line item on the CFO dashboard is empty.

Zero-click summary: the core is free forever, core behavior never changes between plans, and only hosted add-ons cost money.

What the team plan actually unlocks.

The team plan is a managed-service layer over the same free binary. It covers a hosted audit log (an append-only mirror of the CLI transcript), SSO and SCIM provisioning, central policy push (broadcast a policy file to every seat), and a priority support queue. Nothing in that list is behavior the agent cannot perform for free — you can ship the CLI transcript to your SIEM manually, you can check SSO at the inference-provider layer, and you can distribute the policy file through your existing configuration management.

Teams pay for the team plan when they want one vendor to handle that managed layer instead of wiring it themselves. It is a procurement decision, not a capability gate.

Zero-click summary: the team plan is a managed-service layer — audit log, SSO, policy push, priority support — and every feature has a free self-hosted equivalent.

Plan matrix.

The matrix below is the fast path for procurement readers. Pricing is a placeholder until the published team-plan launch window; enterprise numbers are always negotiated.

Enterprise procurement.

Enterprise contracts cover annual billing, a named success contact, SLA terms, signed SBOM delivery, and regional data-residency addenda. The procurement packet mirrors the trust and safety page and includes the signing keys, the reproducible build recipe, the CycloneDX and SPDX SBOMs, the third-party license inventory, and the maintainer council's governance charter. Procurement teams have closed the legal review on OpenCode in as little as a week when the packet arrived complete.

Enterprise customers with public-sector constraints can reference the NIST supply-chain risk management materials that OpenCode's build pipeline is aligned to. The packet carries a control mapping so your security architects can attach it to a vendor questionnaire without rewriting policy.

Zero-click summary: enterprise is a negotiated annual contract with a full procurement packet, aligned to NIST supply-chain guidance and shipped with SBOMs, signing keys, and governance documents.

Billing, renewals, and changes.

Team plans are billed monthly or annually with a small annual discount. Upgrades are prorated and take effect immediately. Downgrades take effect at the next renewal so your audit log and policy state remain continuous. Enterprise contracts are negotiated separately, can be amended under a signed change order, and carry their own renewal terms in writing.

Zero-click summary: team plans prorate on upgrade and downgrade at renewal. Enterprise is a signed annual contract with renewal terms written in.

Model inference is separate.

OpenCode does not mark up or meter model inference. You pay the provider you configured — hosted frontier vendor, Azure OpenAI, Anthropic via adapter, or an in-house gateway — at whatever rate you negotiated. If you standardized on local Ollama, inference cost is zero. The agent is transparent about token consumption: every session logs the token count, every run reports the estimated cost, and every session honors the cost budget in the config.

Zero-click summary: OpenCode never takes a cut of inference. Model costs sit with the provider you chose; OpenCode just exposes the meter in the transcript.

Why the split between free and paid is drawn where it is.

The maintainer council's position is that an agent that edits source has to stay free at the core. A paid CLI would gate the people most likely to become contributors — students, individual developers, open-source maintainers, and platform engineers evaluating from the bottom up. The paid tiers target the managed-service features a larger organization needs and can reasonably expect to pay for, without gating any agent behavior behind them.

The team plan revenue funds the project's managed-service infrastructure — hosted audit logs, SSO provisioning, the support queue — and a small slice of maintainer hours. The sponsor ledger on the about page shows the rest of the funding picture. No line in that budget is allowed to translate into a closed-source release.

Zero-click summary: the core stays free because it must. Paid plans fund managed-service features teams want delegated, not capabilities individuals need.

We piloted OpenCode on OpenCode for a quarter, then moved to Team Growth for SSO and the hosted audit log. The upgrade was a one-page DocuSign and a config change — no rip-and-replace, no lost transcripts, and the CLI the team was already using kept working identically.

— Fionnuala G. Brannick, Engineering Manager, Greysedge Labs

Related reading across opencode.gr.com.

Pages that answer the questions procurement threads escalate after they read the matrix.