Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Payroll Engine

payrollengine.org

  • Free plan
  • Windows
  • macOS
  • Linux
  • Web
  • API
  • Self-hosted
8.3 Club score Visit payrollengine.org

What Payroll Engine is

Payroll Engine is an open-source framework for adding payroll processing to other software platforms. Its backend handles payroll data through a REST API with configurable regulation layers, supporting time-stamped data and recurring or one-off payruns. It can produce payslip, legal-filing, and data-exchange reports. The MIT-licensed framework is free, but country regulations are commercial. The API covers tenant and employee management, payrun jobs, result queries, report output, and backend event webhooks. A browser-based application provides management for tenants, employees, regulations, case data, payruns, reports, tasks, and developer logs. Developers also get a .NET Client SDK with typed REST clients, test runners, local script tools, and JSON schemas for regulation validation. A built-in test framework handles case validation, payrun assertions, and regression testing. The backend can run locally or through Docker Compose, but needs a separately provided database. API key and OAuth authentication are available, though authentication and audit trails are disabled by default. The maker says the backend is a service and should not be used on the public Internet.

Who it suits

It suits HR-tech and EOR platforms, payroll consultants, HR specialists, and DevOps or integration engineers building payroll workflows into larger systems.

Good to know, and what to watch

  • MIT-licensed, open-source framework is free.
  • Supports recurring and non-recurring payruns.
  • Includes case validation and regression testing tools.
  • Browser app manages payroll operations and developer logs.
  • Country regulations are commercial.
  • Database must be provided separately.
  • Authentication and audit trails are disabled by default.
  • Maker says not to use the backend on the public Internet.

Open-source framework

Free

Open source

Getting started

  1. Open the Payroll Engine website
  2. Deploy the backend locally or with Docker Compose
  3. Provide a separate database
  4. Configure API key or OAuth authentication
  5. Use the REST API, .NET Client SDK, or browser application
  6. Add regulation layers, tenants, employees, and case data

Limits to check

The free Open-source framework plan costs nothing and has no per-employee fees or runtime licenses. Country regulations remain commercial and are offered through the companion payrollex.io marketplace.

The Club's review

Payroll Engine is a framework for building payroll processing into another software platform. It suits HR-tech and EOR teams, payroll specialists, and integration engineers who can operate a backend and configure payroll rules. Its developer tooling is substantial, but adopting it also means arranging country regulations and handling deployment and security.

Overview

The MIT-licensed framework captures wage-related case data, calculates wages in payruns, and generates reports such as payslips and legal filings. Its configurable regulation layers can be versioned, combined, and shared across tenants, giving platform builders room to shape payroll workflows around their products. That flexibility comes with a meaningful boundary: the framework is open source, while country regulations are commercial and offered through the payrollex.io marketplace.

Payroll Engine is designed to run locally or through Docker Compose, with a database supplied separately. A browser-based app supports management of tenants, employees, regulations, case data, payruns, reports, tasks, and developer logs. This is a useful working surface for teams building or integrating payroll, but it does not turn the framework into a ready-to-run hosted payroll service.

Key features

The REST API handles tenant and employee management, payrun jobs, result queries, report output, and backend event webhooks. Time-stamped case values with validity periods preserve changes over time, enabling retrospective recalculation and an audit history. Forecasts support isolated what-if scenarios without changing legally valid payruns, which helps teams explore outcomes while keeping production payroll separate.

Payroll rules can be extended through No-Code case actions and C# scripting. A built-in test framework supports case validation, payrun assertions, and regression checks, while the .NET Client SDK adds typed REST clients, local script tools, test runners, and JSON schemas for regulation validation. The SDK also supports JSON and Excel import and export, bulk operations, and CLI extensions. Together, these tools give engineering teams ways to automate and verify payroll work; they will be less compelling to buyers who want payroll configured and maintained for them.

Security needs deliberate setup. The backend supports API key and OAuth authentication, but authentication is disabled by default. Audit trails can be configured by category and are also disabled by default. The maker says the backend is a service and should not be used on the public Internet, so deployment needs to respect that restriction.

Pricing

The Open-source framework plan costs nothing. It includes the MIT-licensed framework, with no per-employee fees or runtime licenses. That makes it a practical starting point for teams evaluating or building an embedded payroll system, but the zero-cost framework does not include country regulations, which are commercial. The overall cost of a production setup therefore depends on those regulations and the infrastructure the adopting team supplies.

Platforms

Payroll Engine lists API, Linux, macOS, self-hosted, web, and Windows support. The deployment model suits teams that want to operate the backend locally or with Docker Compose and use a browser-based management app, though they must arrange the database separately.

Who it's for

The strongest fit is an HR-tech or EOR platform that wants payroll processing as part of its own product, or a payroll consultant or HR specialist working with engineers to configure rules and workflows. DevOps and integration engineers will find a clear role in connecting the API, managing deployment, and automating tests. Organizations seeking a finished payroll service with infrastructure and country rules bundled should look elsewhere.

