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
Work carried out: 2025
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.
One infrastructure plan for 14 departments
Work carried out: 2025
Designed a shared framework for DTU that 14 departments could run on together, each keeping the things that make it different.
A maritime platform built in clean layers
Work carried out: 2025
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.
A mapping product, carried end to end
Work carried out: 2025
Infrastructure, data processing and the map application itself, built and kept running for two years.
A whole company on one small server
Work carried out: 2026
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.
An app that ate 41 MB a second, stopped
Work carried out: 2026
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.
A site that meets the accessibility standard
Work carried out: 2026
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.
The accessibility faults your checker misses
Work carried out: 2026
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.
A safety net that no longer costs half an hour
Work carried out: 2026
Cut the automated checks guarding every release from 27 minutes to 10, by running them in the right order and several at a time.
Your code on your own hardware
Work carried out: 2026
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.
Recognise one of these as your own problem? Get in touch.