Plans & entitlements

skillsvault has four plans. Each one raises a set of limits and unlocks governance features; everything is keyed off your organisation's current plan, which you manage from the console's billing page. This page is the canonical reference for what every plan includes.

Comparison

Prices are billed monthly or yearly — choose the cycle at checkout, and switch it later from the billing page (see Changing plans below). Enterprise is not self-serve; contact sales to enable SSO/SCIM, policy approvals, and unlimited retention with a contract.

What each limit means

Members

The number of people in the organisation. Free is a single user — enough to evaluate skillsvault end to end. Team and up add people; seats are metered (see below) rather than capped.

Namespaces

A namespace is the prefix in a skill's namespace/skill-name identity and the unit a policy can target wholesale. Free includes one managed namespace, Team three, and Business and Enterprise are unlimited, so you can separate, say, acme-legal from acme-sales and govern them independently.

Audit retention

How far back the audit log is visible and exportable: 7 days on Free, 30 days on Team, and unlimited on Business and Enterprise. Older events aren't deleted — the log is append-only — so history beyond your plan's window is kept and becomes visible when you upgrade. Compliance buyers who need a long, immutable history want Business or above.

AI

The editor's AI — assist (drafting and editing a skill), Test triggering and the scorecard — draws on one daily allowance per organisation; each author is also held to an hourly limit so one person can't spend the team's day. One model call is one assist: a Test triggering run counts as 4, a re-run after Improve description as 3, a scorecard as 1, and a result served from cache (the same draft asked again) costs nothing. AI reviews run when a skill is published and have their own allowance; a version whose content was already reviewed is never reviewed twice. Allowances reset at 00:00 UTC. AI is advisory everywhere: the deterministic checks and the runtime gate never depend on a model.

Governance features

How billing is metered

Team and Business are metered on governed seats — distinct developers with an active machine connection to your org. A seat is counted from the fleet itself (machines that have connected and are pulling skills), not from a self-reported number, so you pay for the developers actually under governance. See governed seat and Harness coverage.

Precisely, a governed seat is a person who:

• is an active member of the organisation — someone you remove stops counting straight away, even if their old machine is still listed, and
• has at least one machine that reported to the org (any skillsvault sync or pull) in the last 30 days.

Every paid organisation is billed for at least one seat. Pending invitations and members who never connected a machine are not billed.

The subscription follows the count automatically: when a new person connects their first machine, or a member is removed, the seat quantity on your subscription is updated with a prorated charge or credit for the rest of the period. The count is also reconciled once a day, which is when someone whose machines have been silent for more than 30 days drops off. The billing page shows the current count as N governed seats (billed). Enterprise seats follow your contract instead.