IT & AI engineering for US businesses · 16 practices
Publishing · 2023

Hosting that scaled with a growing publisher — without a rebuild

We moved a growing content business onto a mix of dedicated and virtual servers sized for current load with headroom for growth, and hardened the environment around client data.

4×Traffic absorbed
0Security incidents
−28%Monthly hosting spend

The problem

Traffic was quadrupling year over year on hosting that had been sized for launch, with no monitoring and an unclear security posture.

What we did

  1. Right-sized mix of dedicated and virtual capacity
  2. Content delivery, caching and database tuning before scaling up
  3. Hardening pass and continuous vulnerability scanning

Built with

LinuxCloudflareMySQLTerraform

Client

Writeups · Publishing

Next step

Facing something similar?

Start with a two-week, fixed-fee discovery — then talk to the engineers who'd do the work.