Kibo / For HR
People operations, private by role.
Leave counted in each person's own working calendar, onboarding checklists created the day a hire is added, and leavers' handover and access removal tracked to the day. Everyone asks in plain language; HR keeps control.
Leave, onboarding and offboarding in one place.
Kibo works on leave requests, allowances, public holidays, new hires and leavers. People ask in plain language; Kibo counts the days, finds the approver and shows the request before filing it.
Records it works on:
- Leave requests
- Leave allowances
- Public holidays
- New hires
- Onboarding tasks
- Leavers
- Offboarding tasks
Outcomes, not screens.
Leave is counted in working days from each person's work pattern, country and public holidays, and nobody approves their own leave. A new hire gets every onboarding task with its due date at once. A leaver's handover, equipment and account removal become dated tasks, with IT acting on request.
Approved once. Enforced every time.
Leave approval is a policy, scoped to the team it concerns: in December, the Logistics team lead approves for year-end cover. It is approved once, versioned and applied to that team and nobody else.
Sovereign by design.
On your own servers, or hosted for you in a region of your choice, with an open-licence model. Your people's records are never sent to a third-party AI provider, and no telemetry is sent to anyone.
More: sovereignty · where Kibo runs · on-premise AI
Predictable cost.
Every employee, manager and request is included in the same annual licence as the rest of the company, with no per-seat, per-token or per-module pricing.
More: total cost of ownership
Personal data on a need-to-know basis.
People see their own requests, managers their team, and HR what HR needs; only HR sees leavers. Approvals are enforced by code, nothing is filed without confirmation, and every request is in the audit record.
More: governance · security · policy as code