Engineering, sales and operations need different capabilities.
Give each team the approved packs it needs without exposing the entire company library to every agent.
Early accessUnlimited Skills / Business Edition
Private skills. Controlled rollout. One operating layer.
Business Edition gives AI-native companies one governed source for the capabilities used across teams, agent runtimes and release cycles.
- Private packs
- Team assignments
- Versioned rollout
- Mixed agent fleets
Business control loop
Review once.
Assign deliberately.
Update without drift.
Assign deliberately.
Update without drift.
01Source
Public and private skill libraries
02Govern
Ownership, review state and versions
03Deliver
Teams, agents and release channels
04Measure
Usage, savings and operating evidence
01 / Operational fit
For the moment skills stop being personal files and become company infrastructure.
Business Edition is for teams already using more than one agent runtime, maintaining internal procedures or distributing reusable capabilities across departments.
Your most valuable skills cannot live in a public directory.
Keep internal procedures in governed private packs with explicit ownership, version and assignment boundaries.
Copying folders no longer tells you what is actually running.
Move toward signed release channels, controlled updates and rollback instead of manual file distribution.
The company fleet will not standardise on one agent vendor.
Use one independent capability layer across supported runtimes and extend it through adapters as the fleet changes.
02 / Business capabilities
Everything required to operate a private skill supply chain.
The local MIT router remains the foundation. Business adds the organisation, distribution and operating controls needed above it.
Private skill packs
List, preview, install, synchronise and remove signed team-scoped packs through registered, entitled paths. Local libraries remain outside hosted access by default.
Alpha foundation availableOrganisation and team assignments
Model which teams, installations and agent groups should receive each governed collection instead of distributing one global folder.
Early-access productisationSigned rollout channels
Pin approved versions, promote changes through controlled channels and preserve a path to rollback when a capability causes operational trouble.
Foundation available, workflow evolvingAdmin and audit visibility
Track registered installations, approval decisions and local value evidence. Business-level Money Saved admin export supports CSV and JSON reporting.
Available foundationCross-runtime compatibility
Operate across Codex, Claude Code, OpenClaw, Hermes and filesystem-based extension paths without moving the company into another agent framework.
Adapters available nowPriority compatibility support
Define the company’s actual runtime matrix and work with AI4SALE on the adapter, packaging and rollout gaps that block adoption.
Design-partner delivery
03 / Operating flow
From scattered procedures to an assigned, versioned capability.
The pilot follows the same lifecycle the finished product is designed to govern.
- 01
Map the sources
Inventory public skills, internal procedures, team repositories and the runtimes that consume them.
- 02
Classify and review
Record ownership, sensitivity, compatibility, review state and the exact version approved for managed use.
- 03
Package and assign
Create governed collections or private packs and assign them to the teams, installations and channels that need them.
- 04
Roll out and observe
Promote signed versions, monitor failures and value evidence, then adjust the operating policy before scaling.
04 / Honest availability
A working technical foundation, being turned into a customer-ready Business product.
We separate what can be demonstrated now from what a design partner will help finish.
Local and signed foundation
- MIT local router and retrieval
- Supported runtime adapters
- Registration and team-sync contracts
- Signed manifests and verified archives
- Private-pack client operations
- Business Money Saved admin export
Business operating layer
- Customer-specific pack structure
- Organisation and team assignment model
- Governed release-channel workflow
- Admin reporting and support process
- Compatibility hardening for the pilot fleet
Full product experience
- Client-side encrypted private publishing
- Polished fleet dashboard
- Per-pack delivery acknowledgements
- Automated retry and exception workflow
- Broader self-service administration
Business Edition is offered as a scoped early-access pilot. Roadmap controls are not represented as completed production features.
05 / Edition boundary
Use Business when distribution is the problem. Move to Enterprise when policy enforcement is the boundary.
Team FreeBusiness EditionEnterprise Edition
Small registered teamsLarger multi-team organisationsLarge or regulated fleets
Approved public collectionsPrivate packs and assignmentsPrivate registry and signed policy
Manual approval by defaultAdmin workflow and rollout channelsEnterprise Skill Lock and override control
Up to 10 instances where enforcedPilot-defined team and installation scopeOn-premises or VPC deployment path
Business Edition pilot
Show us how skills move through your company today.
We will map the teams, runtimes, private sources and approval rules, then define a bounded pilot with explicit acceptance criteria.
- No forced runtime migration
- No claim that unfinished controls already exist
- A concrete pilot boundary before implementation
Business inquiry
Tell us about the teams and agent runtimes you need to govern.