Technology
Stack overview
The technology Solagon builds with by default — and why we picked it.
Last updated 2026-04-27
Solagon's default stack is intentionally narrow. We picked the pieces because they're widely-deployed, well-supported, hire-able for, and run cheap to host. Sticking to a small list also means we get faster at every engagement instead of relearning the same surface ten times.
We deviate when it makes sense — but you'd be surprised how rarely the deviation actually pays off.
The default stack
| Layer | Default | Why |
|---|---|---|
| Frontend framework | Next.js 14 (App Router) | Best-in-class React framework, excellent SEO, great DX |
| Language | TypeScript | Catches bugs at compile time; saves money in maintenance |
| Styling | Tailwind CSS + design tokens | Consistent design system, no CSS-in-JS overhead |
| Database | Postgres (via Neon) | The default DB choice for serious work for 30 years |
| ORM | Drizzle | Type-safe, no codegen step, light runtime |
| Auth | Clerk | Production-grade auth without us writing it |
| File storage | Vercel Blob | Trivial for an app that already runs on Vercel |
| Resend + react-email | Reliable transactional email with components | |
| Hosting | Vercel | Best DX for Next.js; commitments-free pricing |
| Analytics | Plausible or GA4 | Stop arguing about analytics; pick one and ship |
| Error tracking | Sentry | Industry standard for a reason |
Every part of this list is there because it has stayed boring under load. Boring is what you want for software you're going to live with for five years.
What we deviate to (and why)
We pick a different tool when:
- The default genuinely can't do the job. E.g., very large image processing might need Cloudflare Workers / Image Resizing instead of Vercel's defaults.
- Your team already knows another tool. If your engineers are heavy on Django, building a parallel Next.js app means we ship a thing your team can't maintain. We'll either match what they know or make a deliberate plan to migrate.
- Compliance requires it. HIPAA, FedRAMP, etc., sometimes constrain hosting / data-store choices. We'll work with your security team's requirements.
- The economics are wrong. Vercel is great until you serve 100M req/month from a single endpoint. We'll move to a cheaper host when the math says so.
We don't deviate because something new and shiny came out, even if we'd love to play with it. New isn't a value.
What you should expect this to mean
A few practical implications of the stack choice:
- Hire-able. Your future engineering hires can read the codebase. Next.js + Postgres + TypeScript is a job posting that gets responses.
- Cheap to run. A typical Solagon-built marketing site costs $0–$20/month to host. A platform with real traffic might be $200–$1,000/month. We don't build things that need a $40k/year infrastructure budget unless the business requires it.
- Easy to migrate off. Standard formats. Standard databases. Standard storage. If you ever want to move to a different host or rewrite a component, you can.