Licensing & billing — AiHummer Docs

AiHummer is a self-hosted product with a commercial licensing model. Every install runs — with no license and no account — on the free Community tier; a paid plan unlocks higher limits and enterprise features. Enforcement lives entirely in your own gateway (nothing about your data leaves your host), and it fails closed to Community: a missing, tampered, or expired license resolves to the free tier, never to unlimited.

Plans

An “AI employee” is a configured agent/persona. Plans are the single source of truth shared by the gateway and the pricing page.

Plan	AI employees	Tenants	Channels	Enterprise features
Community (free)	2	1	Core channels only	—
Starter	3	1	All channels	—
Business	5	1	All channels	White-label, RBAC, audit
Enterprise	Unlimited	Unlimited	All channels	+ SSO, RLS, SLA

A signed license may also carry explicit MaxSeats / MaxTenants / Features overrides that take precedence over the plan defaults.

How a license reaches your instance

Licensing is instance-centric and requires no manual token juggling in the common case:

Auto-registration. On first start the gateway registers itself with the vendor fleet service over an authenticated, TLS-pinned message bus. With no license it registers as Community — this is expected and requires nothing from you.
Buy / manage a plan in your personal account at my.aihummer.ru. The vendor sets your instance’s plan.
License push. Billing signs a fingerprint-bound license for your specific instance and pushes it to the gateway over the bus. The gateway verifies the signature against a trust root baked into the binary and applies the new entitlements live — no restart, no copy-paste.

The signed license is bound to your instance fingerprint, so it cannot be reused on another host.

Air-gapped fallback: a detached token

If your instance cannot reach the bus (a fully air-gapped network), the vendor can issue a detached license token you install manually:

aihummer license show          # inspect the current license / plan

Paste the issued token via the admin Web UI (or the environment the installer documents) and the gateway verifies and applies it the same way. The token is still fingerprint-bound to your instance.

The 402 upgrade flow

Enforcement is soft: existing resources are never disabled or “bricked”. Only a new action that would exceed your plan is blocked, and it returns HTTP 402 Payment Required with a machine-readable body:

{
  "error": "Plan limit reached: your plan allows 2 AI employees.",
  "code": "plan_limit",
  "feature": "ai_employees",
  "upgrade": "https://aihummer.ru/pricing/"
}

For example, creating a 3rd AI employee on Community, enabling a non-core channel, turning on white-label branding, RBAC, or audit-read below the required plan all return this response. The admin Web UI surfaces the upgrade link so an operator can move to a higher plan; already-created resources keep working.

[!NOTE] Plan-limit / billing responses use this dedicated 402 plan_limit shape and are not part of the general AIH-* error-code registry — they are documented here.

The personal account

Plans, payment, billing details and closing documents live in your personal account at my.aihummer.ru. After a purchase or renewal the license reaches your instance automatically over the bus — as a self-hosting customer you interact with licensing through your own gateway and, when needed, the detached-token fallback above. For plan-change questions, reach the vendor via the admin UI’s “Support” page.

Where enforcement runs

In your gateway only. Entitlements are re-derived by re-verifying the signed license on every check; there is no single removable “if licensed” switch.
Fail-closed. Any untrusted license → Community, never unlimited.
Soft. New over-limit actions are blocked (402); existing resources are untouched.