IceHRM

IceHRM's Docker stack builds three containers — the application, a MySQL 8 database seeded from docker/init.sql, and a background worker — and from version 36 the app checks for a newer release itself, banking the current install aside before replacing anything. That self-update path, plus a modular extension system exposed through a REST API, sets IceHRM's open-source core apart from self-hosted HR tools that ship a monolith and leave upgrades to a manual script.

Why IceHRM instead of BambooHR

BambooHR covers the ground IceHRM's community edition does: employee records, an org chart, leave requests against a team calendar, and a self-service portal where staff check their own balances. Where BambooHR adds polish — guided onboarding checklists, an applicant tracking system, review cycles — IceHRM gates the equivalent modules behind IceHrmPro, a paid extension under the Elastic License v2, not the GPL-3.0 core. The open-source install you actually run is closer to a records-and-leave system than a full HCM suite.

The performance case is about where the app lives, not raw throughput. BambooHR bills per employee per month — third-party pricing trackers put the entry tier around $6-10, more on higher plans — and every request crosses the public internet to BambooHR's infrastructure. IceHRM's PHP/MySQL stack runs on a machine you size and place: a VPS near your team, on a private network if needed, with no vendor rate limit between staff and their own leave balances. The tradeoff is that you own uptime and backups instead of a vendor's SLA.

What it does well

• Centralized employee records — job history, qualifications, documents, dependents — browsable as a list or an org chart.
• Leave management with configurable leave types, a work-week and holiday calendar, and manual adjustments an admin can post directly.
• A team leave calendar that lays absences across the month so clashes surface before approval, not after.
• Punch-based attendance with per-employee history and an overtime request-and-approval flow on top.
• Client and project tracking with employees assigned per project, and weekly timesheets with an approval step — useful for agencies billing hourly.
• A REST API and extension architecture for scripting integrations instead of waiting on a vendor roadmap.
• Self-updating installs from v36 that preserve , and installed extensions, with rollback from the same screen.