Compare

18 honest comparisons.

Every page here says where the other framework is the better choice before it says where Stacks is, because a comparison that never concedes anything is an advertisement. The table below is about what ships in the box, which you can check, rather than which is faster, which depends on what you build.

Where Stacks fits best is a team that wants to own its data and its environment. The database, the files, the mail server, and the app all run on servers you choose, through deploy drivers for Hetzner, AWS, or any Linux box over SSH, and the only bill is the servers themselves. It is also the only framework here with its own mail server: real mailboxes on your domain, on the same box, with no per-seat inbox subscription.

All features All use cases

What arrives with the install.

Almost anything can be added to almost anything given enough time. This is the default path a team takes, not the theoretical ceiling.

Framework Auth and roles ORM and migrations Queues and jobs Transactional mail Admin dashboard Realtime Deploy and infrastructure Own mail server
StacksFull-stack TypeScript framework In the box In the box In the box In the box In the box In the box In the box In the box
Next.jsReact meta-framework Bring your own Bring your own Bring your own Bring your own Bring your own Bring your own Partly Bring your own
NuxtVue meta-framework Partly Partly Bring your own Partly Bring your own Partly Partly Bring your own
SvelteKitSvelte meta-framework Partly Partly Bring your own Bring your own Bring your own Bring your own Partly Bring your own
React Router (Remix)React meta-framework Bring your own Bring your own Bring your own Bring your own Bring your own Bring your own Partly Bring your own
AstroContent-first framework Bring your own Bring your own Bring your own Bring your own Bring your own Bring your own Partly Bring your own
RedwoodJSFull-stack React In the box In the box In the box In the box Partly Partly Partly Bring your own
The T3 StackAssembled stack Partly Partly Bring your own Bring your own Bring your own Bring your own Partly Bring your own
NestJSBackend framework Partly Partly Partly Partly Bring your own Partly Partly Bring your own
AdonisJSBackend framework In the box In the box Partly In the box Bring your own Partly Bring your own Bring your own
Express and FastifyHTTP frameworks Bring your own Bring your own Bring your own Bring your own Bring your own Bring your own Bring your own Bring your own
HonoEdge HTTP framework Partly Bring your own Bring your own Bring your own Bring your own Partly Bring your own Bring your own
ElysiaBun HTTP framework Partly Bring your own Bring your own Bring your own Bring your own Partly Bring your own Bring your own
Encore.tsInfrastructure framework Partly Partly In the box Bring your own Bring your own Partly Partly Bring your own
LaravelFull-stack framework In the box In the box In the box In the box Partly In the box Partly Bring your own
Ruby on RailsFull-stack framework Partly In the box In the box In the box Partly In the box In the box Bring your own
DjangoFull-stack framework In the box In the box Partly In the box In the box Partly Bring your own Bring your own
SupabaseBackend as a service Hosted Hosted Partly Bring your own Hosted Hosted Hosted Bring your own
FirebaseBackend as a service Hosted Hosted Partly Partly Hosted Hosted Hosted Bring your own
In the box

Ships with the framework and is documented as the way to do it.

Partly

Available, but through an official add-on, a paid product, or a well-known community package.

Bring your own

Not provided by the framework. You choose a library and wire it up.

Hosted service

Provided, but as a managed service you consume rather than code you run.

Full-stack JS

Frameworks that render pages and own a routing layer.

Stacks vs Next.js

The React meta-framework. Stacks answers the backend questions Next.js deliberately leaves open.

Stacks vs Nuxt

Vue meta-framework with a strong module ecosystem. Stacks brings the application layer under it.

Stacks vs SvelteKit

Small bundles and a lovely reactivity model. Stacks adds everything behind the load function.

Stacks vs React Router (Remix)

Remix v2 lives on as React Router framework mode. Stacks shares its web-standards philosophy and ships more of the stack.

Stacks vs Astro

The best content site framework there is. Stacks is for when the site becomes an application.

Stacks vs RedwoodJS

Full-stack React and GraphQL, now split into Redwood GraphQL, RedwoodSDK, and the CedarJS fork. Different bets, same goal.

Stacks vs The T3 Stack

Best-in-class parts, assembled by you. Stacks is the same territory, maintained as one thing.

TypeScript backends

Server frameworks you would build an API or a service on.

Stacks vs NestJS

Structured TypeScript backends with dependency injection. Stacks trades DI for conventions.

Stacks vs AdonisJS

The other Laravel-inspired TypeScript framework. The closest comparison on this page.

Stacks vs Express and Fastify

Minimal HTTP layers. Everything above the router is a decision you make and maintain.

Stacks vs Hono

A tiny, fast, edge-first router. Stacks is the application you would build on top of one.

Stacks vs Elysia

A high-performance Bun-first framework with end-to-end types. Stacks is the framework around one.

Stacks vs Encore.ts

Infrastructure from code, for distributed backends. Stacks does it for one application.

Other ecosystems

The mature stacks outside TypeScript, and the hosted platforms.

Stacks vs Laravel

The framework Stacks is modelled on, rebuilt in TypeScript on Bun.

Stacks vs Ruby on Rails

Convention over configuration, the original. Same convictions, different runtime and type story.

Stacks vs Django

Batteries included, and the best free admin in the business. Stacks brings that idea to TypeScript.

Stacks vs Supabase

A hosted Postgres platform, not a framework. The two are often used together.

Stacks vs Firebase

Client-first sync and mobile SDKs. Stacks is the server-first alternative you own.