Tech stack

What we actually build with.

This is a short list on purpose. It is what we use often enough to be good at, not everything we have touched — and each one says what we do with it, because a wall of logos tells you nothing.

Web

Build

Next.jsOur default for web apps and marketing sites — server rendering where SEO matters.
ReactComponent layer for everything on the web.
TypeScriptEvery new project. Catches the class of bug that reaches production otherwise.
Tailwind CSSDesign tokens in one place, so a brand change is one file.

Mobile

Build

FlutterOne codebase for iOS and Android. Our main mobile stack.
DartThe language Flutter runs on.
FirebasePush notifications, crash reporting, and auth when it fits.

Backend

Build

Node.jsREST and GraphQL APIs, background jobs, queues.
PHPExisting systems and Laravel-era codebases we maintain or extend.
PostgreSQLDefault relational database for new work.
MySQLCommon in systems we take over.
RedisCaching, sessions, and job queues.

Cloud

Deploy

AWSEC2, ECS, Lambda, RDS, S3, CloudFront, Route 53 — set up and then operated.
Google CloudCloud Run, Cloud SQL, GKE. Also where most of our migrations land.
VercelFront-end hosting when the app is Next.js and the team is small.

DevOps

Deploy

DockerSo the thing that runs in production is the thing we tested.
TerraformInfrastructure as code — recovery is a command, not archaeology.
GitHub ActionsCI, staging deploys, and one-command rollback.

Operations

Run

CloudWatchAlarms on error rate, latency, disk, and spend.
SentryError tracking, so we hear about a crash before your users tell you.

Using something that isn't on this list?

Tell us what it is. If we haven't worked with it, we will say so rather than learn on your budget.

Let's talk