LeavoraStaff Leave & PTO Tracker
Self-hosted staff leave & PTO — accruals, working-day requests, approvals, and live balances.
No sign-up, no password — the demo opens already signed in, on sample data.
- Full PHP source included
- Instant download + licence key
- It never phones home
- Compare vs SaaS pricing →
The problem it solves
For most small teams, "how much leave do I have left?" is a question only a shared spreadsheet can answer — and it is usually wrong. Accruals drift, half-days get miscounted, public holidays land inside a leave request, and two people book the same week off without anyone noticing. HR platforms fix all of it, then charge per employee, every month, forever.
- Balances that drift because the spreadsheet formula was off by a day
- Weekends and public holidays counted as leave by mistake
- Per-employee monthly SaaS pricing for what a team of twelve needs a few times a year
What you get
Invite an employee from their record and they get their own login: their balances, their history, and a request form — nothing else. The invite is bound to that employee, approving stays admin-only, and revoking access never touches their leave history.
Approved or declined, the employee is told by email — dates, type, days, who decided. Off by default, through your own SMTP, and it fires from the same code path whether the decision came from the browser, the API or an agent.
A token-guarded .ics feed (team-wide or per person) your Google/Outlook/Apple calendar subscribes to. One-time URL shown once; revoke a token and the feed goes dark.
Each employee has a manager, a start date, and start-date-prorated accrual, so someone who joined in April earns the right fraction of the year's entitlement.
Annual, sick, unpaid, or custom leave types, each with an accrual rule (annual up-front or monthly) and a carryover cap that never compounds across the leave-year boundary.
A company holiday calendar and a configurable weekend are excluded from every working-day count, so a request that spans a bank holiday charges the right number of days.
Working days are computed automatically, overlaps and double-requests are caught, half-days are supported, and each request runs a pending to approved or rejected workflow with approver and timestamp.
Carried-in + accrued − taken − pending, as of any date, kept to the hundredth of a day in integer centidays — so a full year of monthly accrual lands exactly on the entitlement with zero float drift.
A month grid of who is off with weekends and holidays shaded, a dependency-free per-employee PDF leave statement, and a formula-injection-hardened CSV export.
Add it to a phone or tablet home screen straight from the browser — a full-screen app served from your own server, with no app store involved. Business data is never cached offline, so what you see is always live.
Leavora 2.0 adds the 2.0 owner layer. Upgrade by replacing the files — the database migrates itself, and it is still the same one-time purchase.
- REST API with an OpenAPI spec and signed webhooks
- Two-factor sign-in (TOTP)
- Email notifications through your own SMTP
- CSV import with a mandatory dry run
- One-click backups
- Dark mode
Decide-once now lives in a single function that browser, REST API and agent all pass through — a test asserts exactly one status-update site exists in the whole product. Deciding is deliberately separate from submitting, and six MCP tools work the same request cycle people do.
- Roles with email invitations and a last-admin guard
- Append-only audit trail across browser, API and agent
- Printable PDFs
- Your logo and colours throughout
- Scheduled backups with a guided dry-run restore
- Optional single sign-on (OIDC)
The 3.1 wave gave the catalogue a way to reach the other side of the transaction: counterparty email through your own SMTP server, calendar feeds your own calendar subscribes to, attachments filed where the paperwork belongs, and export presets other people's software imports. Every outbound path ships switched off, runs on your own credentials, and can never break the thing that triggered it. What this app gained is listed at the top of this section.
Pricing — one-time, yours forever
- ✔ Full source included — PHP you can read and change
- ✔ No subscription. One payment, yours forever
- ✔ It never phones home
- ✔ Your data stays on your server
Which licence do I need?
It comes down to how many installations you need. Running your own business on one site is the Single licence. Building or running sites for other people — a second domain of your own, or an installation a client keeps — is the Extended licence.
Single licence
One (1) domain or subdomain
One business, running it on one site.
- Install it on one domain or subdomain you own or operate
- Change the source however you like for that installation
- Run your own business on it commercially, client work included
- Re-download the current build any time from your buyer portal
- A second site, or an installation you hand to a client as theirs, needs the Extended licence
- No reselling, redistributing or sublicensing the source
- Not for offering it to other people as a hosted service
Extended licence
Unlimited sites you own or operate
Agencies, and anyone running it on more than one site.
- Everything the Single licence grants
- Install it on as many domains as you own or operate — no cap on the number
- Build and hand over one installation per client project
- Still no reselling or redistributing the source itself
- Running it as a multi-tenant service others sign up for needs a SaaS agreement
Every download carries the full terms as LICENSE.txt, and the licence you bought is
named on your order and in your buyer portal. The complete wording lives on the
terms page, and the live demo is free for as long
as it takes to decide.
No reviews yet — so here is what we offer instead. Every competitor price on our comparison pages is source-linked and dated, and when a vendor’s price won’t load we say so rather than guess. See the sources for yourself →
Honest limitations
What it does not do — written down before you buy, and kept true on purpose.
- Single-tenant: one business per installation.
- Records leave only — no payroll, no wage calculation, no HRIS integration.
- Approving is always an administrator's act; self-service employees request but never decide — including their own request.
- Carryover is a single cap per leave type; tenure tiers, negative balances and part-time proration by hours are out of scope by design.
- Monthly accrual credits a month only when the employee was employed at its start (no partial-month pro-rating), so balances imported from a pro-rating system can read slightly higher.
- Email sends through your own SMTP server; every employee email is off until you turn it on.
2-minute web installer, plain PHP 8 + MySQL (or SQLite for a trial), no Composer or build step — Docker image included.
Covered in these guides
The limitation-smash release: your tools now write to the people they serve — client emails through your own SMTP, calendar feeds, attachments, export presets — every one of them off until you switch it on.
Platform, rota, waivers, leave, equipment. Five subscriptions priced from each vendor's own page, totalling $2,232 a year — and the single largest line is the one most gyms should not be buying at all.
Till, rota, leave, food-safety checks, expenses. Five subscriptions nobody reviews, priced from each vendor's own page. The total is $2,214 a year — and roughly half of it can be removed without buying anything.
Timetastic charges per person forever and Vacation Tracker enforces a EUR 50 monthly minimum. Here is the three-year math from both vendors' own pricing pages, and the self-hosted leave tracker nobody's comparison page mentions.
Six tracked vendors publish a minimum monthly charge under their headline per-user price. We worked out where each floor bites, from the vendors' own pricing pages. Below those thresholds, the advertised rate is decorative.
Questions about Leavora
Is Leavora payroll?
No — it tracks leave entitlement, requests, approvals, and balances only. It never calculates wages, touches cards or bank rails, or initiates a payment, so it has zero payroll and zero payment surface.
How exact are the balances?
Exact by construction: leave is stored in integer centidays (a hundredth of a day), so half-days and monthly accrual are precise and a full year's accrual lands exactly on the entitlement. The shipped 147-assertion suite covers accrual, carryover, and both DST transitions.
Can I use a fiscal leave year, not the calendar year?
Yes — the leave year is configurable (calendar or a fiscal start such as April 1), and carryover is capped at that boundary.
Does it handle half-days and public holidays?
Yes — requests can be half-days, and a company holiday list plus your configured weekend are excluded from every working-day count.
What if the developer disappears?
You get the full PHP source and your data lives in one database you own — nothing phones home, nothing expires.
Can employees log in themselves?
Yes — invite an employee from their record and they get a self-service login showing their own balances and history, with a request form that runs through the exact same working-day maths and overlap checks as the admin form. They can request; only an administrator can decide.