{"canonical_url":"https://engineer.company/tech-stack/","content_markdown":"# Tech stack\n\nA tool is a means. What a client buys is the judgement that picks the right one\nand the discipline to run it well — but you asked what we work with, so here it\nis, and every line of it is backed by work in [the portfolio](/portfolio/).\n\n## Languages and runtimes\n\n**Python** for data work, automation and services. **Go** where a single static\nbinary and low overhead matter. **TypeScript** and modern JavaScript on the web\ntier. **SQL** as a first-class language rather than something an ORM generates —\nmost of the performance work we are called in for lives there. **Bash** for the\nglue, written to be read.\n\n## Data\n\n**PostgreSQL** is the default, and we go a long way with it before reaching for\nanything else — partitioning, replication, extensions and the query planner. We\nalso run **MS SQL Server**, **BigQuery**, **SQLite** and **Redis**, and the\nspatial stack on top: **PostGIS**, **QGIS**, **GDAL** and **ArcGIS**. Pipelines\nare built to be re-runnable and idempotent, because the question after an\nincident is always \"can we replay it\".\n\n## Cloud and infrastructure\n\n**Google Cloud** and **AWS**, with **Azure** where the client already lives\nthere. **Linux** underneath everything — Debian and Ubuntu. **Docker** and\n**Kubernetes** for the workloads that earn them, and plain systemd units for the\nones that do not. **Ansible** and **Terraform** describe the machines, so an\nenvironment is a document rather than an archaeology project. **Caddy** and\n**nginx** at the front.\n\n## Running it in production\n\n**Prometheus** and **Grafana** for metrics, structured logging for the rest, and\nalerts that fire on symptoms a user would notice rather than on every twitch of\na graph. CI jobs that build, test, scan and deploy without a person in the loop.\nBackup automation and separate restore-test workflows.\n\n## The web tier\n\nStatic-first where it fits, because a static page can be served without a\nrequest-time application layer: **Hugo** builds this site. **Django** and **PHP** where there is an\napplication to serve. Semantic HTML, hand-written CSS, and accessibility treated\nas a requirement rather than an audit finding.\n\n## How we choose\n\nBoring technology, chosen deliberately, beats novel technology chosen by\ndefault. We pick for the problem, for what your team can operate after we leave,\nand for how the thing fails rather than how it demonstrates. When the right\nanswer is the stack you already have, we say so — and when it is not, we say\nthat too, with the reasoning written down.\n\nThis site is its own worked example: the [credits page](/credits/) names every\npiece of technology behind it, down to the typeface and the backup tool.\n\nIf you would rather have a supplier with opinions than one with a preference\nlist, [tell us what you are building](/contact/) *(and we will argue for them)*.\n\n\u003chttps://engineer.company/tech-stack/\u003e\n","date_modified":"2026-11-12T05:34:23Z","description":"The technologies Engineer ApS builds with: languages, data platforms, cloud and infrastructure, and how we decide what to use.","formats":{"gemtext":"https://advisory.engineer.company/tech-stack/index.gmi","gopher":"https://advisory.engineer.company/tech-stack/gophermap","html":"https://advisory.engineer.company/tech-stack/","json":"https://advisory.engineer.company/tech-stack/index.json","markdown":"https://advisory.engineer.company/tech-stack/index.md","pdf":"https://advisory.engineer.company/tech-stack/index.pdf"},"kind":"page","language":"en","title":"Tech stack","url":"https://advisory.engineer.company/tech-stack/","version":1}