Stack
What we run ourselves, and what we pick for clients.
One page covering everything under the hood. No marketing slides, no 'we work with the best partners'. Concrete tools, the reasoning, and what we deliberately do not pick. Aimed at SMB decision-makers who want to verify our choices, and at other consultants who want to read our work.
Our stack
Per layer the tools we know, run, and recommend. Not fifty options, one sharp choice with one or two alternatives where that helps.
Front-end
- Next.js 16 (App Router)
- React 19
- TypeScript
- Tailwind CSS 4
Back-end
- Next.js Route Handlers and Server Actions
- Drizzle ORM
- NextAuth, Better-Auth where it fits
Database
- Postgres (Neon, EU region)
- Self-hosted Postgres where the client wants it
Hosting
- Vercel, EU regions by default
- Cloudflare for DNS, CDN and auxiliary layer
- Hetzner or AWS when self-hosting is required
Observability
- Sentry (EU tenant) for errors
- Vercel Analytics for traffic
- OpenTelemetry where it pays off
AI
- Anthropic (Claude) as primary model
- OpenAI-compatible APIs as fallback
- OpenRouter as gateway for model comparison and routing
Remote support
- RustDesk, self-hosted in EU
- Open-source, no US-cloud dependency
Office IT
- Microsoft 365 as default for SMB
- Google Workspace as alternative
- Migration between the two is no issue
Office automation
- n8n, self-hosted
- Make for light integrations
- Zapier where the client already runs it
- Power Automate inside Microsoft 365 environments
Why these choices
Four principles, and we don't bend on these for fashion.
- Modern, not trendy
- We pick tools we have known for years and that have a steady community and maintainer. No new library every month, no experiment on your budget.
- EU data sovereignty where possible
- Customer data in EU regions: Neon EU, Vercel EU, Sentry EU, Microsoft 365 EU. RustDesk self-hosted. Where a US tool is the only good option, we say so.
- Open-source as default
- Lock-in as low as possible. Postgres, Next.js, Drizzle, n8n, RustDesk: all open-source. If you decide to move on, your code and data are portable.
- Small set of tools, expert level
- We know our stack inside and out. Ten tools we are expert in, not fifty we know superficially. That saves you money on every next project.
What we deliberately don't pick
For honesty: these are not bad tools, but for our clients they are usually not the right choice.
- WordPress as greenfield default
- Renovating or migrating an existing WordPress site, sure. Building a new site, we don't default to WordPress: too much maintenance, too much plugin risk, too many security patches. A Next.js business site is cheaper and faster long-term.
- Salesforce for small SMB
- Too heavy, too expensive, too many consulting hours to get running. For clients with fewer than 50 sales people, a simpler CRM (HubSpot, Pipedrive, or a small custom system) is almost always better.
- On-prem Active Directory for small businesses
- A domain controller in a server cabinet, for a fifteen-person company, is rarely the right call in 2026. Microsoft Entra ID (cloud) or Google Workspace deliver the same without the hardware burden.
- Closed-source SaaS-only telephony without an export path
- Telephony where you cannot export your numbers, IVR trees and call logs when you want to leave: we advise against. SIP-based providers with portability are the right direction.
Where we bring in partners
Honest about what we don't do ourselves. For the following work packages we have a fixed partner network, with one point of contact on our side.
- Native mobile apps
- iOS in Swift, Android in Kotlin. Cross-platform (React Native, Flutter) we do in-house, but for truly native work we bring in partners.
- Deep brand design
- Logo from scratch, brand strategy, complete identity. We have our own design approach for business sites and SaaS UIs, but we are not a brand agency.
- Legal advice
- GDPR compliance at the operational level we handle ourselves; legal contract work and disputes go to an NL law firm we work with.
- Specialised cybersecurity audits
- NIS2 baseline and quickchecks we do ourselves. For deep pen-tests, code audits and certification we work with specialised security firms.
How we work
- Code in your GitHub organisation
- We are collaborator while we work. On handover we drop our access if you want. No escrow, no 'rights granted on payment'.
- Vercel deploy in your account
- Production and staging in your own Vercel team. We have access to deploy, you keep ownership and billing.
- Docs and post-launch support
- README, env vars, deploy instructions. Four weeks after launch, bug fixes without extra invoice.
- Senior, no junior hours
- We don't send a junior to learn on your budget. Every hour we invoice is senior work.
Who this is for
- SMB decision-makers who want to operate without an in-house IT team and want to know what runs under their stack.
- Tech-savvy decision-makers who want to verify their choices before they sign.
- Other consultants and developers who want to read our work, and possibly collaborate.
Question or project on the table?
Want to dig deeper, or curious whether your stack fits ours? Send a short description, we reply within two business days.
Build: 063cbb1