BoilerplateHub

Best ORM and Query Layer for Nuxt SaaS in 2026

How does your code talk to the database? These 4 options list first-party Nuxt support. Community ports are deliberately left out, because glue you maintain yourself is not the same as support.

Nuxt 3 and later rebuilt the framework on Vue 3, Vite, and Nitro, which means Nuxt 2 answers are not partially correct, they are entirely wrong. An agent needs to know that composables, components, and utils are auto-imported, that the server directory runs on Nitro with h3 helpers rather than Express, and that data fetching has to be SSR aware or the same request fires twice. Config lives in defineNuxtConfig and runtime values come from useRuntimeConfig, not from process.env at the point of use.

Quick picks

Best overall

Drizzle

Queries map closely to SQL, so you can predict what the database receives.

Best free or open source

Prisma

One schema file is the single source of truth for types and migrations.

Worth a look

Kysely

You write SQL semantics directly, so nothing surprising reaches the database.

All 4 options

1. Prisma

Visit →

Schema-first TypeScript ORM that generates a typed client and handles migrations from a single schema file.

Cost shape: The ORM is free and open source. Optional hosted extras like connection pooling are billed separately.

Strengths

  • ✓One schema file is the single source of truth for types and migrations.
  • ✓Generated client gives autocomplete over relations that is hard to beat.
  • ✓Migration tooling handles the common cases without you writing SQL.

Tradeoffs

  • ✗Its own schema language sits outside SQL, so unusual database features need escape hatches.
  • ✗The generate step must run in build pipelines or types silently go stale.
  • ✗Query builder hides the emitted SQL, which complicates performance tuning.

2. Drizzle

Visit →

TypeScript ORM where the schema is plain code and queries read like the SQL they compile to.

Cost shape: Free and open source, with optional paid hosted tooling around it.

Strengths

  • ✓Queries map closely to SQL, so you can predict what the database receives.
  • ✓No code generation step, since the schema is ordinary TypeScript files.
  • ✓Very light at runtime, which suits edge and serverless deployments.

Tradeoffs

  • ✗Closeness to SQL means you write more of it than with a heavier ORM.
  • ✗Deeply nested relational fetches get verbose compared to a generated client.
  • ✗Type inference errors can be long and hard to read when schemas grow.

3. Kysely

Visit →

A type-safe SQL query builder rather than an ORM, for people who want SQL with autocomplete.

Cost shape: Free and open source, with no hosted component to buy.

Strengths

  • ✓You write SQL semantics directly, so nothing surprising reaches the database.
  • ✓Types come from your database schema, catching column typos at build time.
  • ✓Tiny surface area, so it composes with whatever migration tool you prefer.

Tradeoffs

  • ✗No entity model or change tracking, since it deliberately stops at queries.
  • ✗Migrations and schema types are separate concerns you must wire together.
  • ✗Relation loading is manual, so nested reads take deliberate assembly.

4. TypeORM

Visit →

The classic decorator-based TypeScript ORM, familiar to anyone coming from Java or C# entity mapping.

Cost shape: Free and open source, maintained by the community.

Strengths

  • ✓Active Record and Data Mapper patterns are both available for different team tastes.
  • ✓Entity decorators feel immediately familiar to developers from Hibernate or Entity Framework.
  • ✓Long history means most integration problems have been hit and documented already.

Tradeoffs

  • ✗Decorator metadata relies on compiler settings that trip up modern build tools.
  • ✗Lazy relations make it easy to fire many queries without noticing.
  • ✗Maintenance pace has been uneven, leaving long-lived issues open.

Pricing described qualitatively because published plans change often. Data checked 2026-08-23.

Side by side

Option Cost shape Main tradeoff
Prisma The ORM is free and open source. Optional hosted extras like connection pooling are billed separately. Its own schema language sits outside SQL, so unusual database features need escape hatches.
Drizzle Free and open source, with optional paid hosted tooling around it. Closeness to SQL means you write more of it than with a heavier ORM.
Kysely Free and open source, with no hosted component to buy. No entity model or change tracking, since it deliberately stops at queries.
TypeORM Free and open source, maintained by the community. Decorator metadata relies on compiler settings that trip up modern build tools.

Frequently asked questions

What is the best orm and query layer for Nuxt?

Drizzle is the safest default because it works across the widest range of projects: TypeScript ORM where the schema is plain code and queries read like the SQL they compile to. That said, Closeness to SQL means you write more of it than with a heavier ORM. If that matters to you, one of the others below is the better call.

Is there a free option for Nuxt?

Prisma is the one to look at. The ORM is free and open source. Optional hosted extras like connection pooling are billed separately. The tradeoff: Its own schema language sits outside SQL, so unusual database features need escape hatches.

How many orm and query layer options actually support Nuxt?

4 of the options we track list first-party support for Nuxt. We only count documented support, not community ports, so the real number is sometimes higher if you are willing to maintain the glue yourself.

Go deeper

Head to head

→ Drizzle vs Prisma→ Kysely vs Prisma→ Prisma vs TypeORM→ Drizzle vs Kysely→ Drizzle vs TypeORM→ Kysely vs TypeORM

Other layers for Nuxt

DatabasePaymentsTransactional EmailHostingAnalytics

Same layer, other frameworks

Next.js
Nuxt boilerplates → Agent setup for Nuxt → Stack recommender →