Pros and cons

  • Pros: MIT licensing and no per-employee or runtime license fees make the framework accessible for embedding and experimentation.
  • Pros: Versioned regulation layers, time-aware records, and isolated forecasts support adaptable payroll workflows and retrospective recalculation.
  • Pros: API, SDK, scripting, and regression-testing tools give engineering teams several ways to integrate and validate payroll operations.
  • Cons: Country regulations are commercial, so the free framework alone does not supply a complete country-specific payroll setup.
  • Cons: A separate database and backend operations put deployment work on the adopting team.
  • Cons: Authentication and audit trails are disabled by default, and the maker says not to use the backend on the public Internet.

Alternatives

Compare global payroll software if you are choosing among broader payroll products rather than a framework to embed.

PHPPayroll is another option for teams seeking a free, open-source, self-hosted payroll edition across Linux, macOS, web, and Windows.

Dapplon Global Payroll may suit buyers looking for a paid payroll product with a free trial and Android or iOS access.

Paybooks is another paid option with a free trial and payroll, leave-management, employee self-service, and statutory-compliance features in its Xplore plan.

Better HR is a paid alternative with a free trial and Android and iOS apps.

Omni HR Payroll is a paid option with a free trial, multi-country support, digital payslips, statutory filing, and accounting integration.

BIPO HRMS Payroll is a paid alternative for buyers who want to request a free demo.

Rippling offers a custom plan built around its core platform, with products purchasable separately and most billed per employee per month.

UKG Pro Benefits Hub is a paid option for organizations seeking benefits administration through the UKG Pro subscription service.

Verdict

Choose Payroll Engine if you are building an HR-tech or EOR platform and want an open-source framework with API, scripting, and testing tools for embedding payroll. The main reason to choose it is the control its configurable rules and developer tooling give an integration team. Look elsewhere if you need a turnkey payroll service: country regulations cost extra, and the backend, database, and security setup remain your responsibility.

The verdict

Payroll Engine provides payroll processing components and developer tools for teams embedding payroll into another platform. Its separate database requirement, commercial regulations, and stated restriction against public-Internet use are important deployment considerations.

Questions people ask

What does Payroll Engine cost?

The Open-source framework plan is free. The framework is MIT licensed, while country regulations are commercial.

Which platforms does it support?

It supports API, Linux, macOS, self-hosted, web, and Windows environments.

Is Payroll Engine open source?

Yes. The framework is released under the MIT License.

How can developers integrate it?

The REST API is the programmatic integration surface, and the .NET Client SDK provides typed clients and automation tools.

Does it include testing tools?

Yes. Testing supports case validation, payrun assertions, report-result checks, regression testing, and test runners.

Can it run publicly on the Internet?

The maker describes the backend as a service that should not be used on the public Internet.

What the maker publishes

Commercial limits
The framework is MIT licensed, while country regulations are commercial and offered through the companion payrollex.io marketplace. source
Commercial regulations
The framework is open source, while country regulations are commercial. source
Compliance and audit
Audit trails can be configured by category and are disabled by default. source
Deployment
The backend is designed to run locally or through Docker Compose, and its database must be provided separately. source
Deployment
The maker distributes pre-built Docker images for the backend, web app, and Payroll Console, with the full stack started using Docker Compose. source
Developer tooling
The Client SDK supports JSON and Excel payroll or regulation import/export, test runners, bulk operations, and CLI extensions. source
Developer tools
The .NET Client SDK provides typed REST clients, test runners, local script development tools, and JSON schemas for regulation validation. source
Features
The engine supports time-stamped payroll data, recurring and non-recurring payruns, and reports for payslips, legal filings, or data exchange. source
Forecasts
Forecasts support isolated what-if scenarios that do not affect legally valid payruns. source
Founded
2018 source
Headquarters
Switzerland (author's location; no company headquarters stated) source
Integration
A REST API is the programmatic integration surface, and a .NET Client SDK supports automation workflows. source
Integrations
The REST API supports tenant and employee management, payrun jobs, result queries, report output, and backend event webhooks. source
Intended users
The maker identifies HR-tech and EOR platforms, payroll consultants and HR specialists, and DevOps or integration engineers as its main roles. source
License
The framework is released under the MIT License. source
Payroll processing
Its backend processes payroll data through a REST API using configurable regulation layers. source
Payroll workflow
It captures wage-relevant case data, calculates employee wages in payruns, and generates reports such as payslips and legal filings. source
Product
Payroll Engine is an open-source framework for embedding payroll processing into larger software platforms. source
Regulation layers
Payroll rules are configurable, versioned layers that can be combined and shared across tenants. source
Security
The backend supports API key and OAuth authentication, while authentication is disabled by default. source
Security
The maker warns that the backend should not be used on the public Internet and documents None, API key, and OAuth authentication modes. source
Security limit
The maker says the backend is a service and should not be used on the public Internet. source
Support
The project directs questions and feature requests to GitHub Discussions, bug reports to GitHub Issues, and says to allow a few business days for responses. source
Support
Questions and feature requests go to GitHub Discussions, bugs to GitHub Issues, and the maker asks users to allow a few business days for responses. source

Checked against the maker's pages on 9 Oct 2026.