An agent-native HRIS
Clear records. Useful agents. Human decisions.
VikaPeople connects employee records, onboarding, and leave with the work that follows. Rules compute policy results. Agents prepare evidence and next steps. Your team approves consequential changes.
For HR, managers, and employees at services and product companies.
A decision has a trail.
- Source
Demo employee · manager change request
- Rules
Effective date and permissions
- Proposal
The exact change, ready for review
- Human approval
A different person decides
- Receipt
The change and its approval record
We have built core records, onboarding, and leave for internal testing. We plan to add Employee Concierge.
An employee record that carries the work forward.
Records, tasks, agents, and approvals share one workflow. Each role sees the records and fields it can access.
- Records with history
- Keep employees, teams, managers, and effective dates together. Review a proposed change before it takes effect.
- An inbox for exceptions
- Find approvals, agent questions, missing records, and blocked journeys in the Action Center. Each item has a next step.
- A read-only HR Copilot
- Ask about employee records, team structure, and headcount. The Copilot reads within your permissions. It does not change records.
Employee Concierge · planned
A policy answer needs a source.
The planned Employee Concierge will answer from approved policies that apply to the employee. Each answer must name its evidence.
- Cite the policy title, version, section, and effective date.
- Use only sources that the employee has permission to read.
- State when a source is missing, expired, or in conflict.
- With consent, pass an unresolved question and its context to a person.
Synthetic policy example
Who approves my leave request?
Your manager or HR decides your request. The agent can explain the policy. It cannot approve leave.
Effective 1 September 2026
When the source is missing
I cannot find a current policy for this question. May I pass it to HR with this context?
From VikaHire to VikaPeople
Carry the hiring handoff into the first day.
A hire starts a reviewed handoff. VikaHire owns the recruiting record. VikaPeople owns the employee record and the onboarding journey.
- 01
Review the handoff
A signed VikaHire event opens a proposal for a pre-boarder. An approver decides whether to create the record.
- 02
Prepare the journey
The journey template sets tasks, owner roles, and due dates. The Onboarding Agent explains the template and identifies tasks without a named owner.
- 03
Resolve the blockers
Track documents, task dependencies, and the start date. The agent asks HR whether the new joiner is ready.
- 04
Approve activation
The agent raises an Action Center item. A person proposes activation, and a different person approves it.
The handoff carries contact details, the offer title, and the start date. It excludes interview scores, recruiter notes, and candidate history.
Repeated deliveries do not create another proposal. Conflicting hire events raise an exception for review.
Deterministic rules own policy arithmetic
The model explains. The rules compute.
Code computes leave accruals, balances, dates, and policy results. A ledger records each change. The model does not invent a balance.
- Before a request
- Preview working days, the resulting balance, and policy failures. Working weeks, holidays, and half-days follow the rule set.
- At the decision
- The Leave Operations Agent summarizes the request and follows up. A manager or HR approves, rejects, or returns it for changes.
- After approval
- The ledger records the approved days. Cancellation adds a reversal. Your team can trace the balance to its entries.
Each agent has a job. Each decision has an owner.
These five agents exist in the internal build. They start disabled. An administrator enables rehearsal before live work.
Onboarding Agent
Agent workExplain the journey, report missing owners, and ask HR about readiness.
Human decisionA person proposes activation. An approver decides.
Record Steward
Agent workFind duplicates, missing fields, and record exceptions.
Human decisionYour team reviews corrections and record merges.
Lifecycle Watcher
Agent workRaise tasks for start dates, probation ends, and document expiry.
Human decisionYour team decides any change to employment.
Import Agent
Agent workPropose column mappings and prepare an import preview.
Human decisionYour team reviews mappings and approves record changes.
Leave Operations Agent
Agent workSummarize requests, follow up, and verify the ledger after a decision.
Human decisionA manager or HR decides leave.
The roadmap includes Policy Concierge, Org Change, Offboarding, and Notification agents. It also includes an agent for personnel insights.
Evidence before confidence.
These principles guide VikaPeople. They set the limits of the product and its agents.
VikaPeople does not compute payroll or statutory filings. Its scope excludes surveillance, employee ranking, and performance scoring. It does not promise automatic IT account provisioning.
- Show what supports the answer
- Source records, policy citations, missing information, and rule results matter more than a confidence score.
- Untrusted content is data
- Documents, imports, and policy text can contain instructions. Agents must treat that content as source material, never as permission to act.
- Approve before the effect
- Consequential changes require approval. An expired approval does not permit a change. Agents cannot decide employment, pay, or leave.
- Keep Core HR independent of AI
- Records, approvals, leave rules, and exports must continue when an AI provider fails.
Tell us where HR work gets stuck.
Share the workflow you want to improve. We can discuss whether VikaPeople fits your team.
This form prepares an email draft. It sends nothing and stores no submission on this site. Review and send it in your email app.
Complete all fields.
Enable JavaScript to prepare a draft, or write to the address below.
You can also write to hello@vikawork.com.