Horilla

Open-source HR software, honestly reviewed. No marketing fluff, just what you get when you self-host it.

TL;DR

• What it is: Open-source (LGPL-2.1) HRMS covering recruitment, attendance, payroll, leave, performance management, and onboarding — in a single self-hosted application [3].
• Who it’s for: Small-to-medium businesses willing to self-host a Django app that want to stop paying per-employee on BambooHR or Freshteam. Also relevant for companies in markets like India, UAE, and Nigeria where the project explicitly targets [2].
• Cost savings: BambooHR starts around $6–9/employee/month — a 50-person company pays $300–450/mo. Horilla is free software; your only cost is a server [website].
• Key strength: The most complete all-in-one HR feature set in the free/open-source category — biometric integration, OKR-based performance management, and payroll in a single codebase [website][3].
• Key weakness: 1,103 GitHub stars and virtually no independent third-party reviews. The project is largely unknown outside Southeast Asian and South Asian markets, and the licensing (LGPL-2.1) adds legal review overhead that MIT-licensed alternatives don’t [3][merged profile].

---

What is Horilla

Horilla is a Django-based HRMS built by an Indian software team and published under the LGPL-2.1 license. The GitHub description calls it “a free and open source HR and CRM software,” and the website is blunter: “the only comprehensive HR software solution that’s absolutely free” [website][README].

The scope is wide. Horilla tries to cover the full employee lifecycle in one application: recruitment pipeline, candidate tracking, onboarding workflows, employee directory (with LDAP sync), attendance (including biometric device integration), leave management, asset tracking, payroll with contract management, and a performance management module built around OKRs and 360° feedback [website]. There’s also a CRM module listed in the sitemap, which suggests the project is expanding beyond pure HR [2].

It’s built on Python/Django with PostgreSQL as the database, which puts it in the same architectural family as older enterprise software rather than the Node.js wave that powers most newer SaaS entrants. Deployment paths include Docker (published to Docker Hub as horilla/horilla), pip install into a Python virtualenv, or a shell script installer [README]. A mobile app is mentioned on the homepage, though details are sparse [website].

As of this review, Horilla sits at 1,103 GitHub stars and 779 forks — a modest number that reflects either early-stage adoption or a user base that skews toward private enterprise deployments rather than the hobbyist self-hosters who drive GitHub stars [3][merged profile].

---

Why people choose it

The honest answer is that independent third-party reviews of Horilla are nearly absent from English-language sources. What exists is Horilla’s own comparison blog posts pitting itself against BambooHR, Freshteam, Monday HR, OrangeHRM, Sentrifugo, and Kredily — written by Horilla’s own team [2]. That’s a yellow flag worth naming directly.

What we can synthesize from available sources:

The “free vs paid” framing is Horilla’s entire pitch. The sitemap reveals a pattern: every comparison page is titled “Free vs Paid: Horilla HRMS vs [Competitor]” [2]. This tells you exactly who they’re targeting — organizations that are currently paying for a named HRMS and doing the math on switching. The website repeats “100% free,” “free of cost,” and “host it wherever you like” as primary value propositions, not feature depth [website].

The Indonesian on-premise HRIS roundup [5] — which covers the Southeast Asian market where Horilla has some traction — frames the appeal in terms of data sovereignty: on-premise HRMS keeps employee data on internal servers, away from third-party cloud providers. For companies in markets with specific data residency requirements (a common concern in Indonesia, India, and the Middle East), that argument has real weight [5].

OpenAlternative describes Horilla as a “comprehensive open-source HR management solution” that “streamlines HR processes, from recruitment to offboarding” [3]. That’s accurate but generic. The more useful signal is the 779 forks against 1,103 stars — a fork-to-star ratio of roughly 0.7, which is unusually high. High fork counts relative to stars often indicate enterprise users who fork privately to customize rather than star publicly — consistent with the kind of company that would self-host HR software.

The absence of Trustpilot, G2, or Capterra coverage is notable. It doesn’t mean the product is bad, but it means you can’t triangulate against user experience data the way you can with something like OrangeHRM or Factorial.

---

Features

Based on the README and website, Horilla covers:

Recruitment:

• Job posting management and application forms [website]
• Recruitment pipeline with configurable stages [website]
• Candidate tracking with skill zones [2]
• Interview scheduling [2]
• Candidate self-service portal for application status [website]

Onboarding:

• Task assignment workflows for new employees [2]
• Configurable onboarding stages [website]
• User-level permissions for onboarding steps [2]

Attendance:

• Web check-in/check-out with time runner [2]
• Biometric device integration [website]
• Overtime calculation [website]
• Late arrival and early departure tracking [website]
• Work type requests and rotating shifts [2]

Leave:

• Employee leave applications and approval workflows [website]
• Leave balance tracking and accrual management [website]
• Customizable approval rules (by duration, project, additional layers) [website]
• Leave dashboard [2]

Employee management:

• Employee directory with role, department, hierarchy tracking [website]
• LDAP integration for data sync [website]
• Disciplinary action management [2]
• Employee offboarding workflows [2]

Performance (PMS):

