The technologies we master
Not tutorials, not PoCs - production experience on real SMB projects.
Frontend
The frameworks and languages we use to build modern, performant interfaces.
Backend & Infrastructure
The back-end technologies we use to build robust APIs and scalable infrastructures.
AI & Automation
The automation and AI tools we master to optimize your business processes.
Why this stack
Every line of code we ship is a long-term commitment. Picking the wrong framework for a custom SaaS does not just slow today's release - it locks the next two years of maintenance into the wrong direction. Our stack is the result of five years of production projects for SMBs and startups, deliberately reduced to the technologies where we have shipped the most demanding work.
Next.js 16 covers our frontends (App Router, React Server Components, edge rendering when it makes sense). Supabase backs nearly all our authentication, Postgres and storage needs - fast, SQL-first, easy to migrate out of if needed. n8n powers the automation layer when an in-house workflow engine would be overkill. Python and FastAPI cover anything ML, data pipelines or LLM integration heavy enough to warrant a dedicated service.
TypeScript runs end-to-end. The infrastructure side relies on Vercel for the frontend, Railway or Fly.io for stateful workloads, and OpenAI plus Anthropic for the LLM layer. Choosing this exact combination keeps onboarding under a week for a new contributor, simplifies hiring, and ensures that nothing in our stack will be deprecated by next year.
How we pick a tool
A new framework or library lands on our radar weekly. We ignore most of them. Three criteria must be met before a tool earns a spot in this list: we have shipped at least three production projects with it, the maintainers have a track record of stable releases beyond two years, and there is a credible exit path if the tool ever gets discontinued. The third criterion eliminates most of the JavaScript ecosystem on its own.
For our clients, the practical consequence is simple: we never use you as a beta tester. The shiny new framework you read about on Hacker News last week will only enter your codebase once we are sure we can still maintain it three years from now without a rewrite. If the tool clearly belongs to your project despite not being on this list, we tell you, and we negotiate the trade-off transparently.
If you want to dig deeper, each technology below links to a detailed page with our opinion, the project types it fits, and the gotchas we have run into in production.