Why we stopped putting everything behind one load balancer
Splitting public and internal traffic made incidents smaller and cheaper to debug.
We are a small engineering studio in Stockholm. Most of our work is taking an existing system, finding what slows it down and fixing it without a rewrite.
Start a conversationSee our workCustomer portals, internal tools and APIs, built to be maintained by your own team after handover.
A written review of hosting, backups, monitoring and costs, with a prioritised list of fixes.
Profiling slow pages and queries, caching strategy and load testing before your busy season.
Splitting public and internal traffic made incidents smaller and cheaper to debug.
Seven questions we ask before trusting any restore procedure.
Logical replication, one short pause and a rollback plan.