Declare what you want. The planner decides how. Then shows you why.
The planner chooses between EXISTS, JOIN, and lateral subqueries based on relation cardinality. You describe what, it decides how.
Every query exposes its plan, compiled SQL, and bound parameters via dump(). Debug before you execute.
Schema-per-tenant isolation with orm.withSchema(). Every query is automatically scoped — no manual prefixing.
Direct pg Pool — no ORM layer, no codegen, no runtime dependencies. Tree-shakeable ESM.
Hierarchies via include({ recursive: true }) with automatic CTE generation. Trees and graphs without raw SQL.
Built-in helpers for pgvector (cosine distance, L2, inner product) and ParadeDB (BM25 full-text search).
Write what you need in TypeScript or NQL — tables, filters, relations, aggregations.
orm.select('posts').where(eq('published', true)).include('author')The semantic planner analyzes cardinality, chooses JOIN strategy, extracts CTEs, optimizes.
include-strategy: lateral-join (to-one relation)Every decision is visible via dump() — SQL, parameters, plan reasoning. Debug before you execute.
SELECT ... FROM "posts" LEFT JOIN LATERAL (...) WHERE $1No codegen step. Full SQL observability via dump(). The planner shows you why it chose a strategy, not just what SQL it generated. Native multi-tenant with withSchema().
// See every decision the planner makes
const dump = orm.select('posts')
.where(eq('published', true))
.include('author')
.dump();
dump.plan.decisions
// → [{ type: 'include-strategy',
// choice: 'lateral-join',
// reason: 'to-one relation' }]Automatic include strategy selection — no manual JOINs for relations. The planner picks lateral, subquery, or join based on cardinality. Built-in pgvector and ParadeDB helpers.
// Relations just work — planner decides strategy
const users = await orm
.select('users')
.include('posts.comments.author')
.dump();
// Nested 3-level include — zero manual JOINs
// Result: users[].posts[].comments[].authorFirst-class relation handling with .include(). Schema-level type inference without manual interface definitions. Multi-tenant isolation built-in, not bolted on.
// Multi-tenant in one line
const tenantOrm = orm.withSchema('acme_corp');
const users = await tenantOrm
.select('users')
.where(eq('active', true))
.dump();
// → SELECT * FROM "acme_corp"."users" WHERE ...The core planner, schema DSL, query builders, and NQL work independently of any database. Write once, swap adapters.
v1.0.1 highlights: Range operators (rangeOverlaps, rangeContains, rangeContainedBy), dump({ queryName, correlationId }) for end-to-end request tracking, fixed relation-mode .join() on compile-only adapters.