• OKR-based goal setting with alignment to company goals [website]
• 360° feedback from multiple sources [website]
• Continuous performance review cycles [website]

Payroll:

• Contract and agreement management [website]
• Allowance and deduction configuration [website]
• Payroll processing (details sparse in available sources)

Assets:

• Asset allocation and request tracking [website]
• Maintenance scheduling [website]
• Audit trails for compliance [website]

Employee helpdesk: Listed in the sitemap; details not available in scraped content [2].

CRM: Listed as a separate module on the navigation; scope unclear from available data [2].

---

Pricing: SaaS vs self-hosted math

Horilla’s pricing model is simple: $0 for the software. There is no cloud SaaS tier, no per-seat pricing, no feature gating. LGPL-2.1 means you can self-host it, modify it, and use it commercially — with the obligation that if you distribute modified versions of Horilla itself, you publish the source changes [README][merged profile]. For internal company use, LGPL places no meaningful restrictions on what you do with it.

What self-hosting costs:

• Software: $0
• Server: $10–20/mo for a VPS with 4GB RAM (PostgreSQL + Django + Redis if needed)
• Your time or a one-time deployment service

For comparison, what competitors charge per month:

• BambooHR: ~$6–9/employee/month (pricing not publicly listed; widely reported in that range). 50 employees = $300–450/mo.
• Freshteam: free tier up to 50 employees, then ~$1.20–4.80/employee/month depending on plan.
• Monday HR: based on Monday.com pricing (~$9–16/seat/month).
• OrangeHRM: open-source community edition free; Professional plan pricing on request.
• Sentrifugo: open-source, self-hosted only.

Note: Exact competitor pricing is not available in the provided sources — figures above are approximate and should be verified before financial planning.

Concrete math for a 50-person company:

If you’re paying BambooHR at $8/employee/month: $400/mo, $4,800/year. Horilla self-hosted on a $15 VPS: $180/year. Delta: ~$4,600/year — enough to pay a developer for a day or two to set it up and maintain it. The math becomes more dramatic as headcount grows, since SaaS HR pricing scales linearly with employees while your server cost stays flat.

The caveat that always applies: the “free” software isn’t free of the cost of your time. Someone has to set it up, update it, back up the database, handle the inevitable Django migration that fails on a minor version upgrade.

---

Deployment reality check

The README installation path has a rough edge worth flagging: it does not lead with Docker Compose. Instead, the primary documented path is clone the git repo → set up a Python virtualenv → install pip dependencies → configure PostgreSQL manually → run Django migrations. That’s a 20-step process aimed at developers who are comfortable with the full Python stack [README].

Docker is available (horilla/horilla on Docker Hub) but the README focuses on the manual installation path for Ubuntu, Windows, and macOS in sequence, which suggests Docker is not the primary path the team dogfoods [README][merged profile].

What you actually need to run this:

• A Linux server (Ubuntu documented; other distros on your own)
• Python 3 installed and managed
• PostgreSQL, set up with a specific database and user
• pip and virtualenv
• A Django-literate person for ongoing maintenance — or willingness to become one

What can go sideways:

• Django projects accumulate migration debt. Version upgrades can break running instances if you’re not tracking upstream carefully.
• Biometric device integration is listed as a feature but requires compatible hardware — no specifics in available documentation [website].
• LDAP integration is mentioned but configuration details aren’t in any scraped source [website].
• CRM module scope is completely undocumented in available sources [2].
• No evidence of REST API surface for external integrations — important if you need to connect Horilla to your accounting software, ERP, or Slack.

Realistic time estimate: A Django developer can have a working instance in 1–2 hours. A non-technical founder following documentation carefully: 4–8 hours, with real risk of getting stuck on PostgreSQL configuration or dependency conflicts. If you’ve never managed a Python application in production, budget for either a technical hire or a deployment service.

---

Pros and cons

Pros

• Genuinely free, LGPL-2.1. No per-seat fees, no feature gating, no “community vs enterprise” split that hides critical features behind a paywall [website][README].
• Broadest feature set in the free HRMS category. Recruitment, payroll, performance management (OKRs + 360°), biometric attendance, and asset tracking in one application is unusual for a free tool [website].
• Self-hostable on your own infrastructure. Your employee data never touches a vendor’s cloud [website][5].
• Active development. OpenAlternative shows last commit 11 hours ago at time of listing [3] — not an abandoned project.
• Biometric integration. Rare even in commercial HRMS products at the small business tier [website].
• Comparison pages against competitors exist for BambooHR, Freshteam, OrangeHRM, Monday HR, Sentrifugo, and Kredily — useful for migration research [2].
• Mobile app listed on the homepage, though details are thin [website].

Cons

