Centuro Global

The Angular upgrade was not framed as housekeeping. It was taken on because the build runner was running out of memory and stopping, and it included moving from the legacy browser builder to the application builder specifically for build performance. The version number went up as a consequence of fixing that, not as the goal.

A migration on a branch that lives for months is a migration that never lands. This one went through the same promotion path as everything else — feature, then qa, then uat, then pre-production, then production — with the fixes that surfaced after the version change shipped as ordinary work rather than held in a batch.

The Terraform is deliberately boring: a module each for VPC, subnets, internet gateway, route tables, ECS cluster, ECS service, task definitions, RDS cluster and instance, database parameter groups, S3 and EC2 — and then dev, qat, uat and prod as four directories that compose them. Environments differ in variables, not in structure, which is what stops "it works in uat" from being an infrastructure question.

Sentry for errors and performance tracing, PostHog for product events. Both went in deliberately, so a regression in a jurisdiction nobody on the team lives in shows up as a trace rather than a support ticket.

ISO 27001 comes round every year and it asks about the things engineering owns: access, change control, how production is provisioned, what is logged. Infrastructure as code and a promotion path with review gates are the answer to most of those questions, which is the practical argument for building them that way. We have supported that audit annually, and supported technical due diligence during fundraising.

A large Angular application on version 18, authenticating through Microsoft Entra with MSAL, translated with ngx-translate, taking payment through Stripe, and reporting through Chart.js and ExcelJS export. It is the surface through which customers run entity setup, immigration and compliance work across those 170-plus countries.

The platform started on hand-managed Docker Compose hosts behind nginx, with certificates renewed by script. We moved it onto an ECS estate defined entirely in Terraform, with RDS behind it, across four environments that share their shape. That migration is ours, and it is the reason provisioning is now a reviewed change rather than an act of recall.

Annual ISO 27001 audit support, and technical due diligence during a funding process. Both are engineering questions asked by non-engineers, and both are easier to answer when the infrastructure is already a text file.

Upgrading a framework because a newer one exists is how teams spend quarters and gain nothing. Upgrading because the build runner is dying gives you a finish line you can recognise. The builder migration was the actual fix; the version came along with it.

Four directories composing the same modules means a difference between uat and production is a value someone changed, visible in a diff. It costs more discipline up front and it removes an entire genre of incident.

This began as delivery through a partner agency and continued directly with Centuro. That is not a technical decision, but it is the one that produced everything above — infrastructure ownership, audit support and diligence work are things a team gets asked to do only after it has been around long enough to be trusted with them.