Uses
The stack we build on.
The tools, frameworks, and services we reach for first — both for client work and for our own builds. Updated as the stack evolves.
Web + product
Our default stack for everything we ship.
App Router, deployed on Vercel. The right answer for ~90% of web builds.
Non-negotiable. The compiler catches more bugs than we ever could.
Pragmatic, fast, easy to hand off to other developers.
Accessible primitives we build on top of when projects need real UI surface area.
AI + agents
What we reach for when the answer is intelligence.
Our default for serious work — best reasoning, best tool use, predictable behavior.
Clean abstraction for streaming responses, structured outputs, tool use.
When a workflow has real graph structure. We avoid it when something simpler works.
Used when a specific capability or price point fits better than the default.
Data + integrations
What sits underneath the AI and the apps.
Default database. Serverless Postgres gets you 95% of the way for 5% of the operations cost.
Type-safe DB access. Drizzle for new builds, Prisma when the project already has it.
Reliable background jobs, cron, and event-driven workflows. Replaces a lot of homegrown queue code.
When the workflow is owned by non-engineers and needs a UI to maintain it.
Email + comms
The boring infrastructure that has to work.
Transactional email. Clean API, fair pricing, doesn't get marked as spam.
Email templates as React components. Finally fixes the worst part of email.
Where every project lives. We work in the client's workspace, not a separate one.
Hosting + ops
Where the work runs.
Default for Next.js. Best DX, zero ops, predictable bill until you're huge.
DNS, CDN, R2 for object storage. Sometimes Workers for edge logic.
Error tracking. We don't ship anything to production without it.
Privacy-respecting analytics. We avoid GA for new projects.
How we work day-to-day
Tools, hardware, opinionated takes.
Editors. Cursor for the heavy AI-pair-programming days.
Where a lot of the work happens, including this site.
Cheap insurance against the laptop being the bottleneck.
Project tracking. Better than the alternatives by a clear margin.
Inspired by the /uses tradition. Have a tool you swear by? Tell us about it.
Let's build
Stack feel familiar?
If your team is already living in this neighborhood, we'll fit right in.
Book a consultation →