Cases
What we have delivered, in the words you would use for it.
Every case here is work the company delivered itself, said in the words a customer would use rather than the words an engineer would. Each one links to the full record behind it — the situation, the task, what was actually done and what came of it — because a claim you cannot check is only a claim.
Every case here was delivered by Engineer ApS itself. The wider record goes back to 2003 and includes work delivered by our founder inside client teams before the company existed — we say which is which rather than blurring it.
A tenth of the cloud bill, and nothing lost
Rethought the whole infrastructure and moved it off AWS, cutting the running costs to a tenth with no drop in what the team got done.
Work carried out: 2025 Read what was actually done
One infrastructure plan for 14 departments
Designed a shared framework for a research institute that 14 departments could run on together, each keeping the things that make it different.
Work carried out: 2025 Read what was actually done
A month of meter readings in 180 milliseconds
Built the pipeline that turns raw electricity readings into hourly figures: 30 days of data, gathered from mixed sources, answered in 180 milliseconds.
Work carried out: 2025 Read what was actually done
A maritime platform built in clean layers
Separated the app, the interface and the database so each can be changed without breaking the other two, and kept the business rules in one place.
Work carried out: 2025 Read what was actually done
A mapping product, carried end to end
Infrastructure, data processing and the map application itself, built and kept running for two years.
Work carried out: 2025 Read what was actually done
Quicker answers from a better choice of key
Moved the platform's identifiers to time-ordered keys, so the indexes stay tidy and lookups stay quick as the data grows.
Work carried out: 2025 Read what was actually done
A brand 200 times better known
Built the name up in shops, in print and on screens until 200 times more people recognised it.
Work carried out: 2025 Read what was actually done
Twice the engagement, from listening first
Studied what customers actually did rather than what they said, then acted on it: engagement and loyalty both doubled.
Work carried out: 2025 Read what was actually done
Three locks on the door, none of them locked
Audited the server's intrusion defences and found all three had never worked: one watched the wrong door, one was overruled by a broader rule, and one could not run at all.
Work carried out: 2026 Read what was actually done
Backups that have actually been restored
Set up encrypted off-site backups that test themselves every month, so the day you need them is never the day you find out whether they work.
Work carried out: 2026 Read what was actually done
A whole company on one small server
Ran the code hosting, seven websites, the privacy network and the backups for an entire company on a single 512 MB machine, by treating memory as the binding design constraint.
Work carried out: 2026 Read what was actually done
Servers you can rebuild from scratch
Wrote the whole server setup down as code, so a machine can be rebuilt exactly as it stands today and every change is reviewed before it reaches the live system.
Work carried out: 2026 Read what was actually done
An app that ate 41 MB a second, stopped
Traced an application filling the machine's memory until it froze, and fixed the cause: 111 GB of waste on a 36 GB laptop, brought down to nothing.
Work carried out: 2026 Read what was actually done
A site that meets the accessibility standard
Took every kind of page to WCAG 2.2 Level AA in both colour themes, with a written record behind each claim and an automated check that defends it.
Work carried out: 2026 Read what was actually done
The accessibility faults your checker misses
Found and fixed 11 real barriers an automated tool had passed as healthy, among them links invisible to the eye that a keyboard could still land on.
Work carried out: 2026 Read what was actually done
A safety net that no longer costs half an hour
Cut the automated checks guarding every release from 27 minutes to 10, by running them in the right order and several at a time.
Work carried out: 2026 Read what was actually done
Know the licence of everything you ship
Put a licence check on 644 third-party components that runs on every build, and proved it fires by breaking it on purpose.
Work carried out: 2026 Read what was actually done
Your code on your own hardware
Set up private code hosting on the company's own server, reachable only through one controlled entry point, with no public web panel to attack.
Work carried out: 2026 Read what was actually done
Recognise one of these as your own problem? Get in touch.