Technologies
The stack behind our software, and how often we really use it.
Every technology below has a usage tier: Daily, Regularly or When it fits. Where we have no published project in something, its page says so instead of inventing one.
Frontend
The interface your users actually touch. Angular, React, Vue, Next.js, and TypeScript, built for products that stay fast as they grow.
Backend
The engine behind the product. Node.js and NestJS on AWS for most of what we run, .NET where the system calls for it.
Mobile
iOS and Android apps wired to the same backend as your web product. Kotlin and Ionic behind the EHEIM app; Flutter and React Native when they fit.
Database
Where the data lives. MongoDB behind most of our platforms, PostgreSQL behind Sharewear and QRPixel, and schema design that holds up as you grow.
Questions about our stack
Straight answers on tiers, defaults and your existing code.
What do the usage tiers mean?
Daily means it is behind most of what we ship. Regularly means we use it on several projects. When it fits means we use it when a project calls for it, and the page says whether we have a published case study.
Do you have a default stack?
Angular on the front end, Node.js or NestJS on the back end, MongoDB or PostgreSQL for data, hosted on AWS. We change it when your team or product needs something else, and explain why in the proposal.
Can you work in the stack we already have?
Often, yes. We read the code first and tell you honestly whether we are the right team for it. If your stack isn’t one we use regularly, we will say so.
Do you use Go, Rust or Python?
Yes, for specific services inside larger systems: Go for busy APIs and workers, Rust for performance-critical components, Python for data, automation and AI services. Each page says how we use it and where it doesn’t fit.
Not sure which stack fits?
Tell us what you’re building.
A 30-minute call. We’ll recommend a stack and explain why, even if it isn’t one we use every day.