22 October 2026
Every few years we step back and evaluate the tools we use. Not because the old ones stopped working, but because the landscape changes and staying informed is part of the job. Here's what our stack looks like in 2026 and why.
We use Next.js for most web projects. Server-side rendering, static generation, API routes, and file-based routing in one framework. The App Router has matured significantly and handles everything from simple marketing sites to complex web applications.
Tailwind CSS handles styling. It's fast to write, easy to maintain, and produces small CSS bundles. We pair it with CSS variables for theming (light/dark mode) rather than relying on Tailwind's built-in dark mode classes.
For simpler projects or when the client has an existing React codebase, we'll use Vite with React. For backend-heavy applications, NestJS or Ruby on Rails depending on the team's preference and the project requirements.
Both are excellent. We choose between them based on the project. Flutter when we want pixel-perfect consistency across platforms or when the UI is heavily custom. React Native when the client's team already knows React or when we need deep native module integration.
Flutter's been our default for new mobile projects over the past year. The developer experience is faster, the widget system is more predictable, and multi-platform support (iOS, Android, web, desktop) from one codebase is genuinely useful.
For desktop applications, Electron is the pragmatic choice when the app is an extension of a web product. Flutter desktop is newer but surprisingly capable for cross-platform desktop apps that don't need heavy native integration.
For Java-based enterprises, we still use JavaFX. It's not fashionable, but it's rock-solid for line-of-business desktop applications.
TypeScript everywhere. Having the same language on frontend and backend reduces context-switching and lets us share types and validation schemas across the stack.
We use NestJS for larger backends that need structure (dependency injection, modules, decorators). For simpler APIs, Next.js API routes or a lightweight Express setup does the job.
When a project needs something different — Ruby on Rails for rapid prototyping, Java Spring Boot for enterprise integration — we use the right tool rather than forcing our default.
Need something built with modern tools?
We use the stack described here for every client project. Let's talk about yours.
Start a ConversationPostgreSQL is our default relational database. It handles everything from simple CRUD apps to complex queries with JSON support, full-text search, and geo-spatial data.
Firebase is our go-to for mobile apps that need real-time data, authentication, and push notifications without building a custom backend. It's fast to set up and scales automatically.
For graph data, we've used Neo4j on projects where relationships between entities are the core domain model.
Vercel for Next.js projects. The deployment pipeline is effortless and the edge network is fast globally. This website runs on Vercel.
AWS and Google Cloud for everything else. Which one depends on client preference, existing infrastructure, and specific service requirements. We don't have religious opinions about cloud providers.
DigitalOcean for simpler hosting needs where the full AWS complexity isn't justified.
Git and GitHub for version control. Linear for project management. Figma for design handoffs. Postmark for transactional email. Cloudflare for DNS, security, and Turnstile CAPTCHA.
We keep our toolchain lean. Every tool in the stack earns its place by saving more time than it costs to maintain.
Honestly, not much right now. The biggest shift we're watching is AI-assisted development tools. We use them daily for code generation, testing, and documentation. The productivity gains are real, and we expect this to become a bigger part of our workflow.
The stack matters less than people think. What matters more is knowing when to use what, and having the discipline to pick boring, proven tools over exciting new ones. That's what we try to do.
If you're curious about the technology behind a specific project, browse our portfolio or ask us directly.
We specialise in turning ideas into working products fast. Tell us what you're building and we'll show you how we'd get it done.
Australian dev team. 10+ products shipped. Free initial consultation.
