How Halcyon ships 2.6× more often, with 71% fewer rollbacks
A payments company with strict change control replaced its release spreadsheet with a review queue and an audit log its compliance team trusts.
- fewer releases rolled back
- 0%
- median time to first review, down from 3.4 hours
- 0 min
- more releases each week
- 0.0×
The challenge
Halcyon processes card payments for 9,400 merchants across Europe. Every release needed sign-off from two engineers and a compliance lead, tracked in a spreadsheet that took a day to reconcile before each audit.
Releases had drifted to once a week. Each one bundled around 60 changes, and when something broke it took hours to find which change was responsible.
Our auditors now ask for the Lumen export instead of a spreadsheet. That alone gave us back a week every quarter.
The approach
The platform team rolled Lumen out to one squad first. Review requests moved into a dedicated queue, and every approval was written to the audit log with the reviewer, the diff and the time.
After six weeks the rest of engineering followed. Compliance got read-only access to the audit log and stopped asking for the spreadsheet.
The results
Smaller, more frequent releases made rollbacks rarer and easier. When one is needed, the release page shows exactly which change to revert.
The last two audits closed without a single follow-up request about change management.
See it on your own releases
Free for 14 days, with the audit log included.