Technical founders. Enterprise pedigree.

HubBound is a registry for AI agent capabilities. Software teams version prompts, skills, rules, hooks, subagents and MCP servers as Artifacts, bundle them into Kits, and install them on every developer's machine with a single command. Think of it as npm for AI agent capabilities, with the organization layer public registries do not have: teams, roles, scoped distribution and per-team measurement.

An AI Artifact is a versioned, reusable unit of AI agent configuration. It can be a prompt, a skill, a rule, a hook, a subagent or an MCP server. Every Artifact has an owner, a version history and a visibility scope, and any Artifact can be installed on its own or bundled into a Kit.

A Kit is a named, versioned bundle of AI Artifacts installed with one command. A Kit is to Artifacts what a package is to modules. Instead of asking a new developer to copy nine files out of a wiki, you hand them one Kit and their environment matches the rest of the team in seconds.

Most teams start by pasting prompts into a wiki or copying rules files between machines, which drifts within weeks. HubBound replaces that with a registry: prompts, rules and MCP servers become versioned Artifacts, get bundled into Kits, and are distributed to specific teams. Improving a prompt improves it for everyone who installed it, and the CLI keeps every machine in sync.

No. HubBound works alongside the tools your team already uses — it standardizes how they are configured, distributes those standards as Kits, and measures how they are used. Your developers keep their preferred tools.

HubBound supports the leading AI coding tools — Claude Code, Cursor, OpenAI Codex, Antigravity and GitHub Copilot — and Kits are portable across all of them. The same Kit installs into any supported provider without rewriting the standards it contains. New providers are added continuously.

Public registries are directories: they help you discover an MCP server, but they do not know who is on your team. HubBound adds the organization layer — private Artifacts scoped to your company, Kits distributed to specific teams, admin and member roles, and usage measured per team. Discovery is table stakes; scoped distribution inside a company is the part public registries cannot do.

Private Artifacts and Kits are scoped to your organization: only its members can see, install or fork them. Public and private live side by side in the marketplace, and visibility is enforced at the organization level.

Merged PRs, the AI share of changes, top users, tool efficiency, tool rework and team effectiveness — per team or aggregated across the organization.

Engineering organizations of any size with more than one developer using AI — from startups standardizing AI usage from day one, to enterprises that need governance and visibility across many teams. The buyer is usually a head of engineering or platform lead; the daily user is the individual developer.