Tools we actually know.
The list below is deliberately short. We'd rather use a few components deeply and consistently than many superficially — and we document each choice as a deliberate decision.
We choose technology by architecture — not by trend.
Every decision is documented in Architecture Decision Records. We can explain it years later — and revise it when context changes.
We design APIs and events before we pick UI libraries. What's integratable stays replaceable.
TYPO3, Angular, NestJS, PostgreSQL — proven components with long support horizons. New tech goes in deliberately, where it solves problems.
Logs, metrics, traces belong in the blueprint. A system you can't measure isn't a system you can take responsibility for.
Shared identity, shared deployment model, shared standards. Variety belongs in the domains — not in the foundation.
We'd love to hear from you.
Send us three sentences about your initiative. We'll come back within two working days with concrete questions and an honest assessment — even if we're not the right fit.