From procurement and authorization to metering, one gateway governs the full capability lifecycle.
Skills and plugins keep a single source of truth for manifest, version and status. .tueopkg uploads pass validation (semver / capability declaration / payload integrity) and packages are stored by sha256 content addressing.
Ed25519 cryptographic signatures derive three trust tiers: official / partner / community. A declared signature that fails verification means tampering or impersonation, and installation is refused.
Trial → request-approval → order (corporate / online) → finance confirmation → VAT invoice, with full audit trails. A budget gate holds every purchase, bringing AI capability procurement under enterprise purchasing policy.
Tenant-level encrypted credentials (AES-256-GCM) are decrypted and injected by the gateway at call time; neither users nor AI ever see the secret, and the same source is visible across hosts (cohort / studio).
Each call passes the install gate, the pay gate and the availability-scope gate, then dispatches by kind: action → executor sandbox, knowledge → direct injection. The pay gate and usage metering are welded into the gateway, so delegated calls pass the gates and are metered automatically.
The price lives on the product: operators set a global price and can override it with a B2B contract price per customer. Billing follows a fixed rule — perpetual license or subscription duration, never usage- or seat-based.
"Who can use it" is allocated by all-staff, department or person (sourced from the identity roster). The usage dashboard surfaces dormant entitlements — paid rights with zero calls is wasted spend — and answers "is this worth it".
A signed license file is the single root of trust with zero-network activation; a soft node lock binds to deploymentId (preventing copies across deployments without locking hardware and annoying customers). Air-gapped and online use the same mechanism.
The .tueoupdate unified update bundle (catalog plus platform components in one package) enters the intranet through a single import point; updates are idempotent by digest, rollback-capable, and default to bundle-runtime with no image needed.
From declaration to runtime enforcement, every step is visible and controllable.
The package read-only declares the permissions and high-risk actions it requires.
High-risk permissions are flagged with red chips, visible at a glance before procurement.
Granting happens at installation time, not as a toggle at publish time.
Executor runners use unshare to cut network access; cross-repository changes are blocked.
Book a demo to see the full governance loop of procurement, authorization and metering.