• Virtually no independent English-language reviews. You’re flying mostly blind on real-world production experience. High fork count hints at private enterprise use, but public user experience data is absent [3].
• LGPL-2.1, not MIT. Technically more restrictive than MIT for redistribution and embedding in other software. For internal use this doesn’t matter, but it adds a legal review step that MIT eliminates [merged profile].
• Django/Python stack requires maintenance. If your team doesn’t speak Python, dependency management and Django version upgrades are ongoing costs [README].
• Installation path is developer-first. No one-click install, no managed cloud tier, no “copy this docker-compose.yml and you’re done” documentation in the primary path [README].
• 1,103 GitHub stars is low for an HRMS you’re trusting with payroll and employee records. Compare: OrangeHRM has been around for 20 years and has a much larger known user base [3].
• Documentation depth is unclear. The sitemap shows video tutorials for common tasks [2], but no evidence of API documentation or advanced configuration guides in available sources.
• CRM module is unexplained. Its scope, feature set, and relationship to the HRMS modules is undocumented in any scraped source [2].
• No evidence of REST API for integration with external tools — a significant gap if you need to connect your HRMS to accounting, Slack, or your own internal systems.

---

Who should use this / who shouldn’t

Use Horilla if:

• You’re a 10–200 person company in India, Southeast Asia, or the Middle East currently paying per-seat for BambooHR or Freshteam and you have (or can hire) someone comfortable with Python/Django.
• Data residency matters — your employee data cannot leave your own servers for regulatory or policy reasons [5].
• You want biometric attendance integration without paying for enterprise HRMS pricing.
• You’re open to spending a few days on deployment in exchange for eliminating a $300–500/mo recurring bill.
• Your HR team doesn’t need 24/7 vendor support — you’re self-sufficient.

Skip it if:

• You have fewer than 10 employees and the problem isn’t expensive enough to justify self-hosting complexity.
• Your team has no Python/Django experience and no budget for a one-time deployment service.
• You need verified third-party reviews, SOC 2 compliance, or an auditable SLA. Horilla offers none of these publicly.
• Your HR stack needs to integrate with external tools via API — no evidence of a REST API surface.
• You’re in the US or EU market and want a tool with an established support community in your timezone and language.

Consider OrangeHRM instead if:

• You want a more battle-tested open-source HRMS with 20 years of production use and a larger community.
• You need professional support options without going full commercial.

Stay on BambooHR/Freshteam if:

• Your compliance requirements demand vendor accountability and documented SLAs.
• You want product support, not a Django app to maintain.
• You need deep integrations with your existing SaaS stack (ATS, payroll processors, benefits providers).

---

Alternatives worth considering

• OrangeHRM — the original open-source HRMS. Longer track record, larger community, also self-hostable. Has a commercial “Professional” tier for support contracts. More English-language documentation and reviews than Horilla.
• Sentrifugo — another open-source HRMS option, though development pace has been slower. Mentioned directly in Horilla’s own comparison pages [2].
• Factorial HR — commercial SaaS, similar feature scope to Horilla but with managed cloud, support, and integrations. Price: ~€4–9/employee/month.
• BambooHR — the commercial incumbent in the SMB HR space. Polished product, large integration catalog, ~$6–9/employee/month.
• Freshteam — Freshworks’ HRMS offering. Free tier for up to 50 employees, broader integration ecosystem than Horilla.
• Krayin — if you specifically need the CRM half of what Horilla offers (22,189 GitHub stars, more established) [3].

---

Bottom line

Horilla is the right answer to a specific question: “I need a complete HRMS with payroll, performance management, and biometric attendance, I’m paying too much for commercial software, and I have someone who can manage a Django application.” If all three conditions are true, the math is clear — $0 software versus $300–500/month is an obvious call, and the feature list is genuinely impressive for a free project.

The gaps are real. Independent production reviews don’t exist yet in English. The install path assumes a developer. LGPL-2.1 adds a legal checkbox. There’s no evidence of a REST API for integrations. These aren’t fatal if your context matches, but they’re the costs you pay for the price tag.

For non-technical founders in the US or EU market looking for the easiest off-ramp from BambooHR, Horilla is a stretch — the setup complexity is real and the support community is thin in English. For a technically-equipped SMB, particularly one in South or Southeast Asia where the project has its strongest footprint, it’s worth a serious evaluation. That’s what unsubbed.co exists to help you decide — and if deployment is the blocker, that’s exactly the problem upready.dev solves.

---

Sources

1. Horilla Blog — “How to Use Dataloader.io in Salesforce Like a Pro” (Horilla’s own site, used for context on CRM module presence). https://www.horilla.com/blogs/how-to-use-dataloaderio-in-salesforce-like-a-pro-full-guide/
2. Horilla Sitemap (used for feature module list, comparison pages, and video documentation index). https://www.horilla.com/sitemap/
3. OpenAlternative — Open Source Projects tagged “Opensource” (Horilla listing: 1,129 stars, 779 forks, last commit 11 hours ago). https://openalternative.co/tags/opensource
4. OpenAlternative — Open Source Projects tagged “Django” (category context). https://openalternative.co/tags/django
5. Rifka Qonita, LinovHR Blog — “10 Rekomendasi Software HRIS yang Menyediakan On-Premise” (February 5, 2026). https://www.linovhr.com/blog/software-hris-on-premise/

Primary sources:

• GitHub repository and README: https://github.com/horilla-opensource/horilla (1,103 stars, LGPL-2.1 license)
• Official website: https://horilla.com
• Docker Hub: https://hub.docker.com/r/horilla/horilla