Engineer / Platform
Cases
Selected engineering work in plain language, with delivery context and links to the full record behind each case.
Engineer ApS was registered in 2025. These cases include company projects and work our founder carried out in client teams and as an employee, dating back to 2003. Each case explains the role and working arrangement.
Infrastructure simplified beyond AWS
Reviewed an international client’s infrastructure, removed unused services, adjusted capacity and moved workloads away from AWS.
Read the case studyA mapping product, carried end to end
Infrastructure, data processing and the map application itself, built and kept running for two years.
Read the case studyThree 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.
Read the case studyBackup automation with an explicit restore method
Implemented restic backup, retention, integrity checks and a monthly restore-test workflow, with documented activation prerequisites. The implementation record dated 2026-10-27 records no completed live restore.
Read the case studyPublic services on a small server
Hosted the company’s public web and git services on a 512 MB machine, treating memory as a design constraint.
Read the case studyInfrastructure defined in a repository
Defined Engineer ApS host roles, service configuration and checks in Ansible. Reusable configuration keeps infrastructure decisions visible in the repository.
Read the case studyHow the platform configuration is applied - Declared configuration
- Ansible roles
- Service definitions
A bounded event pipeline for a macOS app
Bounded event buffers, filtered subscriptions and budgeted logging in a macOS app. A recorded full test run reduced core log lines from 610,996 to 1,411.
Read the case studyHow events reach consumers and logs - Native events
- Typed, bounded subscriptions
- Log budget
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.
Read the case studyKnow 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.
Read the case studyYour code on your own server
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.
Read the case study
These cases introduce selected engineering work in plain language. Each links to the full record: the situation, the contribution and the result. Use the examples to judge relevance to your project, then ask about the scope and supporting evidence.