Workforce Suite

Why this suite

Managing a team means three quiet systems that never stop running: who's off and when, who works which shift, and how many hours everyone actually did.

• Three staff tools, three subscriptions, three logins
• One suite: leave & PTO, the weekly rota, and approved timesheets on your own server
• Each installs standalone — adopt them one at a time

Honest limitations — the whole suite

Each product's own limits apply unchanged when it arrives as part of the suite.

Leavora — Staff Leave & PTO Tracker (PHP + MySQL, Self-Hosted)

• 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.

Rostera — Staff Shift Scheduler & Rota (PHP + MySQL, Self-Hosted)

• Not a time clock: it plans and publishes shifts; it does not capture attendance.
• No pay rates, ever — hours and coverage, not wages.
• Swap requests exist; approving a swap is always a human act — there is no automated swap engine.
• Email goes through your own SMTP server; telling staff about a published rota is off until you switch it on.
• Single-tenant: one business per installation.

Clockora — Staff Timesheet & Time Tracker (PHP + MySQL, Self-Hosted)

• Single-tenant: one business per installation.
• Hours only — no invoicing, pricing, rates, wages or payroll. No email can contain a pay figure because the product stores none.
• Overlap detection applies to clock entries (start + end); manual-duration entries have no position on the clock, so a per-employee-per-day 24-hour ceiling refuses the impossible day instead.
• Email sends through your own SMTP server; every staff-facing message is off until you turn it on.
• Reminders need a scheduler: cron/reminders.php must run daily — the app does not run background jobs by itself.

Trainora — Self-Hosted Training Matrix: Competencies, Expiry, Evidence

• It does not issue certificates — no certificate generator; it holds the evidence you were given
• Not a learning platform — no courses, no content, no quizzes, no e-learning, no SCORM
• One tag, not a rules engine — a competency applies to everyone, or to one group
• No self-service login — the people in the register are tracked, not users
• Changing a competency's validity does not rewrite records already on file
• Single-tenant: one organisation per installation

Onboardora — Self-Hosted Employee Onboarding: Checklists, Owners, Derived Dates

• Not an HR system of record — no payroll, no salaries, no contracts of employment, no holiday tracking
• No right-to-work or background-check verification — you can tick that the check happened, it does not perform it
• No payroll/HRIS connector — REST API, signed webhooks and MCP are there; wiring them is yours
• No offboarding — equipment tracks issue and return, but there is no leaver flow
• No employee self-service login — tasks owned by the starter are chased by email
• Single-tenant: one company per installation
• Not legal advice — what belongs on a checklist where you operate, and how long you keep the record, are your decisions