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.
Your first org is free to start
Creating your first organisation is always free — you can publish skills, connect a machine, and run the gate on the Free plan before deciding to upgrade. Paid plans are for adding people and longer-lived governance.
Comparison
| Free | Team | Business | Enterprise | |
|---|---|---|---|---|
| Price | €0 | €20/mo | €40/mo | Contact sales |
| Members | 1 | Metered | Unlimited | Unlimited |
| Namespaces | 1 | 1 | Unlimited | Unlimited |
| Audit retention | 7 days | 30 days | Unlimited | Unlimited |
| Org governance | — | ✓ | ✓ | ✓ |
| Full policy engine | — | — | ✓ | ✓ |
| SSO | — | — | ✓ | ✓ |
| Signed bundles | — | — | ✓ | ✓ |
| Audit export | — | — | ✓ | ✓ |
| Policy approvals | — | — | — | ✓ |
| SCIM provisioning | — | — | — | ✓ |
Prices are billed monthly or yearly — choose the cycle at checkout. 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 and Team include one namespace; 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 queryable and exportable: 7 days on Free, 30 days on Team, and unlimited on Business and Enterprise. Compliance buyers who need a long, immutable history want Business or above.
Governance features
| Feature | Plan | What it unlocks |
|---|---|---|
| Org governance | Team+ | Org-wide skill approval, distribution, and the runtime gate |
| Full policy engine | Business+ | The complete matcher set and richer policy authoring |
| SSO | Business+ | Single sign-on for the console |
| Signed bundles | Business+ | Cryptographically signed policy distribution |
| Audit export | Business+ | CSV / JSON export of the audit log |
| Policy approvals | Enterprise | A review/approval step before a policy goes active |
| SCIM provisioning | Enterprise | Automated user provisioning/de-provisioning |
How billing is metered
Paid plans 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.
Changing plans
Upgrade or change your billing cycle from the console's billing page. Limits apply immediately on change — for example, dropping below a plan that allows multiple namespaces requires you to be within the new plan's namespace limit first.