geek vibes.geek vibes.
05 / 06 · ARCHITECTURE & DEV

Headless, modular, boring in the best way.

Our default stack: Next.js + Payload CMS + Postgres on Vercel — the same stack we use to run this site and our own product (GV Proposals). We adapt to your reality and migrate from legacy in phases. No big-bang rewrites.

01 · DEFAULT STACK

What we use to ship fast.

FRONTEND

Next.js 16

App Router, React Server Components, edge runtime. The framework we know inside out — including its sharp edges.

CMS

Payload CMS

TypeScript-native headless CMS. Editors get a UI they can use; engineers get a typed API. No vendor lock-in.

DATA

PostgreSQL

Boring is good. ACID, JSON columns when needed, mature operational tooling. Hosted wherever the client lives.

RUNTIME

Vercel / AWS / Coolify

Vercel for speed-to-market, AWS for enterprise, self-hosted (Coolify) for data sovereignty constraints.

02 · WHAT WE BUILD

Common projects.

  • Marketing sites with editor-friendly CMS
  • E-commerce on headless architecture (Shopify / Medusa / custom)
  • Customer portals & self-service apps
  • Internal tools & operations dashboards
  • API integrations (Odoo, SAP, Salesforce, HubSpot)
  • Legacy migration (PHP / WordPress / .NET → modern stack)
03 · PROOF: WE EAT OUR OWN COOKING

This site + GV Proposals run on the same stack.

Next.js 16 + Payload CMS + Postgres + Coolify (self-hosted). Bilingual i18n, draft/publish workflow, dynamic OG images, Lexical rich-text, RSC streaming. Production since early 2024 — no surprises.

Next.js 16Payload 3PostgreSQL 16TypeScriptTailwind v4Coolify
04 · HOW WE WORK

Engineering principles.

  • Trunk-based development with feature flags — no long-running branches.
  • CI/CD from day one. Preview deploys per PR.
  • TypeScript strict mode everywhere. Zod / Valibot at boundaries.
  • Automated tests on critical paths — pragmatic coverage, not vanity %.
  • Observability built-in (logs, traces, metrics) before the first user.
  • Documentation lives in the repo. README per package. ADRs for non-trivial decisions.
05 · PROCESS

4 phases, end-to-end.

01 · DISCOVERY

1-2 weeks

Codebase audit (if any), stack assessment, risk map, sprint-zero scope.

02 · ARCH

1 week

System diagram, data model, infra plan, CI/CD setup, security baseline.

03 · BUILD

6-12 weeks

Iterative sprints with biweekly demos. Production-ready every sprint.

04 · HANDOFF

2 weeks + retainer

Knowledge transfer, runbooks, on-call rotation, optional support retainer.

Need a stack second opinion?

30-min architecture review. We map risks and quick wins before any commitment.

Schedule review →
Architecture & Dev · Headless · Next.js + Payload · Geek Vibes · Geek Vibes