Cases

What we have delivered, in the words you would use for it.

  • Archive, boxes, shelf
  • Records, filing cabinet, files

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.

The Engineer mascot: a friendly blue and white robot in a circuit-patterned cape, standing with a hand at its chin and looking up in thought

  1. The Engineer mascot: a friendly blue and white robot in a circuit-patterned cape, leaning out from behind the edge of a panel, one hand on the edge

    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.

    2025 Read what was actually done

  2. A mapping product, carried end to end

    Infrastructure, data processing and the map application itself, built and kept running for two years.

    2025 Read what was actually done

  3. 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.

    2026 Read what was actually done

  4. 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.

    2026 Read what was actually done

  5. 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.

    2026 Read what was actually done

  6. 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.

    2026 Read what was actually done

  7. 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.

    2026 Read what was actually done

  8. 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.

    2026 Read what was actually done

  9. 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.

    2026 Read what was actually done

  10. 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.

    2026 Read what was actually done

Your problem has a shape — and it is probably one of these.

Each case is a real engagement, written in the words the client used for it.

Tell us about yours

Recognise one of these as your own problem? Get in touch.