No logo cemetery. We list what we actually run in production — and briefly why. Decisions sit on an 18-month horizon, not the next GitHub trend.
Server-first, minimal JS footprint, real i18n — no 200 kB client bundles for a marketing page.
Validation and OpenAPI come from the same code. No after-the-fact documentation theatre.
PostgreSQL can do more than most teams realise. We rarely leave it.
Models that stay in production. We avoid frameworks that aren't reproducible.
100 % contract coverage before a single line hits mainnet. Audit reports as a gate, not decoration.
Reproducible, patchable, observable. No bespoke cloud-YAML rituals without a reason.
If it wasn't logged, it didn't happen. Metrics, alerts and health checks belong in the first PR.
Positioning includes what you leave out. These tools have their place — but not in every project, and rarely as first choice. We are honest when the answer is no.
Over-engineering without a payoff. 90 % of production stacks run happily on Docker Compose + systemd.
Schema evolution, joins, transactions — SQL is right most of the time. NoSQL goes on top, not instead.
Inflexible for custom logic, expensive lock-ins, plugin hell. OK for a plain corporate site — not for a product.
We pick tools on an 18-month horizon, not by GitHub trend. Proof before hype.
Not reproducible, not auditable, not rollback-able. Every deploy session produces technical debt.
Mocks lie about reality. Contract tests against real sandboxes — or nothing.
See how this stack looks in production — or tell us what you need.