Tech stack
The tools we build with
Split by discipline: the game pipeline on one side, the web stack on the other, and what each tool is for.
Everything we build with, split by discipline and grouped by the job it does. We pick from these lists per project rather than forcing every brief through the same stack.
Game development
Games
A 2D pipeline in Unity: prototype, build, release, patch.
01
Engine and code
Where the game itself gets made.
Unity
The engine behind every game we ship: 2D scenes, physics, animation and custom editor tooling.
C#
The language our gameplay, systems and editor tools are written in.
Unity 2D
Tilemaps, sprite animation and 2D physics, which is all our games need.
02
Ship and iterate
Getting a build in front of players and keeping it there.
Steam
Store pages, builds and post-launch updates for finished PC titles.
Git
A branch per feature and a history we can walk back through when something stops feeling right.
Figma
UI layouts, HUD mockups and art direction before anything gets built.
Web development
Web
From a marketing site to a platform with a long roadmap.
01
Languages
What the code itself is written in.
TypeScript
Typed JavaScript that catches mistakes before they reach production.
JavaScript
The language of the web and the foundation of everything we ship in the browser.
PHP
The language behind years of our platform, e-commerce and CMS work.
Python
Scripting, tooling and the odd side project like our PyQuickie extension.
02
Front end
How interfaces get built and styled.
React
The UI library behind most of the interfaces we build.
Next.js
Our go-to framework for fast, search-friendly websites and web apps.
Astro
A framework for content sites that ship almost no JavaScript.
Livewire
Reactive interfaces for Laravel apps without a separate frontend stack.
Alpine.js
Small interactions dropped straight into server-rendered pages.
jQuery
The classic DOM library, still running large parts of the web.
Tailwind CSS
Utility-first CSS that keeps styling fast and consistent.
Bootstrap
The CSS framework behind many of the sites we maintain and extend.
Vite
The build tool behind our fastest front-end setups.
03
Back end and data
The systems and storage behind the interface.
Node.js
The JavaScript runtime behind our tooling, APIs and server-side code.
Laravel
A PHP framework for building solid, maintainable backends quickly.
Prisma
A typed database client for our TypeScript projects.
MySQL
The relational database behind most of our PHP and platform work.
PostgreSQL
A powerful open-source database we use for modern application work.
Redis
In-memory storage for caching, sessions and queues.
GraphQL
A query language for APIs that sends exactly the data a page needs.
04
CMS and commerce
So clients can edit their own content and sell from it.
WordPress
The most widely used CMS, tuned for clients who edit their own sites.
Craft CMS
A flexible, developer-friendly CMS for content-rich client sites.
Statamic
A Laravel-based flat-file CMS that keeps content and code in one repo.
Storyblok
A headless CMS with a visual editor, ideal for component-based sites.
Shopify
The platform we recommend for most online stores.
05
Hosting and infrastructure
Where the work runs once it is live.
Vercel
Zero-config hosting built for Next.js projects.
Netlify
Simple, reliable hosting for static and Jamstack sites.
SiteHost
Managed hosting for Laravel and PHP sites that need to sit close to their customers.
AWS
Cloud infrastructure for the projects that need more than a platform host.
Render
Straightforward hosting for APIs, workers and background jobs.
Kinsta
Managed WordPress hosting we trust with busy client sites.
WP Engine
Enterprise-grade WordPress hosting for client sites that cannot go down.
Cloudflare
DNS, CDN and security in front of most sites we look after.
Docker
Containers that make every environment behave the same.
06
Design and workflow
How the work gets designed, reviewed and shipped.
Figma
Where our designs are made, shared and handed to development.
Git
Version control on every project we touch, no exceptions.
GitHub
Where our code lives, gets reviewed and ships from.
BrowserStack
Real-device testing so sites work everywhere, not just on our machines.
Not sure which fits?
We will tell you
Send us the problem rather than the stack. We will come back with what we would use and why.