Catalogue

Fourteen modules, all included in your plan.

Contractor invoicing, equity and compensation tracking, recruiting reach, partner payroll integration: the capabilities beyond the core. Every one of them is included in a paid plan at no extra charge, so there is nothing to price module by module. The one plan price is on the pricing page. What is on this page is the decision that comes first: what each module is for, what it counts, and what it says it will not do.

All fourteen are shipped and purchasable today. Nothing below is a roadmap entry, and nothing below is quote-only.

Before someone is an employee

Hiring, and the hand-off into the record. One module, because there is one job here and we have not invented a second.

1 module

What people are paid, and what work costs

Contractors, equity, pay and reimbursements. Every module in this group records money and none of them moves it: no payout rail, no bank file, no funds resting anywhere in Capstan.

4 modules

When people worked, and what they hold

Shifts and rosters, time against projects, and the laptop someone is carrying. Operational records, kept where the people records already are.

3 modules

How people are doing

Reviews, training and surveys. Performance and Engagement publish the same boundary in their own words: no AI forms a judgment about a person, anywhere in Capstan.

3 modules

Running the HR function itself

For the team that runs HR rather than for everyone in the company: a case queue instead of a shared inbox, and reporting that runs as the person reading it.

2 modules

After someone leaves

A former employee still needs their own documents. Their access to them does not depend on anyone still working here.

1 module

True of every module, whichever ones you pick

Six rules, and not one of them varies by module, which is why they are here once rather than on fourteen pages. A module page tells you what that module is; this is what buying any of them means.

Not one is required
The core HRIS is complete without them, and no module needs another module to work. Where two of them meet, the capability is simply absent when only one is on rather than broken. What the core does.
A paid plan comes first
A workspace on the free plan is refused with an upgrade prompt rather than a subscription starting quietly underneath it, and moving onto a paid plan is a request a person here grants by hand rather than a checkout. How that request works.
Included, not billed line by line
Every module is part of a paid plan at no extra charge. There is nothing to buy or meter module by module: the plan per-seat price is the only charge, and the whole suite is switched on with the plan. The one price.
Moving back to Free deletes nothing
If a workspace drops back to the free core the module surfaces go, but the data stays: retained on a schedule, restored when you return to a paid plan inside that window, and included in a full workspace export either way.
The free core reaches no module
On the free core, nothing a module adds is reachable, at any level from a whole module down to a single field, and that boundary is checked against the shipped code and the live data on every push and again nightly. How that is checked.
Every one publishes its limits
71 of them across the fourteen, taken from each module's specification rather than softened for a catalogue, and printed second on the module's own page rather than buried under it.

Fourteen modules, all included in a paid plan. The core they sit on is free.