Employee directory and secure personnel records
A single directory holds every employee record, scoped so only the right people can see it.
Runlium People
Support the employee lifecycle with clear ownership, private records, policy-aware workflows, and a better self-service experience.
Core capabilities
Employee records, onboarding, leave, documents, goals, reviews, and operating requests.
A single directory holds every employee record, scoped so only the right people can see it.
New hires get a role-specific onboarding checklist, and offboarding collects access and documents on the way out.
Leave requests route to the employee's manager or HR, with balances kept per policy. Attendance tracking is planned.
Planned: goals, check-ins, and reviews connected to development plans.
Planned: policy acknowledgements and document expiry reminders.
Reporting lines and job history are kept as people join, move, and leave. A visual org chart is planned.
Connected workflows
Each workflow is modeled as visible steps, typed events, clear ownership, approval rules, retries, and recoverable execution.
Launch role-specific onboarding when an offer is accepted.
Route leave requests through the correct approval policy.
Notify employees and managers before documents expire.
AI in context
The AI experience is designed to retrieve only permitted context, expose evidence for important answers, and separate recommendations from approved execution.
Who is overloaded across active projects?
Prepare an onboarding plan for a new product designer.
Which compliance documents expire this quarter?
Works with
Records, permissions, and events are common across the platform, so each module adds context to the others instead of copying it.
Invoices, expenses, approvals, subscriptions, budgets, and operational finance visibility.
Omnichannel tickets, service levels, knowledge, customer health, and success plans.
Documents, decisions, policies, procedures, wikis, templates, and governed knowledge.
New to the category? Read what an AI business operating system is, or see how the modules share one platform architecture and workspace-based pricing.
Founding design partner
Use cases from founding teams will define the first workflows, integrations, fields, and migration tools.