# We build with technology that lasts

> We choose stack based on performance, maintainability and operational control. Not based on weekly hype. When it makes sense, we keep [data and infrastructure in the EU](/en/hrde-vytvoreno-v-eu).

[Canonical HTML](https://dreamind.cz/en/technologie)

## We pick stack by objective

### Performance and SEO by default

For web projects we rely on Next.js SSR/SSG, Core Web Vitals and fast first render from day one.

### Clean engineering without tech debt

TypeScript, clear architecture and explicit boundaries so the product remains easy to evolve.

### Security and operations ready

Roles, auditability, stable release flow and monitoring are part of design, not afterthoughts.

### Control over data

EU-first infrastructure and fewer third parties. We measure what you need without invasive tracking.

## Technology by project stage

### START — Fast website or landing page

- Next.js + TypeScript for fast delivery
- Performance and technical SEO from the start
- Simple content editing via CMS
- Low operational complexity

Final stack is tuned to your goal.

### GROW — Growth, conversion, integrations

- Scalable frontend and BFF in Next.js runtime
- Integrations with CRM, ERP, emailing or internal APIs
- Conversion and key-event measurement
- Ongoing performance optimization

Final stack is tuned to your goal.

### SCALE — SaaS or platform

- Node.js or ASP.NET based on domain needs
- Roles, workflow, auditability and security
- Cross-system integrations and robust data model
- Architecture ready for heavy load

Final stack is tuned to your goal.

## What we use in production

### Frontend

We build fast, maintainable UI with Next.js and React, backed by TypeScript for safer iteration.

- Next.js
- React
- TypeScript

### Backend & API

We use Node.js (including Next.js runtime/BFF) and ASP.NET. Choice depends on domain and integration needs.

- Node.js
- Next.js Runtime/BFF
- ASP.NET
- REST / Webhooks

### Data

For transactional data we typically use PostgreSQL. Prisma keeps data work consistent in Node parts.

- PostgreSQL
- Prisma

### CMS

We use Payload when teams need safe and fast content updates without developer dependency.

- Payload

### Analytics

We combine self-hosted Plausible with custom event tracking: privacy-first but actionable.

- Plausible
- Custom Analytics

### Hosting & Infra

Infrastructure is matched to scope: often Hetzner + Coolify with a Docker-first approach, and Kubernetes when justified.

- Hetzner
- Coolify
- Docker
- Kubernetes
- Git

## Stability and long-term evolution

### CI/CD workflow

Releases are Git-driven. Every change goes through clear review and controlled deployment.

### Docker-first deployment

We containerize applications to keep environments predictable and repeatable.

### Kubernetes where it makes sense

For larger systems we orchestrate and scale with K8s. For smaller projects we avoid unnecessary complexity.

### Observability

Logs, metrics and errors are monitored so issues can be found and resolved quickly.

### Security baseline

Secret management, roles, regular updates and dependency minimization are standard, not add-ons.

When it makes sense, we keep data and infrastructure in the EU under your control.

- EU jurisdiction
- Privacy-first analytics
- Transparent operations

## How we decide on technology

### Can you work with our current stack?

Yes. We start with a technical audit and recommend what to keep, improve or replace.

### Who owns the code and infrastructure access?

You do. We hand over repositories, access and documentation so operation stays under your control.

### Can analytics work without invasive tracking?

Yes. We use privacy-first analytics with actionable event tracking.

### Do you run on Hetzner, Coolify and Kubernetes?

Yes. We design infrastructure by project size and SLA from lean setups to full orchestration.

## We design stack by outcome, not trend.

- Fastest realistic delivery path
- Scope and budget estimate
- Sustainable architecture without tech debt

[Book a consultation](/en/kontakt)