Where I moved the needle most.
Four out of many. These are the ones that made a measurable difference.
- 01Read the case
Travel and digital content
$500 → $120 a month, and the whole migration in eight working days.
From managed cloud to two self-hosted servers
A platform selling travel, tickets and digital books was paying $500 to $600 a month on low traffic. It moved to two self-hosted servers with the database replicated: if one goes down, traffic moves to the other.
- 02Read the case
Pharmaceutical
Migrated to AWS against a deadline, and modernized afterwards without the rush.
From a VPS to AWS in two steps: migrate first, modernize after
A Laravel application ran on a VPS with its database and Redis on the same machine. It was first migrated to AWS as it was, to meet the date; then it moved to containers, with the database, the cache and the files off the server.
- 03Read the case
Pharmaceutical · internal event
3,000 concurrent users on a platform that lived thirty days.
Infrastructure for an event that happens once
A pharmaceutical company's year-end event: each person uploaded a photo and the others voted. The peak was announced and would not happen twice. The infrastructure was written entirely as code in three days and taken down when it ended.
- 04Read the case
Software factory
Fifty inactive accounts removed, and a spending cap where there had been none.
An AWS account nobody was governing
The account had grown with no owner: old buckets holding hundreds of gigabytes, stopped instances still billing, and inactive users with more permissions than they needed. Access and spend were the same problem.
Facing something similar?
Get in Touch