Stack

Last updated: Jun 17, 2026

In this section, you can find a detailed walkthrough of our entire tech stack.

For each component, you will find the following items:

Rationale: A brief explanation of what the component does and why we chose it.
Alternatives: Similar components we considered and the main reasons why we did not choose them.
Usage: How the component is used and pending implementations involving it.

You will also be able to see our philosophical standpoint towards our stack.

Methodology

Here is how we evaluate and select new components for our stack:

Research: We start by researching available stacks, technologies, and solutions that address the need at hand, using search engines and AI tools to build an initial list of candidates.
Evaluation: We build a spreadsheet to theoretically assess the pros and cons of each candidate. At this stage, we also apply criteria derived from our own ecosystem and engineering philosophy, which often helps certain tools stand out.
Proof of concept: We select the two or three candidates with the highest scores from the evaluation phase and build a small-scale proof of concept for each. The goal is not to prototype a full feature, but to integrate each candidate into our ecosystem and observe how it behaves under real-world conditions.
Defense: By this point, the engineer leading the evaluation has developed a well-grounded opinion. They are asked to make the case for their preferred choice, which opens the floor for other perspectives and helps surface any overlooked considerations.
Decision and documentation: Once the team reaches consensus, with supervision by the CTO and Executive Advisor, the chosen tool is implemented. An ADR is then written to document why we selected it and why the other evaluated options were not chosen.

Below we show you different purposes and in front of each one of them the corresponding component that we use to fulfill it: