YAA\F Ops

License Issuer

BeezLabs ops console — Keycloak yaaif-ops. Private key never leaves this machine.

Pending license requests

Raised from customer Admin UI via POST /v1/license-requests. Issue + Confirm a license for the installation, then the customer can Download from server.

Issued licenses

Confirmed activations stored in Postgres (…). Admins can regenerate (fresh JWT / new jti) or upgrade entitlements. Both require Generate → Confirm after customer activation.

Signing key

One long-lived issuer keypair. Generate once; reuse for every license.

Issue license

Paste identity JSON from ./scripts/installation/print-identity.sh (or Admin UI → About → License → Copy request JSON). Customer activates the JWT in Admin UI; api-server stores it in OpenBao installation/license. After activation, confirm below so this tool records the license in Postgres.

01 · Identity

Customer installation

Label is required before confirm. Identity binds the JWT to OpenBao fingerprint.

02 · Term & edition

License window

Edition presets fill capacity, credits, and features. Override any field before generate.

yaaif-v1 current · yaaif-v0 previous.

03 · Capacity

Installation limits

Hard caps enforced by api-server for tenants and desktop workers.

04 · Credit usage

Monthly allotment & costs

Each tenant independently inherits this monthly allotment. Costs are credits charged per unit.

Use -1 for unlimited, or enable the toggle.

05 · Features

Entitled surfaces

Edition change resets checkboxes to defaults. Integrations: teams, email, slack, lark, mcp_hosts, opencode.

License activity

Audit trail of license-related actions across all ops users (issue, confirm, label, keys, leases).

Ops users

Local grants for this issuer. Reader can browse licenses and activity (not auto-assigned). Admin can issue licenses and manage users. Blocked users cannot use the ops API.