Discuss the project
Design partner trackUnlimited Skills / Enterprise Edition

Make skill delivery part of the security boundary.

Enterprise Edition is the governed control layer for large mixed-agent fleets where capability sources, versions and delivery state must be enforceable and auditable.

Plan an Enterprise rollout View every edition
  • Private registry
  • Signed policy
  • Enterprise Skill Lock
  • On-premises or VPC path
Enterprise enforcement model Approved source.
Approved version.
Intended fleet.
01Registry

Constrain allowed capability sources

02Policy

Sign the rules for managed instances

03Lock

Audit or refuse disallowed delivery

04Evidence

Build fleet and compliance state

01 / The enterprise risk

An agent’s capability is executable operating policy, not another file to sync.

At fleet scale, an unreviewed instruction, stale version or wrong destination can become a security, compliance or change-management incident.

Source risk

Which registries and local roots may provide skills?

A public directory, private team repository and local override should not automatically carry the same trust level.

Version risk

Which exact signed revision was approved?

File presence does not prove that every managed instance received the intended release or retained it after an update.

Destination risk

Which agents and teams are permitted to use it?

Capability scope must follow organisational policy instead of spreading through copied folders and individual installs.

Evidence risk

Can operations prove what happened?

Security and compliance teams need durable state, exceptions and change history, not screenshots from each agent workstation.

02 / Enterprise controls

A policy-enforced layer above every supported agent runtime.

Community Core stays MIT and local. Enterprise controls are opt-in for managed environments and do not turn the product into another agent platform.

01

Enterprise Skill Lock

Audit or refuse unmanaged registries, release channels, manifest keys, local roots, community actions, hub allowlists and remote fallback.

Local policy MVP available
02

Signed managed policy

Fetch a signed policy assignment, verify both assignment and payload, support dry-run, and refuse unsafe removal of unmanaged local policy.

Client foundation available
03

Private registry boundary

Keep enterprise skill bodies, signing operations, entitlements and policy administration outside the public repository and public catalog.

Private foundation / deployment scoped
04

Controlled administrator override

Record exceptional approval paths instead of bypassing policy invisibly, with explicit actor, reason, scope and change state.

Governance path evolving
05

Fleet compliance state

Build toward per-agent and per-pack acknowledgement, retry state, policy version and exception evidence across the managed fleet.

In development
06

Enterprise evidence export

Package local value and governance evidence with a verifier so reporting can be checked independently instead of accepted as an opaque dashboard number.

Evidence foundation available
03 / Enforcement path

Policy travels from the enterprise boundary to the managed instance.

The design separates policy authority, signed delivery and local enforcement.

  1. 01

    Define the enterprise policy

    Choose approved registries, channels, signing keys, roots, community actions and fallback rules for each managed scope.

  2. 02

    Sign and assign

    Bind the policy to the intended organisation, team or installation through a signed assignment contract.

  3. 03

    Verify locally

    The client verifies the assignment and policy before installing it. Dry-run performs verification without changing local state.

  4. 04

    Audit or enforce

    Managed instances log disallowed actions in audit mode or refuse them in enforce mode, while unmanaged Community Core remains unchanged.

  5. 05

    Collect evidence

    Fleet dashboards and delivery receipts are being productised to expose policy, version, update, failure and exception state.

04 / Deployment boundary

Fit the control plane to the company’s security model.

The final deployment is selected during design-partner scoping, not assumed from a generic SaaS architecture.

Managed service path

Registered managed instances

Use signed registry contracts and policy assignments while keeping local prompts, source code, skill bodies, local paths, tokens and device private keys outside policy-sync payloads.

Private cloud path

Customer VPC

Place the private registry and governance services inside a customer-controlled cloud boundary with contracted integration and operating responsibilities.

Planned deployment option
Private infrastructure path

On-premises

Run the registry and policy boundary inside enterprise infrastructure where network, identity and data-residency requirements demand it.

Planned deployment option
Local-first remains the default:managed policy sync is designed not to upload local skill bodies, prompts, source code, local paths, search queries, secrets or private device keys.
05 / Honest availability

Enterprise controls have a real technical foundation. The complete fleet product is still being finished.

Design partners enter with explicit boundaries, milestones and acceptance tests.

Available foundation

Policy and verification

  • Local Enterprise Skill Lock MVP
  • Audit and enforce modes
  • Signed managed-policy verification
  • Dry-run and safe removal guards
  • Private-pack and registry client contracts
  • Enterprise evidence pack and verifier
Design partner scope

Environment integration

  • Enterprise policy model
  • Private namespace and registry boundary
  • Fleet adapter matrix
  • Change-control and exception workflow
  • Deployment and support responsibilities
In development / planned

Complete fleet operations

  • Per-pack delivery acknowledgements
  • Retries and compliance receipts
  • Full fleet dashboard
  • SSO and SCIM integration
  • Packaged VPC and on-premises deployment

Unlimited Skills does not claim guaranteed fleet delivery until acknowledgement, retry and compliance-receipt workflows are completed and verified in the target environment.

06 / Enterprise questions

What security and platform teams ask first.

Does Enterprise Skill Lock control every file on a workstation?

No. It governs Unlimited Skills delivery paths and can constrain approved registries, channels, signing keys, roots and related actions. A user with direct filesystem and source-code access still requires normal OS and endpoint controls.

Can policy sync read our prompts or skill bodies?

No. The managed sync contract excludes local skill bodies, prompts, source code, local paths, search queries, secrets, tokens and private device keys.

Is SSO or SCIM available today?

Not as a finished production integration. Both are planned Enterprise capabilities and must remain explicit roadmap items until implemented and verified.

Do we have to replace our current AI agents?

No. Unlimited Skills is an independent capability and policy layer above supported runtimes. The design-partner process maps the existing fleet before proposing adapters or controls.

Enterprise design partner

Bring the policy boundary, not a generic feature wishlist.

Tell us which registries, teams, runtimes, signing rules and deployment constraints define a safe rollout in your environment.

  • Explicit available/planned boundary
  • Deployment model agreed before build
  • Acceptance tests for policy and evidence
← Back to Unlimited Skills overview
Enterprise inquiry

Tell us about the fleet and governance boundary you need to control.


    Protected by reCAPTCHA. The Google Privacy Policy and Terms of Service apply.