Skip to main content

Security

Rebuilding an inherited platform on a clean foundation

In progress

When a client inherited a platform they could not trust, we started building them a clean one they own outright, with a control board that tracks every step of the move.

After the security audit, the marketplace needed a platform it fully owns. We are rebuilding it on a clean foundation: new cloud accounts, infrastructure written as code, six repositories with automated checks, and a control board that tracks every step of the move.

Client
A remote-staffing marketplace
Engagement
Architecture, rebuild, and transition planning
Status
In progress
Discipline
Platform rebuild
What we built
  • Clean cloud accounts
  • Infrastructure as code
  • Rebuilt codebase
  • Automated checks
  • Control board
Stack
  • AWS
  • OpenTofu
  • Postgres 16
  • Angular 21
  • Cloudflare Workers
  • GitHub Actions
  • Playwright

Before

The audit showed the marketplace's inherited platform could not simply be patched: the risk ran through every codebase and through how they were deployed. The responsible path was a clean rebuild in an environment the client owns outright, built and tested in full before anyone depends on it, followed by one controlled move. We are building it, with a control board that tracks every step.

What made it hard

01

The running marketplace could not be disrupted while the new platform was built.

02

Every critical audit finding had to be closed in the rebuild, with a test to prove it.

03

The new environment had to be owned and controlled by the client from the very first account.

04

A move with hundreds of steps needed one place that shows what is done, what is in progress, and what is blocked.

What we built

01

Set up new cloud accounts with guardrails from day one: public storage blocked, budgets, multi-factor sign-in on the root account, and no long-lived access keys.

02

Wrote the infrastructure as code: load-balanced servers across two zones, managed Postgres 16, encrypted storage, and a secrets store behind an access gate, with twelve health checks per server after each release.

03

Rebuilt the code in six repositories with automated checks on every change (secret scanning, static analysis, 1,699 API tests, and 64 browser tests), and moved the admin panel from Angular 6 to Angular 21.

04

Fixed 103 of the 115 mapped audit findings, including every critical one, then re-audited the new code and fixed every blocker and major issue it found.

05

Reviewed 6,101 live chat conversations for real user problems and folded 124 fixes into the new build.

06

Built a control board that tracks all 259 steps of the move, with an owner and status for each, a timestamped action log, and a flag on any step that needs a person to confirm with multi-factor sign-in.

Results

322Pull requests in 18 days

Merged across six repositories from September 14 to October 2, 2026, each through automated checks.

1,699API tests passing

Plus 64 browser tests, run on every change to the rebuilt platform.

259Steps on the control board

Every step of the move, each with an owner, a status, and a timestamped log.

Where it stands

In progress, tracked step by step on the control board.