What technologies we use – and why we don’t commit to a fixed stack.
No Rigid Framework. A Toolbox.
Every company is different. Every operational system has different requirements. That’s why we don’t work with a fixed tech stack that we impose on every project. We choose the technologies that fit the project – not the other way around.
What remains the same for us: We develop Full-Stack.
From the data model to the backend logic to the user interface, everything comes from one source. And we rely on modern, widespread technologies – no exotic in-house developments that only we understand.
Technologies We Often Work With
Our toolbox includes, among others:
| Database | PostgreSQL, MariaDB, MongoDB, and others depending on requirements |
| Backend | TypeScript, Python, Node.js |
| Frontend | Modern web frameworks, responsive and cross-platform |
| AI & ML | Python-based ML pipelines, LLM integrations, custom agent frameworks |
| Infrastructure | Cloud hosting with German/EU providers, CI/CD pipelines |
| Integrations | REST APIs, webhooks, database connections, file interfaces |
This is a snapshot – not a definitive catalog. The technologies used in your project will arise from the architecture we develop together during the system audit.
Our Principles in Technology Selection
More important than the individual technology are the principles by which we select them:
Open and Widespread
We focus on technologies that are widely utilized, well-documented, and supported by large communities. This means: Your company remains independent. You could run the system yourself or continue its development with another partner at any time.
Open Source Where Possible
Where good open-source solutions exist, we utilize them. No unnecessary licensing costs, no vendor lock-in, transparent code. We continuously evaluate new frameworks and libraries – and implement what proves effective in practice.
Future-Proof
Technologies become outdated. Therefore, we ensure that the stack of a project not only works today but will also be viable in three to five years. Active development, stable APIs, broad adoption – these are our criteria.
Pragmatic
The best technology is the one that solves the problem. Not the newest, not the trendiest, not the one with the most attractive logo. We make technology decisions based on one criterion: What brings the best outcome for this project?