Technologies
The stack is chosen for each project according to its context, your team and the long-term cost of maintenance.
A clear interface reduces friction and helps teams adopt new processes.
We choose React, Next.js or Angular on the web, and React Native or Flutter on mobile, according to the product, SEO, team and interaction needs.
| Technology | When we choose it |
|---|---|
| React | We choose React for rich interfaces when client-side interaction remains central. |
| Next.js | We choose Next.js when SEO, server rendering or fast pages matter. |
| Angular | We choose Angular for structured business applications that benefit from strong conventions. |
| TypeScript | We choose TypeScript whenever front-end code must stay safe and transferable. |
| React Native | We choose React Native when an app shares logic and skills with a React web front end. |
| Flutter | We choose Flutter when one code base must deliver a polished, consistent app on iOS and Android. |
A legible application foundation keeps business rules understandable and changeable.
We use .NET and ASP.NET Core for business systems, with REST APIs for integration and gRPC between internal services.
| Technology | When we choose it |
|---|---|
| .NET | We choose .NET for business domains that need a maintainable, durable foundation. |
| C# | We choose C# when the team needs one strongly typed language across business and infrastructure code. |
| ASP.NET Core | We choose ASP.NET Core for performant, testable web APIs and services. |
| EF Core | We choose EF Core for data access that stays readable and versioned through migrations. |
| REST APIs | We choose REST when varied clients need a simple HTTP contract to integrate. |
| gRPC | We choose gRPC for fast, strictly typed calls between internal services. |
Reliable data gives teams a shared basis for decisions.
PostgreSQL, SQL Server, MySQL and Redis are selected according to transactions, search, availability and internal skills.
| Technology | When we choose it |
|---|---|
| PostgreSQL | We choose PostgreSQL for strong transactions and rich queries without a proprietary licence. |
| SQL Server | We choose SQL Server when the Microsoft ecosystem and your internal skills weigh heavily. |
| MySQL | We choose MySQL for straightforward relational applications already invested in its ecosystem. |
| Redis | We choose Redis for cache or temporary state, not as the only source of truth. |
Predictable operations protect availability and delivery pace.
Docker, Azure and CI/CD bring repeatability, with automation proportionate to risk.
| Technology | When we choose it |
|---|---|
| Docker | We choose Docker when reproducible environments reduce differences between teams. |
| Azure | We choose Azure when its managed services and your operating constraints provide a concrete gain. |
| CI/CD | We choose CI/CD when repeated releases make manual controls too risky. |
| Observability | We choose observability when availability and diagnosis must be followed in production. |
The right structure keeps a system simple to change today and able to grow tomorrow.
A modular monolith is often a better first step than microservices; patterns are tools, not goals in themselves.
| Technology | When we choose it |
|---|---|
| Modular monolith | We choose a modular monolith when it keeps early product complexity under control. |
| Microservices | We choose microservices only when genuinely independent deployments or loads justify their cost. |
| Clean Architecture | We choose Clean Architecture when several interfaces must evolve around the same domain. |
| DDD | We choose DDD when shared vocabulary and business rules need a precise common model. |
Integration removes duplicate entry and connects systems that need to cooperate.
RabbitMQ, messaging, external systems and payment integrations are used when the flows justify them.
| Technology | When we choose it |
|---|---|
| RabbitMQ | We choose RabbitMQ when asynchronous, decoupled processing absorbs uneven workloads. |
| Messaging | We choose messaging when users need updates without blocking the main journey. |
| External systems | We choose an external integration when it removes duplicate entry and its contract is reliable. |
| Payments | We choose a payment provider according to served countries, fees and compliance requirements. |
AI can accelerate research or tasks when it remains controlled and measurable.
We consider LLM, RAG, automation and document processing with safeguards, evaluation and human review.
| Technology | When we choose it |
|---|---|
| LLM integration | We choose an LLM when a text task benefits from controlled, measurable assistance. |
| RAG | We choose RAG when answers must rely on your current documents. |
| Automation | We choose automation when a process is stable and its exceptions are identifiable. |
| Document processing | We choose document processing when repetitive entry can be checked by a person. |
The stack is chosen for each project according to its context, your team and the long-term cost of maintenance.