The stack.
Same tools every project. No spelunking, no committee debates.
Most agencies pick a stack to look impressive. We pick one to ship in 2 weeks and run on $0–50/month at low scale.
Frontend
One framework, one type system, one styling layer. We don't debate it per project.
Backend
Postgres for everything we can. Boring, fast, ten years from now it still works.
Auth
NextAuth for most. Clerk when MFA and org-management actually need to be solved.
Payments
Stripe Checkout for one-time. Stripe Billing for subscriptions. Webhooks land in Postgres.
Transactional only. We don't do marketing email — that's a different tool, different problem.
Background jobs
Inngest for most. Vercel Cron for the simple stuff. We avoid spinning up Redis if we can help it.
AI
Claude reads, GPT speaks, Gemini scales. Provider-agnostic abstraction so we can swap in a config flip.
Hosting
Vercel for the app. AWS S3 for files. Cloudflare for DNS. Three vendors, each best at their job.
Observability
Sentry catches what users hit. Analytics tells us what users do. AI cost tracking is its own line item.
Project board (optional)
When the engagement is multi-month, we use Linear so you can see what's shipping and what's next.
Why this stack?
Because it ships in 2 weeks and runs on $0–50/month at low scale.
Most agencies pick a stack to look impressive: microservices, Kubernetes, three databases, four queues, an event bus, six Lambda functions, and a Datadog bill bigger than the engineering team. We pick one to ship fast and bill cheap. When you outgrow it, you replace pieces — not the whole thing. The stack is boring on purpose.
Want this stack on your build?
Free 45-min architecture audit. We map your problem onto this stack and tell you exactly what we'd ship, in what order, for how much.