An unusual start
The back end that runs Mintage Workforce today was created on 23 January 2026, but it did not start out as an HR system. For its first week it was a small internal tool for tracking outgoing messages and their replies. Over a few busy days it gained password sign-in, background jobs, notifications, a dashboard with exportable reports, a date range picker and the plumbing needed to deploy it reliably. The clock was set to Guyana time, and the many small fixes in the log are what getting a new app to run smoothly looks like.
We mention this because it is the honest history of the code. Most of those 111 commits were about that first tool, not about HR.
Clearing the ground
On 30 January the messaging features were removed. What was left was a clean, general-purpose starting point: a single-page web app with sign-in, user accounts, background jobs, logging and a tested way to build and deploy. By the end of the day an admin could add new users, and the icons and documentation had been tidied up to match.
That clean base was exactly what the HR product needed. The first Workforce front end from 2024 had shown which features mattered, but it needed a modern back end of its own that could share employee data properly with Mintage Payroll.
What came next
In the first week of February this starter app was renamed Workforce and the rebuild began in earnest. That month turned out to be one of the busiest in the product's history.
This article was written from Mintage Workforce’s commit history for January 2026. See Mintage Workforce today