Skip to content

03 — Open Source HR/Workforce Platform Landscape

Research date: 2026-04-15

Executive Summary

No single open source project covers all requirements. The landscape divides into (a) broad HR suites covering 40-60% of needs with shallow depth, and (b) specialized tools excelling in one area. Recommendation: build core from scratch, study reference codebases for data models, integrate specialized tools via API.

Tier 1: Full HR Suites

Frappe HR (ERPNext)

  • Stack: Python, JavaScript, MariaDB/PostgreSQL, Frappe Framework
  • License: GPL-3.0 (copyleft — derivatives must be GPL)
  • GitHub: ~2,000 stars (hrms), ERPNext parent 22,000+ stars, 200+ contributors
  • Activity: Very active. Weekly commits, regular releases, strong commercial backing
  • Coverage: Employee management, onboarding, leave, attendance, payroll, expense claims, performance. ~8/13 requirements
  • Gaps: No rostering/scheduling, no document verification, no communication suite, no asset management
  • Architecture: Monolithic Frappe framework with own ORM/UI. Cannot extract HR modules without full stack
  • Verdict: Best open source HR suite. NOT usable as foundation (incompatible stack). Useful as reference for payroll engine logic, leave policies, employee lifecycle workflows

OrangeHRM

  • Stack: PHP 8.x, Symfony, MySQL, Vue.js
  • License: GPL-3.0
  • GitHub: ~985 stars, company-driven development
  • Activity: Active. Version 5.8 Nov 2025
  • Coverage (Open Source): Employee management, leave, basic ATS, time tracking, reviews, reporting. ~6/13 requirements
  • Gaps (Open Source): Payroll enterprise-only, no rostering, no verification, no communication
  • Architecture: Symfony-based (not Laravel). Feature-limited open source to drive paid upgrades
  • Verdict: Closest PHP match but Symfony not Laravel, deliberately stripped features

Odoo Community Edition

  • Stack: Python, PostgreSQL, JavaScript (OWL)
  • License: LGPL-3.0
  • GitHub: 40,000+ stars, 2,000+ contributors
  • Activity: Extremely active. Version 19 released
  • Coverage (Community): Employee directory, attendance, leave, basic recruitment, timesheets. ~5/13 requirements
  • Gaps: Payroll locked behind enterprise license. No rostering, no verification
  • Verdict: Massive ecosystem but open-core model locks best HR features behind proprietary license

TimeTrex Community Edition

  • Stack: PHP, PostgreSQL/MySQL
  • License: AGPL-3.0 (strong copyleft)
  • Activity: Maintained since 2003
  • Coverage: Time & attendance, scheduling, basic payroll, HR management, invoicing. ~5/13 requirements
  • Verdict: Interesting for scheduling/rostering engine and payroll logic. AGPL restrictive for SaaS.

Tier 2: Specialized Tools (Integration Candidates)

Kimai — Time Tracking

  • Stack: PHP 8.x, Symfony 6, Doctrine, MySQL/MariaDB/PostgreSQL
  • License: AGPL-3.0
  • GitHub: 3,500+ stars, very active (daily commits)
  • Relevance: Best-in-class open source time tracking. JSON API, invoicing, plugin system. Reference for time & attendance module.

Cal.com — Scheduling

  • Stack: TypeScript, Next.js, Prisma, PostgreSQL
  • License: AGPL-3.0 (commercial license available)
  • GitHub: 35,000+ stars, 700+ contributors
  • Relevance: Best open source scheduling. Robust API, webhooks, embeddable. Could serve interview scheduling via API integration.

Twenty CRM — Contact Management

  • Stack: TypeScript, React, NestJS, PostgreSQL, GraphQL
  • License: AGPL-3.0
  • GitHub: 43,000+ stars, 300+ contributors
  • Relevance: Excellent architectural reference for CRM-like features. Custom objects, clean architecture.

Mautic — Communication Automation

  • Stack: PHP 8.x, Symfony, MySQL, Doctrine
  • License: GPL-3.0
  • GitHub: 7,500+ stars, 500+ contributors (Mautic 5 released)
  • Relevance: Directly relevant to Reach module. Multi-channel (email, SMS, web, social). Same PHP ecosystem. Could self-host and integrate via API.

Huly — Project Management + HRM + ATS

  • Stack: TypeScript, Svelte, MongoDB-like
  • License: EPL-2.0 (Eclipse — most permissive of all reviewed)
  • GitHub: 25,000+ stars, 345+ releases, daily commits
  • Relevance: Architecture patterns worth studying. EPL-2.0 is business-friendly.

InvoiceNinja — Invoicing/Billing

  • Stack: Laravel, Flutter (mobile), React
  • License: Elastic License (source-available, not OSI open source)
  • Relevance: Most mature Laravel-based business app. Same stack as AgenticAI-app. Architectural reference.

Crater — Invoicing

  • Stack: Laravel, Vue.js, React Native (mobile)
  • License: AGPL-3.0
  • GitHub: 8,000+ stars
  • Relevance: Clean Laravel + Vue.js invoicing. Another Laravel reference codebase.

Tier 3: Not Viable

  • ICE Hrm: ~530 commits, 12 contributors, 8 months inactive. Too small.
  • Sentrifugo: Aging Zend Framework. Not viable.
  • Elixir/Phoenix HR platforms: None exist in open source.
  • Rust enterprise platforms: None production-ready.
  • AI agent market: $7.84B in 2025, projected $52.62B by 2030 (46.3% CAGR)
  • Gartner: 40% of enterprise apps feature task-specific AI agents by end 2026
  • Key frameworks: LangGraph, CrewAI, Mastra, Dify (114K+ GitHub stars)
  • Standards: MCP (Anthropic → Linux Foundation), A2A (Google → Linux Foundation)
  • 61% of enterprise stacks will be MACH-based by 2026

No open source project combines HR operations with AI agent capabilities today. This is the market gap.

Recommendation

Build from scratch:

Scout, Verify, Reach, Pulse core logic. These are the differentiators.

Study for design patterns (do not fork):

  • Frappe HR — payroll engine, leave policies, employee lifecycle
  • Twenty CRM — custom object architecture, GraphQL API design
  • Kimai — time tracking data models, reporting
  • Huly — modular platform architecture

Integrate via API where practical:

  • Mautic for email/SMS campaign orchestration
  • Cal.com for interview scheduling
  • TimeTrex scheduling algorithms as reference

Do not adopt any existing platform as foundation because:

  • No project covers >60% of requirements
  • Best suites use incompatible stacks
  • GPL/AGPL creates SaaS complications
  • AI-native architecture doesn't exist in any current platform
  • Faster to build than integrate + adapt (10-15% savings at most)

Sources

  • OrangeHRM, Frappe HR, Odoo, Kimai, Cal.com, Twenty CRM, Huly, Mautic, InvoiceNinja (GitHub repositories)
  • ERPNext Deep Dive 2026 (devdiligent.com)
  • AI Agent Tools Landscape 2026 (stackone.com)
  • Build vs Buy Decision Framework (neontri.com)
  • Composable HR Architecture (peoplespheres.com)