- Adopt
- Trial
- Assess
- Hold
- New
AdoptOur default. We reach for this without a discussion.
- 10
PostgreSQL
The default database for anything with relationships. JSONB, full-text search and window functions remove most of the reasons projects reach for a second store.
- 11
Bun
Runtime, package manager and test runner in one binary. Install and cold-start times are the difference we actually feel day to day.
- 12
Redis
Sessions, rate limits and job queues. Kept for those; not used as a cache in front of a database that is not yet slow.
- 13
Self-hosted Docker Compose
For clients who must own the box: one file that a new engineer can read, and the same file locally and in production.
- 14
Static hosting at the edge
A prerendered site needs a CDN, not a server. Cloudflare Pages and Netlify both end the conversation about uptime for marketing sites.
AssessWorth the time to understand. Not in client work yet.
- 15
Serverless PostgresNew
Scale-to-zero branches per pull request are genuinely useful. We want more evidence on cold starts and connection limits under real load first.
HoldWe do not start new work with this. Existing work is fine.
- 16
Kubernetes for small teams
Two services and a database do not need a control plane. It buys elasticity nobody asked for and charges an operations role the client has not hired.
Next step
Tell us what
you need built
Send the idea in whatever shape it is in — a document, a sketch, or two sentences. You get a written scope and a fixed figure back before anything is committed to.