Product engineering
Multi-tenant back ends and modern web front ends built as one product, from the first migration to the shipped screen.
Independent software company
Larva designs, builds and operates multi-tenant SaaS products end to end — schema to sign-in, billing to backups. Our flagship product, Leaveo, is leave management that shows its arithmetic.
What we do
Most of what breaks in software lives in the seams — between the schema and the API, the API and the screen, the screen and the invoice. We keep the seams inside one team.
Multi-tenant back ends and modern web front ends built as one product, from the first migration to the shipped screen.
Infrastructure as code, immutable release artifacts, expand-and-contract migrations, tested restores and a written recovery plan.
A validation pyramid with the server as the authority, tests traced back to numbered requirements, and a gate that has to be argued with.
A tokenised design system, WCAG AA contrast floors as a build rule, and full right-to-left support rather than a mirrored afterthought.
Our product
LeaveoLeaveo is Larva's leave and vacation management product for distributed teams. Every charged day carries its reason: the dates counted, the dates skipped, and the workforce group policy that produced the result — visible before a balance changes, and still attached to the record after approval.
Illustrative working-day calculation
3 working days will be charged.
Monday 14 September to Friday 18 September 2026
Policy source — example workforce group · Friday–Saturday weekend · group holiday on 16 September. This is a policy example, not customer data.
How we work
Our delivery method is written down and applied to every change, whether it is a new epic or a one-line fix.
Requirements are numbered and traceable. Nothing is built against a conversation; it is built against a document that can be reviewed and disagreed with.
Priority-zero acceptance criteria get a red-phase test before implementation starts, so "it works" means something specific rather than something hopeful.
Independent review layers look for the failure the author did not imagine — data integrity, tenancy boundaries, migration safety, edge cases.
Every requirement is mapped to the tests that actually cover it. The gate reads that map, not a green checkmark on a dashboard.
Expand-and-contract migrations, one-version compatibility between old and new processes, and a rollback path that does not depend on luck.
The work, in numbers
Straight answer on status. Leaveo's core leave workflow, notifications, workforce groups, holidays, team calendar, self-service registration and paid checkout are built. Advanced reporting, chat and calendar integrations exist behind feature controls and are described as available only once they are released. We would rather tell you the release horizon than sell you a roadmap.
Whether you want Leaveo for your team or a product partner who will own the whole line, the first conversation costs nothing and commits nothing.