Skip to content
Engineer
Menu
Design
English

Engineer / Categories

Infrastructure

  1. One infrastructure plan for 14 departments

    Designed a comprehensive infrastructure framework for a research institute impacting 14 departments, featuring flexible modules, unified data pipelines, and structured support strategies for long‑term adoption.

    Designed a comprehensive infrastructure framework for a research institute across 14 departments — modular, with unified data pipelines and support strategies.

  2. Built the company's first observability dashboard

    Developed and launched the company's first observability dashboard, providing real‑time system performance insights and data visualization on the large office TV.

    Built the company's first observability dashboard for real-time system insight, helping teams detect and resolve incidents 40% faster.

  3. Ran 10 PostgreSQL and MS SQL servers on Ubuntu

    Designed, deployed, and maintained 10 PostgreSQL and MS SQL servers on Ubuntu Linux VPS, ensuring optimal server performance and reliability.

    Designed and maintained 10 PostgreSQL and MS SQL servers on Ubuntu Linux VPS at 99.9% uptime, with 30% faster queries via tuning.

  4. Wrote 1,000 RBAC rules to secure Linux servers

    Enhanced data security by implementing 1,000 RBAC rules for developers, application instances, PostgreSQL, MS SQL, and other Linux servers, preventing unauthorized access; documented with Ansible automation.

    Implemented a recorded 1,000 RBAC rules across developer, application, database and Linux access, with documented Ansible configuration.

  5. Automated 100 critical data backups using Barman

    Automated 100 critical data backups using Barman, Google Cloud, Bash, and Python, ensuring data integrity across databases.

    Automated 100 critical database backups with Barman, Google Cloud, Bash and Python — turning data recoverability into a tested fact.

  6. Ran 20 Docker apps on Google Cloud and AWS

    Deployed and maintained 20 Docker containerized applications, troubleshooting with Podman and Kubernetes, and managing R‑based apps on Google Cloud and AWS.

    Deployed and maintained 20 Docker containerized apps across Google Cloud and AWS, troubleshooting with Podman and Kubernetes for stable releases.

  7. Managed 30 Ubuntu Linux VPS instances

    Managed 30 Ubuntu Linux VPS instances, implementing disaster recovery strategies and ensuring optimal network configurations.

    Managed 30 Ubuntu Linux VPS instances with tested disaster-recovery strategies and solid networking — a resilient foundation to grow on.

  8. Led access management across M365 and SSO

    Prevented security breaches by leading access management initiatives, utilizing M365, 1Password, Red Hat SSO, and OKTA SSO.

    Led access management with M365, 1Password, Red Hat SSO and OKTA, sharply cutting unauthorised-access risk and making access auditable.

  9. Cut operational risk with Grafana and Prometheus

    Mitigated operational risks by implementing a monitoring dashboard using Grafana and Prometheus, improving system reliability.

    Built a Grafana + Prometheus monitoring dashboard that catches problems before they escalate, shifting the team from firefighting to prevention.

  10. Managed 8 WireGuard and IPsec VPN connections

    Managed and troubleshot 8 WireGuard VPN and IPsec VPN connections, ensuring secure communication across Google Cloud and Linux systems.

    Managed and troubleshot 8 WireGuard and IPsec VPN connections across Google Cloud and Linux, ending recurring connectivity outages.

  11. Overhauled internal processes, saving 8,000 hours

    Overhauled internal processes, saving 8,000 hours by improving software architecture, systems, and scheduling efficiency.

    Overhauled internal processes to save ~8,000 hours, improving software architecture, systems and scheduling efficiency.

  12. Administered network infrastructure

    Administered network infrastructure for over 1,000 servers, ensuring optimal system deployment, security, and troubleshooting.

    Administered network infrastructure for 1,000+ servers, ensuring reliable deployment, solid security and prompt troubleshooting.

  13. Automated SSL/TLS certs for 100 Docker apps

    Automated SSL/TLS certificate creation for 100 Docker applications, ensuring secure connections across Ubuntu Linux hosts.

    Automated SSL/TLS certificates for 100 Docker apps on Ubuntu Linux, ending manual renewals and the outages expired certs cause.

  14. Configured and deployed 1,000 Wi‑Fi routers

    Configured and deployed 1,000 Wi‑Fi routers, improving network accessibility and performance for clients.

    Configured and deployed 1,000 Wi-Fi routers with a standard setup, giving clients dependable wireless access and performance.

  15. Administered 100 Bare Bone servers

    Administered 100 Bare Bone servers, physical networks, and IP telephony systems, ensuring robust infrastructure for company growth.

    Administered 100 bare-bone servers, physical networks and IP telephony, providing the robust foundation the company grew on.

  16. Administered 40 websites on Apache and Nginx

    Administered 40 websites on Ubuntu Linux hosting servers with Apache and Nginx, ensuring high availability and performance.

    Administered 40 websites on Ubuntu Linux with Apache and Nginx at high availability and performance — hosting clients never had to think about.

  17. A mapping product, carried end to end

    Architected, developed and supported infrastructure, data processing and a map application over 2 years, covering both software delivery and operational maintenance.

    Architected, built and supported infrastructure, data processing and a map application over two years, covering delivery and operational maintenance.

  18. Infrastructure simplified beyond AWS

    Reworked an international client’s infrastructure by removing unused services, adjusting capacity and moving workloads away from AWS. The founder reports a 10x reduction in cloud costs with no loss of productivity.

    Reviewed an international client’s infrastructure, removed unused services, adjusted capacity and moved workloads away from AWS.

  19. Provisioned Azure infrastructure as code

    Provisioned Azure infrastructure as code with Bicep — Container Apps, PostgreSQL Flexible Server, Front Door/WAF and networking — across the development, staging and production environments.

    Provisioned Azure infrastructure as code with Bicep — Container Apps, PostgreSQL, Front Door/WAF — reproducible across dev, staging and prod.

  20. Owned end‑to‑end platform deployments to Azure

    Owned end‑to‑end deployments of the platform to Azure, managing releases across development, staging and production environments.

    Owned end-to-end Azure deployments, moving releases through dev, staging and production along a defined, repeatable path.

  21. Implemented backups and disaster recovery as code

    Configured database backup retention as infrastructure‑as‑code, then audited the recovery position and documented the restore procedure — naming the remaining gaps rather than leaving them to be found during an incident.

    Configured database backup retention as infrastructure-as-code, audited the recovery position and documented the restore procedure and remaining gaps.

  22. Ran 24/7 support for ~1,000 IPTV/OTT servers

    Provided round‑the‑clock 24/7 infrastructure support for an IPTV/OTT streaming platform, administering ~1,000 servers plus client‑owned systems for global customers in China, the US and Germany.

    Provided 24/7 infrastructure support for an IPTV/OTT streaming platform — ~1,000 servers plus client systems across China, the US and Germany.

  23. Kept IPTV streaming signals running non‑stop

    Ensured uninterrupted delivery of IPTV streaming signals between suppliers and clients, monitoring and maintaining the streaming network and IP telephony around the clock.

    Ensured uninterrupted IPTV streaming between suppliers and clients, monitoring and maintaining the streaming network and IP telephony 24/7.

  24. Built infrastructure that still runs years later

    Planned and implemented new infrastructure functionality for internal and external systems, building solutions durable enough to still run years later with minimal change.

    Planned and built infrastructure for internal and external systems durable enough to still run years later with minimal change.

  25. Built the entire core infrastructure from scratch

    As one of the first hires, designed and built the entire core infrastructure and supporting processes from scratch for a green‑energy SaaS startup, laying the foundation for rapid growth.

    As one of the first hires, designed and built a green-energy SaaS startup's entire core infrastructure from scratch, enabling rapid growth.

  26. Integrated a company‑wide password manager

    Integrated a company‑wide password‑management system, strengthening security and streamlining access control.

    Integrated a company-wide password-management system, strengthening security and streamlining access control across the organisation.

  27. Built first‑party error monitoring and tracing

    Built first‑party error monitoring and OpenTelemetry tracing rather than buying them — payload sanitising, spike and regression detection, symbolication and a synthetic heartbeat — behind 11 operator views.

    Built first-party error monitoring and OpenTelemetry tracing — sanitising, spike detection, symbolication and a heartbeat — behind 11 operator views.

  28. Infrastructure defined in a repository

    Built the company's own infrastructure as 19 Ansible playbooks and 34 roles across 12,065 lines of YAML, converging a live host to a declared state with every play idempotent.

    The repository supplies the configuration for rebuilding the declared environment, and the parts of it that were only ever true because somebody remembered…

  29. Public services on a small server

    Hosted the company’s public services on a single‑core 512 MB host — a git forge, a web server for seven domains, Tor, two alternative‑protocol servers and intrusion banning — treating 464 MB of usable memory as the design constraint; backup automation is a separate implementation.

    The recorded public-service setup ran on a machine that cost less per month than a lunch, and the design is better for the discipline rather than merely…

  30. Three locks on the door, none of them locked

    Found and closed three SSH brute‑force protections that had never worked: a ban jail watching port 22 while the daemon listened on 1986, a rate limit shadowed by a broader rule above it, and a ban action whose binary never resolved, so no ban had ever applied.

    Three protections that had never once fired now do, and the class of defect they belong to — a control whose failure mode is that it keeps reporting healthy —…

  31. Hardened SSH to 24 validated directives

    Hardened SSH to 24 asserted directives with three‑stage validation — the candidate file, the assembled config, then the daemon's own read‑back — after the read‑back caught the running server silently overriding two of the twenty‑four.

    The SSH posture is now the daemon's answer rather than the repository's claim, and the difference is not theoretical — it was already two settings wide when…

  32. Proved the intrusion ban works every run

    Proved the intrusion‑banning path end to end on every hardening run by banning a reserved test address, reading the resulting kernel rule and unbanning in a guaranteed cleanup block, so a jail that stops working fails a run instead of reporting healthy.

    A banning path that stops working now fails a converge instead of continuing to report healthy, which is the only property that mattered.

  33. Verified firewall rules by position

    Verified firewall rules by position rather than presence, reading the numbered rule list and the live packet‑filter chain, because a rule that exists is not a rule any packet reaches.

    The firewall posture is now checked the way a packet experiences it. The most useful outcome was not the check but what it revealed about the reporting that…

  34. Backup automation with an explicit restore method

    Implemented restic backup automation with retention, integrity checks and a monthly restore‑test workflow; documented storage activation and live‑restore verification as separate operational steps.

    The repository contains the backup and restore-test implementation and documents its activation prerequisites.

  35. Built dead‑man's‑switch host monitoring

    Built dead‑man's‑switch monitoring that pings only while memory and disk are healthy, so a degraded host raises an alert by going silent — and caught six variable names saying "free" where the check correctly measured "available", an order of magnitude apart on a 464 MB box.

    The host gained an alarm that fires when the expected signal is absent, and the misleading names were corrected.

  36. Made Ansible check mode tell the truth

    Made check mode tell the truth across the whole platform after finding six probes deciding on a value the host never gave, because Ansible's command module reports success under --check while skipping the command entirely.

    A dry run now either measures something or says it did not, and neither of those is the third option it used to have.

  37. Added a one‑second preflight for secrets

    Added a preflight play that runs the same code as the converge against operator‑local secrets in about a second, after a half‑applied production run died on its ninth task with the swap settings already written to the live host.

    A secret that does not resolve now costs a two-second refusal on a laptop instead of a partly-applied change to a live server.

  38. Reconciled a 20‑record DNS zone as code

    Reconciled a 20‑record DNS zone declaratively against the Cloudflare API with separate audit and BIND‑export entry points, and turned the CDN proxy back off on privacy grounds after building it.

    The zone is versioned, comparable and exportable, and the one decision that went against the obvious default is written down with its reasoning so that nobody…

  39. Cut systemd sandbox exposure on every unit

    Cut systemd sandbox exposure across every unit this platform installs — a dead‑man's‑switch service from 9.6 UNSAFE to 1.5, an internet‑facing git forge from 8.3 EXPOSED to 1.5 — and added a converge‑time parser check after finding a misspelled directive silently ignored in three unit templates.

    Every unit runs with the privileges it needs and not the ones it does not, the numbers are measured rather than asserted, and the class of defect where a typo…

  40. Built 7 read‑only host reporting roles

    Built seven read‑only reporting roles that render a live host to Markdown — facts, access, git, metrics, traffic, security and provider inventory — under a rule that no number is printed the run did not measure.

    The estate can be described from the repository on demand, and the reports have found real things: the two dead security controls, an undeclared listening…

  41. Your code on your own server

    Deployed the company's own git forge on Soft Serve, private by default with no web panel and its SSH port bound to loopback behind a jump host, and made the landing page in front of it a build artefact of the main site rather than a hand‑kept copy.

    The company hosts its own code on its own hardware, and the page in front of it inherits every check the main site passes rather than drifting away from it in…

  42. Ran containers on Podman and Quadlet

    Deployed a container plane on Podman and Quadlet under systemd rather than Docker, because Docker's default bridge‑port publishing can bypass UFW rules — and gave deploys an unprivileged user with one fixed command instead of root.

    Containers run under the supervisor that was already trusted, behind the firewall that was already declared, and a routine release uses one scoped command…

  43. Provisioned a second server from code

    Automated the provisioning of a second server on a second cloud provider, creating the firewall before the machine so it is born behind one, with both providers' firewalls written directly against their REST APIs to avoid a third‑party collection.

    A second host can be created, or re-adopted, from the repository, behind a firewall that already exists, at a cost the file states.

  44. Wrote a scope rule after a credential leak

    Wrote a scope rule into the repository after a restructure carried another company's inventory, firewall allowances and prose into it — and kept the quarantined residue under the secret scanner rather than excluding it.

    The scope boundary is a written rule with a stated test, the residue is visible rather than buried, and the specific shape of credential that got through now…

  45. Split every operational secret per host

    Split the four per‑host operational secrets after establishing that two hosts sharing one dead‑man's switch alert less than two switches, not more, and that a shared backup passphrase can expose both hosts' backups, even in separate repositories, if someone obtains it and can read both repositories' encrypted data and key files.

    Secrets are per host by construction, and the two failure modes that would have followed from sharing them are written down where the next person edits the…

  46. Mirrored the site to Gemini and Gopher

    Built Gemini and Gopher outputs from the same website source; the achievement records 777 documents in each format at that stage, with zero HTML bytes changed by adding the formats.

    Recorded 777 Gemini and 777 Gopher documents in a historical build; zero HTML change concerns adding those output formats.

  47. Rehearsed the forge CI hook, found 2 defects

    Rehearsed the forge‑side CI hook and found two defects unreachable by reading the file: a fallback that put an unresolvable argument on the hook's input, and git's own environment variable following the gate into the checkout and turning 19 tests red.

    The hook works on both paths and both defects were found before any real push met them. The limit is that a rehearsal is still a simulation: it proves the…

  48. Measured 13 addresses with no tracking

    Measured thirteen addresses from the web server's own access log alone — no cookie, no tracker and no third‑party service — masking the client network as each line is written, and folding the result into a permanent archive of 21 daily counts and 20 monthly facets.

    Thirteen addresses are measured this way, and the site ships no cookie, no tracker and no third-party request, so there is nothing to consent to and nothing…

  49. Published a readable Tor onion mirror

    Published the site as a Tor onion mirror on a readable address beginning engineer, with the key generated off the host so it never reached this repository or a laptop, and left it the one front door of four that is never counted.

    The site has four front doors onto one build, and this is the only one that is never counted. Gemini requests and Gopher connections are tallied per day with…

Contact

Still working out what you need?

Tell us what is going wrong, or what you are trying to build. We will tell you what it would take, roughly what it would cost, and whether we are the right people for it.

From 1,400 DKK an hour, excluding VAT — and less per hour on a longer booking.

welcome@engineer.company +45 50 10 61 84 Copenhagen, Denmark