Five SKUs · Scope-priced · Access by request

KYE GovernedUI™ SKU ladder — paid to prevent uncontrolled AI-agent execution.

We don't publish per-seat or per-month figures. Every deployment is scope-priced — bound to a specific set of governed agents, engines, rails, protected systems, and regulatory exposure. Submit an access request below; an admin reviews your scope and returns a tailored quote with an embedded action button to accept, request changes, or schedule a deep-dive call.

SKU 1 — KYE GovernedUI™ Pilot

KYE-GUI-PILOT-001

One bounded AI-agent workflow. 8–12 weeks. Fixed-scope engagement.

Bundles:

  • Agents — one agent class (sales / support / payments / data export).
  • Engines — Decision Engine + Evidence Engine + Audit Chain.
  • Rails — Authority Rail + Evidence & Replay Rail.
  • GovernedUI modules — Action Approval · Authority Scope · Evidence Timeline.
  • Demo — live sandbox tenant + reference Gateway integration.
  • Stripe — one-time scoped engagement invoice.
  • Outcome — signed pilot evidence report.

Request access — Pilot

SKU 2 — KYE GovernedUI™ Department

KYE-GUI-DEPT-001

One business unit. 3–5 agent classes. 3–5 protected systems.

Bundles:

  • Agents — 3–5 agent classes in one BU.
  • Engines — full 10-engine stack on the BU's tenant.
  • Rails — Operating Model + Authority + Purpose + Runtime Decision + Evidence & Replay.
  • GovernedUI modules — full 11-module suite.
  • Demo — per-BU sandbox tenant + SSO/SCIM enablement.
  • Stripe — annual subscription, signed signed-meter receipt monthly.
  • Outcome — production GovernedUI for one BU.

Request access — Department

SKU 3 — KYE GovernedUI™ Enterprise

KYE-GUI-ENT-001

Company-wide AI-agent governance. Multi-department deployment.

Bundles:

  • Agents — unlimited classes across departments.
  • Engines — full stack with cross-department evidence aggregation.
  • Rails — all 7 rails.
  • GovernedUI modules — full suite + custom policy templates + reviewer roles.
  • Demo — multi-tenant sandbox + dedicated integration engineer.
  • Stripe — annual subscription + true-up clauses.
  • Outcome — Tier-1 enterprise AI governance plane.

Request access — Enterprise

SKU 4 — KYE GovernedUI™ Regulated Infrastructure

KYE-GUI-REG-001

Banking-grade. WORM audit chain. Cross-tenant evidence packs. Sector policy packs.

Bundles:

  • Agents — regulated-class agents with two-person + two-person-with-legal approval modes.
  • Engines — full stack + WORM-anchored audit chain + object-store immutability retention.
  • Rails — all 7 rails + Edge Governance + Reconciliation Engine.
  • GovernedUI modules — full suite + Critical Point Review + Two-Person-with-Legal Approval + Evidence Pack™ Export for Regulator.
  • Frameworks — SR 11-7, EU AI Act Art. 14–15, DORA, ISO 42001, PSD2/3, PCI DSS, HIPAA, NIS2 control mappings.
  • Demo — BYOC / private deployment, dedicated storage, signed evidence packs replayable offline.
  • Stripe — annual + premium support tier.
  • Outcome — regulator-ready AI control plane.

Request access — Regulated

SKU 5 — KYE GovernedUI™ National / Consortium

KYE-GUI-NAT-001

National AI programs, bank consortia, regulatory sandboxes, cross-industry agent registries.

Bundles:

  • Agents — multi-tenant agent registry across organisations.
  • Engines — full stack + federated audit chain + cross-org evidence projection.
  • Rails — all 7 rails + Edge Governance + Reconciliation + Federation.
  • GovernedUI modules — full suite + Regulator Console + Public/Private Sector Evidence Bridge.
  • Demo — sovereign deployment, regulator access layer, sandbox governance.
  • Stripe — bespoke multi-year framework agreement.
  • Outcome — country/industry-scale AI control plane.

Request access — National

How pricing works

  • No public price tags. Public per-seat / per-month figures invite race-to-the-bottom and bypass the qualifying conversation that's required for any regulated deployment.
  • Scope-priced. Every SKU binds a specific bundle: agents × engines × rails × protected systems × frameworks × deployment topology. Two organisations with the same SKU can have meaningfully different scopes.
  • Stripe-backed. Once scope is agreed, billing is via Stripe (Stripe Billing for subscriptions, Stripe Invoicing for one-time pilots). Every charge is bound to a signed meter receipt (kye.billing.bps_event.v1).
  • Procurement-cycle ready. SKUs are designed for enterprise procurement (POs, DPAs, sub-processor lists, security reviews) — not a credit-card flow.
  • Pilot credit. 100% of the pilot fee credits against the first-year annual licence if you upgrade within 60 days.

What happens when you submit an access request

  1. You submit the form in the modal — company, role, scope (agents / systems / business units), regulatory exposure, target SKU.
  2. The form posts to the engagement API, which emits a signed access-request evidence event into the audit chain and dispatches an email to the maintainers.
  3. Admin reviews in the admin console. The same submission appears in the GovernedUI Approval Queue.
  4. Admin returns a tailored quote via an embedded-action-button email — you accept, request changes, or schedule a call directly from the email. The action buttons are signed; no third-party trackers.
  5. If accepted, you receive Stripe payment links bound to the agreed scope. Once paid, your tenant is provisioned and the bundle's modules go live.

Adjacent paths