Catalogue
Buy the ones you need. Skip the ones you don't.
Modules are where genuine cost lives: partner payroll integration, contractor invoicing, recruiting reach, scheduling depth. So modules are where prices live, and they live on the pricing page rather than here, because they are adjusted by country. What is on this page is the decision that comes first: what each one 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
Pay, contractors, equity 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
- Payroll Capstan compiles attendance, leave, overtime and comp into a documented export for your payroll partner, then files the results back into the record. per active payroll member 5 published limits
- Contractor Management Onboard contractors, resolve and collect their tax forms, approve invoices and record each payment with its reference. No money moves through Capstan. per active contractor 6 published limits
- Compensation & Equity Effective-dated compensation records, bands, revision workflows that generate the letter, and an equity view where every employee sees their own vesting. per employee 5 published limits
- Expenses & Travel Multi-line claims with receipts, mileage on your own dated rate tables, and advances that settle against claims, all through your own approval chain. per employee 5 published limits
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
- Time & Attendance (Advanced) Shift definitions, rosters, rotation patterns, swaps and overtime rules on top of the free core punch. Overtime becomes comp-off or a payroll input. per employee 4 published limits
- Timesheets & Projects Time logged against projects and tasks, submitted and approved on your own cadence, with billable reporting only if you choose to configure rates. per employee 5 published limits
- Asset Management A register of what you own and who holds it, from issue at onboarding to return at exit, with condition captured and the holder acknowledging both. per employee 5 published limits
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
- Performance & OKR Review cycles on your own timeline, with your own questions and rating scale, and goals beside them. No calibration, no forced distribution, no AI. per employee 5 published limits
- Learning (LMS) Courses built from your own documents, links and text, assigned by person or org scope, with optional quizzes and completion you can actually prove. per active learner 5 published limits
- Engagement Pulse and annual surveys whose anonymity is structural: an anonymous response carries no author, and results stay hidden below your minimum group size. per employee 5 published limits
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
- Helpdesk Employees raise HR cases from self-service and agents work a real queue: categories, assignment rules, SLA clocks, internal notes and full history. per employee 5 published limits
- Advanced Analytics A permission-projected dataset catalogue, custom reports, dashboards and scheduled delivery. Every widget runs as the viewer, never as its author. per employee 5 published limits
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.
- Billing starts at the click
- Enabling is one click inside the app. Billing runs from that moment, prorated to the term you are already in, and disabling stops it at the end of that term rather than on the day.
- Turning one off deletes nothing
- The surface goes, the data stays: retained on a schedule, restored if you re-enable inside that window, and included in a full workspace export whether the module is on or off.
- Not enabled means not reachable
- Nothing a module adds is reachable by a workspace that has not enabled it, 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, and not one of them required. The core they sit on is free.