Aixo Lab

How we think about technology choices.

You should not need to be a developer to understand why a product is built the way it is. These pages explain our usual defaults, the reasons for them and — just as important — when we would choose something else. They describe how we approach projects, not a list of technologies used on named clients.

Websites and web apps

What runs in the browser, and when each approach fits.

Read more

Mobile apps

Native, cross-platform and what we usually recommend.

Read more

Back end, data and hosting

The unseen parts that decide reliability, security and cost.

Read more

AI in software

Where it helps, how we limit the risks and what to ask.

Read more

The principles behind our defaults

  • Boring is good. Mature, widely used tools have more people who can maintain them, fewer surprises and better documentation. We reach for new technology only when it clearly earns its place.
  • Avoid lock-in where it matters. Your data should be exportable and your code understandable by other developers.
  • Choose for the team that will maintain it. Including you, and whoever follows us.
  • Match the tool to the scale. A simple, well-structured application beats a complicated one for most businesses.
  • Security and privacy by default, not as a later add-on.
  • Be honest about trade-offs. Every choice costs something; we try to say what.

Want a suggestion for your project?

Our technology stack selector asks a few questions and proposes an approach, with reasons, in plain language. It runs in your browser and sends nothing anywhere. For decisions that matter, a conversation is better than any tool.

Unsure what your project needs?

Tell us what you want to achieve. We will explain the options without the jargon.

Request a project quote