Interface style
Colour scheme
Writing
Engineering and practitioner writing from the people building ZivoHR — statutory payroll mechanics, leave policy as a set of rules, permission-aware assistants, and the parts of a multi-tenant system that are easy to get wrong. No launch posts.
Every multi-tenant leak we have seen started the same way — a query that forgot which customer it was for. The fix is not more discipline. It is making the forgetful version impossible to write.
The ZivoHR engineering team
Engineering
12 Aug 2026 · 6 min read
During a rolling deploy, the old release and the new one share one database for a few minutes. Adding a column is invisible to old code. Dropping one takes every old container down — so we made the deploy refuse to run destructive migrations.
The ZivoHR engineering team28 Aug 2026 · 7 min readAccrual, pro-rating, carry-forward caps, lapse dates, encashment, per-location holidays, half-days. Every line of a leave policy is a rule, and in most companies a person executes all of them in a spreadsheet every month.
The ZivoHR product team24 Jun 2026 · 7 min readMost assistant demos work because there is one user and nothing confidential. Real HR data has a visibility boundary that runs between colleagues, and an assistant that ignores it is not a feature — it is an incident.
The ZivoHR engineering team7 May 2026 · 7 min readProvident Fund looks like a percentage of a number. It is actually a per-employee rule with a cap, a history and an effective date — which is exactly the shape a spreadsheet formula cannot hold.
The ZivoHR payroll team19 Mar 2026 · 7 min readNothing published under that topic yet.
Book a demo · 30 min
Everything above is how we think about payroll, leave and permissions. A demo is the same conversation, on your own edge cases.