One employee, five versions
The HR system holds one record, the attendance tracker holds another, and payroll runs off a spreadsheet someone maintains by hand. Reconciling them is a monthly job nobody wants.
Albero HRM runs employees, attendance, payroll, recruitment and performance from a single secure workspace — with encryption, an immutable audit trail and role-aware access built in.
30 modules · 12 integrations · 4 roles
Headcount, attendance and everything waiting on you, in one place.
The HR system holds one record, the attendance tracker holds another, and payroll runs off a spreadsheet someone maintains by hand. Reconciling them is a monthly job nobody wants.
Approvals happen in email, chat and corridors. When finance or an auditor asks who signed off a salary change and when, the answer is a search through inboxes.
Records get reconstructed under deadline rather than captured as the work happens, so the evidence is only ever as good as somebody’s memory of it.
Grouped the way people work rather than the way software is usually sold. Every module reads and writes the same employee record, so nothing needs reconciling at month end.
Where every role lands after signing in.
3The numbers that matter to you, scoped to what you are allowed to see.
Every request waiting on you — leave, expenses, offers — in one queue.
Ask a question in plain English and get an answer from your own records.
The employee lifecycle, from offer accepted to final settlement.
9One record per person — profile, documents, history and reporting line.
Collect documents and details before day one, so day one is not paperwork.
Task lists, asset handover and introductions, tracked to completion.
Clock-ins, regularisation and overtime against the rules you configure.
Build rotating shift patterns and publish rosters your team can see.
Policies, accruals, holiday calendars and multi-step approval chains.
Goals, review cycles and feedback captured against the employee record.
Notice, clearance, asset return and final settlement in one checklist.
Consent-first workplace analytics from CCTV — face templates, never images.
What people cost, and where it goes.
4Run salaries against attendance and leave, then produce payslips.
Claims with receipts, routed to the approver your policy names.
Issue, track and reclaim laptops, devices and licences per employee.
Your subscription, payment method and invoices — admins only.
Hiring and growing the people you already have.
3Roles, pipelines, interview scheduling and offers against one candidate record.
Assign courses and learning paths, then track who actually finished.
Log hours against projects and clients for billing and capacity.
The connective tissue — communication, records, automation and control.
11Company-wide or team-scoped notices, with read tracking.
Pulse surveys and recognition, reported without exposing individuals.
Policies, contracts and letters, filed against the people they concern.
A ticket queue for employee questions, so nothing lives in a DM.
Headcount, attrition, cost and attendance, cut by the fields you use.
The reporting structure that drives approvals and manager scope.
Trigger tasks, notifications and approvals when a record changes.
Connect identity, chat, payments and finance to the same records.
Roles, scopes and entitlements, with a checker that explains each answer.
Who did what, when, from where — append-only, with redacted diffs.
Policies, fields, approval chains and branding for your workspace.
A separate, operator-only control plane for firms running HR on behalf of their clients.
4Every client workspace, its plan and its module entitlements.
What each client is billed, and what has been collected.
Operator-level controls across every workspace you run.
One trail spanning every client — including every support entry.
Fast, clean and thoughtfully designed — from the HR command centre to every employee's self-service home.
Headcount, payroll and everything waiting on you, in one command centre.
What someone sees is decided by who they are, not by which link they were sent. Permissions carry scope as well as verbs — “view employees” means direct reports for a manager and the whole company for HR.
A client's owner. Everything HR can do, plus the plan, payment method and invoices.
Full access to every people module and organisation-wide data. Deliberately no billing.
Their team, approvals and people analytics.
Self-service — payslips, leave, documents, tasks and profile.
| Capability | Admin | HR | Manager | Employee |
|---|---|---|---|---|
| People data in scope | Whole company | Whole company | Their team | Themselves |
| People modules | Team only | Self-service | ||
| Approvals | Their team | Raise only | ||
| Reports & people analytics | Their team | |||
| Payroll & expenses | Own payslips | |||
| Billing, plan & invoices | ||||
| Audit log | Company | Company |
Scroll the table sideways on a narrow screen.
Below is what is running in production today, described precisely enough to check. What is not built is listed underneath rather than left out.
Aadhaar, PAN, passport, bank account, IFSC, tax identifiers, salary and medical notes are encrypted at rest. Separate encryption keys per data domain, so they rotate independently. Authenticated encryption means a tampered record fails to decrypt rather than returning wrong data.
Every action records who, when, from which IP, which browser and device, and what changed before and after. Immutability is enforced in three independent layers: no write route exists, the ORM refuses updates and deletes, and a database trigger rejects them for any client — including one connecting directly to the database.
The trail records that a salary changed, never the figure — so it never becomes an unencrypted copy of protected data.
Plain-HTTP reads are redirected; plain-HTTP writes are refused outright, because their contents already crossed the network in the clear. HSTS with a two-year max-age and preload.
Sessions live in httpOnly cookies, unreadable to page scripts, with CSRF double-submit protection on every write.
Per-IP and per-account limits on authentication attempts, against brute force.
"View employees" means direct reports for a manager and the whole company for HR — permissions carry scope, not just verbs. An access checker explains why any answer was given.
A company's identity comes from the authenticated session, never from anything the browser sends. Module entitlements are per tenant, and suspending a client blocks every login immediately.
The Vision module stores mathematical face templates rather than images, requires a recorded consent per person, falls back to anonymous without one, caps retention, and audits everyone who views surveillance data.
Production refuses to start with missing encryption keys, HTTPS disabled, or default credentials.
We hold no security certification, and we will not imply one. If any of the following is a requirement for you, it is a reason to wait rather than a reason to sign.
Three concrete jobs, done against your own records. No general-purpose chatbot bolted onto a form.
Ask what the notice period is for a band, or how many casual leaves carry forward, and the assistant answers from the policies you uploaded — not from the open internet.
Job descriptions from a role brief, and review summaries from the goals and feedback already on the record. You edit rather than start from a blank page.
Flags attendance and payroll records that break the pattern — a shift that never clocked out, a payslip that jumped without a linked change.
The assistant never sees encrypted identity fields. Aadhaar, PAN, passport, bank and tax identifiers stay encrypted and out of scope for every prompt.
How much notice does a band L4 engineer have to serve?
Sixty days, per your Employment Policy v4 (section 9.2). Managers can approve a shorter period in writing, and that approval is recorded on the exit checklist.
Draft a job description for a senior product designer.
Drafted from your Design career ladder and the last two designer roles you posted. Ready to edit.
Illustrative exchange.
Identity, chat, payments and finance, wired to the same employee records. These are the connections that exist — there is no longer list behind a sales call.
Calendars, mail and file storage against the same employee record.
Approvals and announcements delivered where your team already talks.
Match Albero accounts to your directory so joiners and leavers line up.
Calendar, mail and Drive, connected to people and documents.
Approve leave and read announcements without leaving the channel.
Interview and review meetings scheduled from the record they belong to.
Reach shift and field staff who do not sit at a desk.
Disburse salaries and reimbursements against a completed payroll run.
Collect subscription payments for your Albero plan.
Push payroll and expense journals into your books.
Export cost-centre and headcount data into your finance system.
Keep an enterprise ERP in step with people and cost changes.
Most of people operations is the same everywhere. These are the bits that are not, and what the platform is configured to handle.
Engineers spread across cities and time zones, hired fast and rarely all in one office on the same day.
Rotating shift rosters and overtime rules that change by plant, with contract labour alongside permanent staff.
Clinical credentials expire, and a nurse whose licence lapsed cannot be on the roster the next morning.
Workloads and leave follow the academic year, not the financial one, across campuses that staff differently.
A seasonal ramp that doubles headcount for eight weeks, onboarded store by store and offboarded just as fast.
Drivers and hub staff who never sign in at a desk, with attendance that has to be captured where they are.
Every change to pay or access has to be attributable, months later, to a named person and a timestamp.
One person doing HR alongside another job, who needs the whole lifecycle to work without an implementation team.
You keep running your current process until the imported data matches what you believe is true. Nothing switches over on trust.
Bring employees, documents, leave balances and historical payroll in from spreadsheets or an export from your current HR system. We map the columns with you and show you the result before anything is committed.
Set departments, locations, reporting lines, leave policies and approval chains. The organisation chart is what drives manager scope and approvals, so this is the step worth getting right.
Roll out to HR and managers first, then employees. Self-service, payslips and leave go live together so nobody is asked to use two systems at once.
A straightforward migration for a company under 200 people typically takes five to ten working days end to end — most of it spent agreeing policies and checking imported data, not waiting on software. Larger or multi-entity rollouts take longer, and we will give you a dated plan before you commit.
You pay for people who are actually employed. Someone who exits stops counting at the end of the billing cycle.
Small teams putting core HR in one place for the first time.
billed annually
Start with StarterCompanies running payroll, hiring and reviews on the same records.
billed annually
Book a demoLarger or multi-entity organisations that need a named owner on our side.
Priced against your headcount and modules
Talk to salesEvery plan includes the same security baseline: AES-256 encryption at rest, the append-only audit trail, multi-tenant isolation, enforced HTTPS and role-based access. None of it sits behind a higher tier.
Including the ones where the honest answer is “not yet”.
Your workspace is hosted in a single region, and we confirm which region in writing before you sign. If you have a residency requirement, raise it during the security review and we will tell you plainly whether we can meet it rather than after the contract is signed.
Book a walkthrough with someone who can answer the security questions as well as the HR ones. Tell us your headcount and we will bring a workspace set up to look like yours.