People recordsIn every plan
Employee records, the org chart, imports and everyone’s own profile
Built for Indian statute · 20–500 people
The HR system that already knows the rules you follow.
People, onboarding, attendance, leave and hiring for growing Indian companies — built around Indian leave law, POSH and the DPDP Act rather than translated from software written where none of them apply. Payroll is coming soon.
- The plan you choose, in full
- No card required
- Nothing charged automatically
app.flabido.com/console
Mar 2027 · Open
Audit chain verifiedGood morning, Nikhil
3 approvals owed · 2 joiners start on Monday
Headcount
184
+6 this month
Present today
171
9 leave · 4 late
March cost
₹1.42 Cr
incl. employer PF
Approvals owed
- AIAnanya Iyer · 2 days earned leaveApprove
- RKRohit Kulkarni · regularise 11 Mar2d
0
States and union territories in the GST code table
0%
Provident fund on basic, to the ₹15,000 ceiling
0
Modules in the product — 9 of them in every plan
0
Days of trial on your plan, no card
The product
One record of truth, four surfaces on top of it.
Every change is an interval with a date rather than an overwrite — so the org chart, a payslip reprint and an appraisal letter all agree about what was true in March 2026.
What is stuck, and who is blocking it
Onboarding, exit, probation confirmation and document renewal run through one workflow engine. Owners resolve by relationship, due dates respect the location’s holiday calendar, and the escalation ladder chases a person once rather than six times.
- A running journey is pinned to a template version, so changing the template never rewrites history
- Escalation is decided by the clock, not by how often a sweep happened to run
- Everybody sees exactly what they owe, and nothing they don’t
Statutory — what is owed
EPF — electronic challandue 15 April
₹2,14,800ESI — monthly contributiondue 15 April
₹38,260Professional tax — Maharashtradue 30 April
₹26,800TDS — quarterly return 24Qdue 31 May
₹5,12,400Computed from the month that was actually run, per state, with the register behind each figure.
Everything in it
21 modules. 9 of them in every plan, at every price.
A POSH complaint channel and a DPDP data request are obligations your company carries whatever it pays a vendor. They are not ours to sell.
DocumentsIn every plan
Storing and reading employee documents
RequestsIn every plan
The request desk employees raise questions through
SubscriptionIn every plan
The billing screen, invoices and payment
Data rightsIn every plan
Answering access, correction and erasure requests
POSHIn every plan
Raising a complaint and the Internal Committee’s case list
LeavingIn every plan
The organisation export and closing an account
Audit trailIn every plan
The tamper-evident record of who did what
SettingsIn every plan
Organisation profile, roles, members and security
Journeys
Onboarding and offboarding journeys, tasks and templates
Letters
Letter templates, generated letters and e-signature
Announcements
Company announcements and surveys
Attendance
Punches, shifts, the attendance register and regularisation
Leave
Leave policies, balances, applications and the year-end run
Payroll
Salary structures, payroll runs, payslips and statutory registers
Hiring
Openings, the candidate pipeline, interviews and offers
Performance
Goals, review cycles, probation, improvement plans and increments
Leavers
Resignations, notice periods, clearance and full-and-final
Reports
The report builder, saved reports and scheduled delivery
Assets
The asset register: what the company owns, who holds it, and its history
Expenses
Expense claims: submission, receipts, approval and reimbursement
Built to be checked
Separation your database enforces, not your code.
Every table carrying customer data has row-level security enforced by PostgreSQL itself. The application connects as a role that cannot bypass it — so a query that forgets the organisation returns nothing rather than somebody else’s rows.
- Salary, PAN and bank details encrypted with a key belonging to you alone
- A hash-chained audit trail, where altering an entry is detectable
- POSH complaints readable only by your own Internal Committee — not by any administrator, and not by us
- A full export of everything, including after a subscription lapses
Audit chain — March changes
Leave policy version approved
this9f3c…a71eafter2b60…4d17
Statutory register generated
this4b81…c2d0after9f3c…a71e
Salary batch locked
thise07a…5f93after4b81…c2d0
Audit hash verified
thisc15d…8b46aftere07a…5f93
Each entry carries the digest of the one before it. Altering any of them breaks every link after it, which is what makes tampering detectable rather than invisible.
Data residency
Hosted in Singapore, not India. DPDP access, correction and erasure requests are a screen in the product, not an email thread.
Access
Permissions paired with scopes. “Manager” is a scope, not a role — so the same permission means a different set of people for each person who holds it.
What we are not keeping
Settings → Security in the product lists every guarantee this deployment is not currently meeting. It is published to customers rather than kept internally.
Why Flabido
Four decisions most HR software gets wrong.
| The question | Usual answer | Flabido |
|---|---|---|
| Professional tax | A field you maintain by state, by hand | Dated, cited rules per state — including Maharashtra’s February ₹300 |
| A leave balance | A stored counter somebody adjusts | The sum of an append-only ledger the database refuses to edit |
| A day’s attendance | A status an administrator types | Derived from immutable punches — which is what makes a dispute winnable |
| A payroll run (coming soon) | Frozen on approval, then worked around | Locked by payment; approved versions kept and numbered |
Illustrative · not real customers
What we are building towards.
Flabido has no customers yet, so these are written examples of the outcomes the product is designed to produce — not quotes from anybody. When a design partner will put their name to a sentence, it replaces one of these.
Leave balances used to be a monthly argument. Now the ledger shows every day and why it counted, and the arguments stopped.
Onboarding used to be a checklist in a spreadsheet that three people owned. Now nobody chases anybody and the laptop arrives before the person does.
Seven sites across four states, three legal entities. It is the first system where every site’s muster roll comes out the same way.
Questions
The ones people actually ask.
Anything else — write to us and a person answers.
Can we import from greytHR, Keka or Zoho?
Yes — from a spreadsheet or from greytHR, Keka and Zoho. You set your legal entities, locations and shifts, and the import brings people, structures and history in. The recommendation is then to run a month in parallel with your spreadsheets before relying on it.
Is the payroll output compliant?
Payroll is coming soon: it is held back until a chartered accountant has reviewed its statutory outputs. It computes EPF, ESI, professional tax and TDS under both regimes from dated, source-cited rules — and it is not described as compliant, because no chartered accountant has reviewed the outputs yet. Every rule says so, the run carries the list, and the payslip prints it.
What happens when the trial ends?
Nothing is charged, ever, automatically. Sign-in stops until you choose a plan — ask us and we can extend the trial once. When you take a plan, your paid account starts fresh: nothing from the trial is carried over, so download anything you want to keep first — there is a button for it. If you do not take a plan, everything you entered is deleted thirty days after the trial ends.
More at the full question list, and every guarantee this deployment is not currently keeping is on the security page.
Try it with your own people.
Seven days on the plan you choose, no card. Nothing is ever charged automatically — when it ends you choose a plan, or ask us for more time, and everything you entered is kept for thirty days either way.