Document the billed All-in-One and the license bundle, drop the retired Secret

[M2Night]

What was wrong

all-in-one.mdx stated "It is offline-only: there is no hosted-billing variant."
There is one now — the same container with the billing implementation compiled the
other way. introduction.mdx said the engine ships in three forms; the dashboard
grants four. And no self-hosting page mentioned the license bundle, which every
delivery form now requires before it serves — a reader following these pages would
deploy and watch it fail with no explanation.

What changed

The billed All-in-One

Page
all-in-one.mdx	Removed the false claim. The page now opens on the two forms, splits Usage accounting into air-gapped and billed, and qualifies the volume — only one form writes a ledger.
introduction.mdx	"three forms" → four, and the comparison table gains the column. The capability table keeps one appliance column, labelled "both forms", because the two are identical there — a duplicated column would be six identical cells.
requirements.mdx	The All-in-One host table had no network row at all. Added one: the billed form needs outbound HTTPS for every request, not only at startup.
air-gapped.mdx	"The All-in-One appliance is the straightforward answer to a strict air gap" now names the air-gapped form, and says its counterpart cannot air-gap.
enterprise-releases.mdx	Notes that the two appliance forms are versioned independently — the Helm sentence next to it says both Helm forms share a version, which invites the wrong inference.

The license bundle

Page
registry-access.mdx	The Self Host page's list gains the bundle: what it is, and that GPU-bound contracts need the card UUIDs at request time.
kubernetes.mdx	The pre-install Secrets are three, not two: the JWT secret is gone (nothing has read it since API-key auth replaced the scheme, and the chart no longer asks for it), the license bundle arrives. What it gates and a link to renewal.
all-in-one.mdx	A fourth item under "what running it involves": the mounted bundle, the failure without it, and renewal by replacing the files.
requirements.mdx	A license row in each half: the Kubernetes platform baseline and the All-in-One host table.
operations.mdx	License validity/expiry in the monitoring signals (metrics first, log warnings second); a License renewal section — in place, no restarts, mixed responses for up to a couple of minutes, and the one exception (a bundle carrying a new key); three troubleshooting rows for the three distinct failure shapes (Secret absent, file unreadable, certificate expired).
air-gapped.mdx	The bundle crosses the boundary too, and unlike an image it expires — a recurring transfer, not a one-off.

Disclosure

No hostname, image tag, chart version, Secret name, mount path, or timing internal
appears in any added line — the billing endpoint stays "ask your account team for the
hostname to allowlist", and the license text stays at behavior level (renewal cadence
is "a couple of minutes", not the components' verification interval).

Checks

Every table in developer-guide/self-hosting/ is column-consistent; every internal link
and anchor in the changed files resolves to a page and heading that exist
(operations#license-renewal is new and linked once, from kubernetes.mdx).

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
hanabiaiinc	🟢 Ready	View Preview	Aug 25, 2026, 4:17 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: dd6ad1de-0f1c-4efd-9b62-5607f38fb89b

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}