Skip to main content

Overview

Kenaz Fleet is the optional hosted control plane for teams using the Kenaz Harness and Kenaz Workbench. It gives your organization a single place to manage members, roles, plans, and the shared configuration that gets pushed down to every member's Harness.

The key word is optional. The Harness and Workbench work fully on their own — Fleet is what you add when a team needs centralized visibility, governance, or shared configuration across its members.

What Fleet provides​

CapabilityWhat it means for your team
Org & team managementInvite members, organize them into teams, and assign roles (owner / admin / member).
Plans & billingSelf-serve sign-up for Pro (single seat) or Team (multi-seat). Manage payment, view invoices, and upgrade from the billing portal.
Config bundles pushed to the HarnessAdmins push shared configuration — routing policy, allowed/blocked tool connections, shared context — to every member's Harness automatically.
Shared context graphTeam-scoped context (facts, decisions, reference material) syncs across members so everyone works from the same knowledge base.
Audit & analyticsAggregate usage, adoption, and cost data across the org. Opt-in telemetry gives admins a picture of how AI tools are being used.

Who it's for​

  • Individual professionals on the Pro plan who want a personal Fleet dashboard with usage analytics and cost reporting.
  • Small and mid-size teams on the Team plan who need to manage members, share context across the team, and set guardrails for which AI providers and tools are used.
  • Enterprises who need SAML SSO, isolated infra, tamper-evident audit logs, compliance reports, and deep policy control.

How Fleet relates to the Harness and Workbench​

Your Harness runs on your machine. It doesn't require Fleet. Signing in to Fleet from your Harness is always opt-in — you enter your work email in the Harness, authenticate, and the Harness receives any shared configuration your admin has published.

If your admin has set a routing policy or published shared context, your Harness picks it up the next time it syncs. What Fleet can push is bounded by your role and your org's plan — a policy that requires an Enterprise capability won't apply to a Team org, and an org_member can't change policy for others.

If you sign out of Fleet, your Harness continues working with its local configuration. Nothing stops.

Where to start​

If you're setting up Fleet for your team for the first time, the Getting Started guide walks the whole journey — account, org, plan, and your first shared config — in one place.

If you want to go straight to a specific topic:

Next: Getting Started — the step-by-step admin on-ramp.