Best forA schema-first ORM with generated types and migrations.
Trade-offA generated client and its own schema language sit between you and SQL; complex queries often drop back to raw SQL.
Used by 37 makers' products for this
On GitHub, 6 public pull requests since Oct 2024 moved projects off Kysely: Drizzle ORM (6); 15 moved to Kysely.
For database access & ORMs, the alternatives to Kysely that makers' products we track chose most are Prisma (37), Drizzle ORM (12) and SQLAlchemy (1). 5 of the 5 are open source or self-hostable (Prisma, Drizzle ORM, SQLAlchemy and 2 more) and 5 have a free tier.
Not a ranking: each option is described by the situation it fits, with its trade-off.
Public pull requests on GitHub since Oct 2024 whose title says "Kysely to …" or "… to Kysely": real code changes, by developers in general, not only makers. Each count opens the search that finds them.
| Tool | Moved from Kysely | Moved to Kysely | |
|---|---|---|---|
| 6 | 5 | ||
| 0 | 10 |
How many makers' products we track use each for database access & ORMs.
| Option | Kind | Makers' products | Free tier | Open source | |
|---|---|---|---|---|---|
| Query builder | 0 | Yes | Yes | ||
| Schema-first ORM | 37 | Yes | Yes | ||
| SQL-shaped ORM | 12 | Yes | Yes | ||
| SQL-shaped ORM | 1 | Yes | Yes | ||
| Schema-first ORM | 0 | Yes | Yes | ||
| Schema-first ORM | 0 | Yes | Yes |
Schema-first ORM, SQL-shaped query builder, or the platform's own SDK. A schema-first ORM generates types and migrations from one schema file and hides the SQL; a SQL-shaped ORM or query builder keeps queries close to SQL with full types and a smaller runtime; a backend platform (Supabase, Convex, Firebase) comes with its own client, and adding an ORM on top is often unnecessary.
Kysely (Query builder): A type-safe SQL query builder for TypeScript, with no schema file or code generation step of its own. Trade-off: A query builder rather than a full ORM — migrations are basic and relations are joins you write.
Best forA schema-first ORM with generated types and migrations.
Trade-offA generated client and its own schema language sit between you and SQL; complex queries often drop back to raw SQL.
Used by 37 makers' products for this
Best forA thin, SQL-like TypeScript ORM that runs well on serverless and edge runtimes.
Trade-offCloser to SQL means you need to know SQL, and there are fewer guides and integrations than for Prisma.
Used by 12 makers' products for this
Best forPython backends (FastAPI, Flask, scripts) that want an ORM or a SQL toolkit over any relational database.
Trade-offA large API with two styles (ORM and Core); migrations come from a separate tool, Alembic.
Used by 1 maker's product for this
Best forClass-and-decorator entities in TypeScript, especially in NestJS apps.
Trade-offType safety on queries is weaker than Drizzle, Kysely or Prisma.
No maker product tracked for this yet
Best forModels, associations and migrations in plain JavaScript Node.js apps, especially existing Express codebases.
Trade-offBuilt before TypeScript was common, so typing is added on and query results are weakly typed; the next major version has been in alpha for years.
No maker product tracked for this yet
It depends on what you need it for; we don't rank them. The one makers' products we track chose most for database access & ORMs is Prisma (37 makers' products). You want one schema file that generates types, migrations and a readable query API: Prisma. You deploy to serverless or edge functions and want queries that read like SQL, fully typed: Drizzle ORM. Your backend is Python and not Django: SQLAlchemy.
Yes. For database access & ORMs, Prisma, Drizzle ORM, SQLAlchemy, TypeORM and Sequelize have a free tier a small product can start on.
Yes. For database access & ORMs: Prisma, Drizzle ORM, SQLAlchemy, TypeORM and Sequelize.
On GitHub, 6 public pull requests since Oct 2024 moved projects off Kysely: Drizzle ORM (6); 15 moved to Kysely. Each is a real code change in a public repo, by developers in general.