All articles
Behind the Scenes Aug 6, 2026 1 min read
tools workflow

The tools we actually use (and the ones we skip)

A boring stack on purpose: the test every tool must pass before it ships.

The tools we actually use (and the ones we skip)

The honest stack

People expect a studio to run on exotic tooling. The truth is more boring — and that's deliberate. We use tools that are boring in the best way: predictable, well-documented, and unlikely to vanish next quarter.

What's actually on the desk

  • Laravel + MySQL for client work — mature, boring, fast to ship
  • Vite + Tailwind for frontends — no runtime surprises
  • Git + a staging server — every change reviewed before it touches production
  • AI assistants for drafting and review — speed, not decisions

What we deliberately skip

Kubernetes. Microservices. Serverless event meshes. Blockchain anything. Not because they're bad — because none of our clients need them. Every one of those adds operational complexity, and complexity is a cost the client pays forever.

Technology choices are business decisions wearing technical clothes.

The test every tool must pass

Before we adopt anything, we ask one question: if the person who chose this tool leaves the project, can the next person understand it in an afternoon? If the answer is no, it doesn't ship. That single rule has saved our clients more money than any optimization ever has.

Reading is good. Shipping is better.

Tell us what's broken and a human will come back with a fixed-price proposal within 48 hours.

Submit a problem