Evo Weekly — 15 May 2026
Snippet

Branding Goes Global — and Saves £36K a Year

15 May 2026 Lucian Rimoti improvement live in prod

Clip

Summary

Branded login screens used to be a UK-only privilege. As of this week, customers in EU, US, and APAC get their logo, colours, and login experience too. The team rebuilt the whole branding stack on a shared global backend with APM routing — replacing four separate regional servers with one. Every upload now gets malware-scanned with critical alerts firing within five minutes. The kicker: infrastructure costs drop from around £48K a year to £12K.

Screenshots

Transcript

LR
Lucian Rimoti
34:59 – 37:30

shortly grab the screen share and show you exactly what the change looks like in

Bianca Manase 34:59

Oops. Yeah.

Lucian Rimoti 35:01

production. Okay, so starting with branding. So until last week, if you were a customer in the US, you or APAC and you wanted branded login screens, your logo, colors, experience, so on and so forth.

The answer was simply, it's not possible. Branding only worked in UK production, and that is now fully resolved. And the problem that it solved is that the legacy branding services required initially a separate dedicated server per region.

Scaling to new regions meant provisioning and maintaining an entirely new stack each time. And on top of that, the old solution was over-engineered and complex. Maintenance was slow, costly, and every change carried more risk than it should have.

Why did we do this? Well, and how did we do it? We built a completely new content service or branding with a new pack, new backend, new front end, new infrastructure model.

The key design decision was one shared global backend with APM routing across all four production geographies like UK, EU, US, and APAC that we cover. We've migrated all the existing customer blending data with zero downtime, and we added something the old solution never had, which is every uploaded file is now scanned for malware via Azure Defender with automated critical alerts firing within 5 minutes of detection. If we'd scaled the old solution to cover all the environments and regions we now support, we'd be paying close to 48, 000 pounds a year with a new solution covering everything, all geographies.

This comes down at around 12,000, which is a huge saving that we have. So that's roughly 36, 000 pounds saved annually just on infrastructure. So EU, US and APAC customers now have full branding support.

And the new code base is built on clean architecture principles, meaning the cost of every future change is lower than before. So just to close this off, live across all four regions, customer will see a design uplift that I will show later, build with our new component library, consistent with the rest of the platform. So essentially, one rebuild remove the regional capability gap and the cost problem simultaneously.

If you can switch to my settings screen. Thank you, Bianca. Okay, what did we do with my settings?

Well, my settings has been fully rebuilt as a modern micro front end, the same back end, same APIs, completely rewritten front end, built with the same new component library