clo-web + clo-api reunified — one CLO service

MEANS FOR YOU

clo-web and clo-api, split apart in 2019, are back under one service — Card-Linked Offers has a single codebase again.

clo-web and clo-api were split into separate services in 2019 for reasons nobody currently on the team can fully reconstruct — the best guess is an org boundary that no longer exists. They've been reunified into a single clo service as part of the migration, on the theory that if two services always deploy together and always share the same data model, they should just be one service.

No external API contract changed. If you call CLO endpoints today, you're already calling the reunified service; the split was purely internal.

This is a smaller change than most on this list, but it's the kind of cleanup that only becomes possible once you're rewriting things anyway — nobody was going to schedule a project just to undo a 2019 org chart artifact.

COMMENTS · 4

Josef · 6d ago — Never understood why these were split in the first place. Good cleanup.

⚙ Tomas · 6d ago — Same — best theory anyone has is an old team boundary that hasn't existed in years.

Santiago · 5d ago — Does this change anything for CLO's accounting integration?

⚙ Tomas · 5d ago — No, that integration point didn't move.