EN

Technologies

The tools we use and why

We choose technology not according to trend, but according to how many years the system will live and who will maintain it. A technology that cannot be transferred is a risk in a corporate project, no matter how new it is.

A.I.

  • OpenAI
  • Google Gemini
  • claude
  • Azure AI

front end

  • React
  • Next.js
  • vue
  • Tailwind

Backend

  • Node.js
  • Python
  • .NET
  • PHP

Mobile

  • Flutter
  • React Native
  • Swift
  • Kotlin

Cloud

  • AWS
  • Azure
  • Google Cloud

Database

  • PostgreSQL
  • mysql
  • MSSQL
  • MongoDB
  • Redis

DevOps

  • Docker
  • Kubernetes
  • GitHub Actions
  • CI/CD

Enterprise

  • Microsoft 365
  • Google Workspace
  • SAP
  • Logo
  • Mikro
  • Netsis

Selection criteria

How do we choose a technology?

If we cannot answer four questions positively, we do not use that technology in the corporate project.

Can someone else do the maintenance?

Code and infrastructure must be sustainable with commercially available capabilities. Dependency on us is not a feature, it is a flaw.

Will it still be supported in five years?

We do not use tools that do not have community and corporate support on core systems.

Can we move data outside?

Any system where data cannot be exported in a standard format is not permanent.

Can the total cost be predicted?

License, infrastructure and growth costs should be calculated from the beginning.

Let's talk about where to start on the technology side.

We listen to your existing systems and return with a scope and approach recommendation within two business days. The first meeting is free.