Tech stack

The stack is chosen for the product task, not for a fashionable list

Technology should help launch quickly, maintain easily and scale safely. For each project we choose only the parts that clearly reduce risk or speed up delivery.

Fast frontend
Real-time data
AI integrations
EU infrastructure

Stack groups

Technology categories

We do not use everything in every project. The combination depends on performance, data shape, integrations and maintenance needs.

Tech stack Goal: speed and clear interface

Frontend and web platforms

Astro, Vue 3, Nuxt, Convex and Node.js / Fastify power fast websites, portals, PWA interfaces and real-time web systems.

  • Astro
  • Vue 3
  • Nuxt
  • Convex
  • Node.js / Fastify
  • PWA
  • iOS
Tech stack Goal: correct data without manual refresh

Data, RAG and real time

Convex, PostgreSQL / pgvector, SQLite and Redis are chosen depending on live sync, vector search, transactions or local reliability.

  • Convex
  • PostgreSQL / pgvector
  • SQLite
  • Redis
  • Embeddings / RAG
Tech stack Goal: controlled automated work

AI models and automation

The latest Claude, GPT, Gemini and Llama model families, RAG, agent logic and n8n / Make workflows are connected to real business systems.

  • Claude Opus / Sonnet
  • GPT-5 / GPT-4.1
  • Gemini 2.5 / 3
  • Llama 4
  • Whisper / ElevenLabs
  • n8n / Make
  • Webhooks
Tech stack Goal: stable launch and safe operation

Infrastructure

Hetzner Cloud, Cloudflare Tunnels, Docker and EU servers let us launch reliably, monitor errors and manage access.

  • Hetzner Cloud
  • Cloudflare Tunnels
  • Docker
  • EU hosting
  • Monitoring

Quality criteria

Why a technology enters a project

Tech stack

Speed

The site must load quickly and the interface must respond immediately. Static pages are generated ahead of time, while interactivity is loaded only where needed.

Tech stack

Real-time need

If several users must see the same changes, we choose a real-time data layer instead of manual refreshes.

Tech stack

Maintainability

We prefer simple architecture, types, clear data models and technologies that can still be maintained next year.

Tech stack

Deployment

We choose platforms that can be monitored, restored and moved. For critical data, it matters where it is stored.

Decision guide

How we choose a stack in practice

01

Data first

We identify where data lives, who changes it and how quickly users need to see updates.

02

Then interface

We separate informational pages from interactive modules so the site does not ship unnecessary JavaScript.

03

Then integrations

We check APIs, authentication, limits and failure scenarios before promising automation.

04

Finally operations

We set up monitoring, backups, domains, access and documentation.

FAQ

Tech stack FAQ

Do you always use the same stack?

No. A marketing site, customer portal and AI document search need different choices. The shared principle is simplicity, speed and maintainability.

Can you work with our existing stack?

Usually yes. We first check whether the existing base blocks the goal, then suggest extension or rewrite only when justified.

Where is data stored?

Depending on need, we use EU infrastructure, Cloudflare services or the client environment. For sensitive data we discuss access and backups.

Is the stack good for SEO?

Yes. Astro and server-rendered content provide fast, indexable pages, while interactive modules are loaded separately.

Not sure which stack fits?

Describe the product and constraints. We will suggest the simplest technical direction without over-engineering.

Discuss technology