Does Weavori replace prisma db seed?

Not entirely, and the split is natural. Keep prisma db seed for the small, deliberate data your application needs to boot — defaults, reference rows, an admin user. Use Weavori when the job is a full dataset: it reads the live schema, resolves foreign keys by construction, samples pg_stats for realistic distributions, and needs no seed script.

Does prisma migrate reset still seed my database?

Not in Prisma ORM v7. Automatic seeding during prisma migrate dev and prisma migrate reset was removed; seeding now runs only when you invoke npx prisma db seed explicitly. If your workflow depends on a reset producing data, that step has to be explicit.

Where do I configure the seed command in Prisma?

In Prisma ORM v7, seeding is configured in prisma.config.ts under the migrations seed key — for example a seed value of tsx prisma/seed.ts — rather than the prisma.seed key in package.json used by earlier versions. npx prisma db seed executes whatever command you put there.

Does Weavori work in a Prisma project?

Yes. Weavori never reads schema.prisma — it connects to the PostgreSQL database directly, introspects the real schema, and generates against it. That means it works alongside Prisma, TypeORM, Drizzle, or a database no ORM manages at all.

weavori vs prisma db seed

Weavori vs prisma db seed

Prisma's seed command — you bring the data

Prisma ORM v7 removed automatic seeding from prisma migrate dev and prisma migrate reset — your seed script still runs, but only when you invoke it. That exposes what was always true here: prisma db seed is a runner, Weavori is a generator, and the two answer different questions. Prisma's docs scope seeding to the data an application needs to start — a default currency, a default language — and for that a seed script is exactly right. A production-shaped dataset is a different job: you write the loops, the insert order, the value ranges, and maintain them as the schema moves. Weavori generates that dataset from the live schema in one command, with foreign keys resolved by construction and distributions sampled from pg_stats. Keep the runner for reference rows. Add the generator when the database needs a dataset.

Pricing verified September 2026 · Integrated seeding workflow (Prisma ORM) · prisma db seed website ↗

At a glance

Dimension	Weavori	prisma db seed
Category	Schema-driven CLI	Integrated seeding workflow
What it produces	A whole dataset, from the live schema	Whatever your seed script inserts
Who writes the data logic	Nobody — the schema drives it	You write prisma/seed.ts
Distributions	Sampled from pg_stats	Uniform, or whatever your script does
FK integrity	By construction, parent-first	Your responsibility — insert order and upserts
Cross-column coherence	Temporal ordering, conditional nullability, CHECK constraints	Only what your script enforces
Drift risk	None — the schema is re-read every run	seed.ts duplicates what the schema already says
Scale	Streaming, constant memory — 100,000 rows across 14 tables in 12.4s	Limited by script design and memory
Cost	Free 2K rows/mo; Pro $15/mo	Free (ships with Prisma)

See the plan before a single row is written

Point Weavori at any PostgreSQL database — the preview shows what it will generate, table by table.

How they compare

A closer look at the dimensions that actually change the decision, and where each tool wins.

Runner versus generator

weavori

Weavori is a generator: it introspects the database, plans the work table by table in foreign-key dependency order, and writes the rows. There is no script — the schema is the specification. Typical schemas under 200 tables finish in under two minutes; a 2,500-row run takes 384ms.

prisma db seed

prisma db seed is a runner. You declare a seed command in prisma.config.ts and npx prisma db seed executes it. Everything about the data — which rows, how many, in what order — lives in the script you wrote.

Bottom line: Prisma's documentation scopes seeding to data the application needs to start, such as a default currency or a default language. For that job a seed script is exactly right. Scaling the same pattern into a realistic dataset is a separate project, and Prisma is not claiming otherwise.

Schema truth and drift

weavori

The database is the source of truth on every run. Add a table, rename a column, tighten a CHECK constraint — the next generation adapts with no code change.

prisma db seed

schema.prisma describes the models; seed.ts describes the rows. Two descriptions of one system, kept in sync by hand. When a model changes and the seed script does not, the script still runs — and the data quietly stops matching the schema: a new enum member the script never inserts, a new relation it never exercises.

Bottom line: For two reference rows, hand-maintaining the script is trivial. As the dataset grows, that second description becomes the maintenance burden — the same problem Weavori removes.

Distributions and integrity

weavori

Weavori samples pg_stats so value frequencies match production — a status column that is 70% active stays 70% active — and enforces cross-column coherence: temporal ordering, conditional nullability, and CHECK constraints.

prisma db seed

A seed script inserts whatever it creates. In practice that means a synthetic-data library or literal values, which are uniform by nature, and referential ordering is something you implement — Prisma's own docs use upsert so the seed can run twice without failing.

Bottom line: If your tests or query plans depend on data that behaves like production, distribution sampling matters. For plausible reference data, the script's own values are fine.

Automation and CI

weavori

Weavori is a standalone CLI with API keys, plain/JSON output, standardized exit codes, and offline Ed25519 license validation — built to run headless, including air-gapped. It also ships an MCP server (weavori mcp, 5 tools), so Cursor, Claude Desktop, VS Code Continue, or Qoder can introspect the schema, estimate the run, and generate the dataset without you leaving the editor.

prisma db seed

prisma db seed fits a Prisma project's own workflow, and accepts custom arguments after a double dash for per-environment behaviour. In CI it is one step among many, and the script it runs is code you maintain and ship alongside your application.

Bottom line: Inside a Prisma repository, npx prisma db seed is the idiomatic command and should stay. Weavori is what you add when the database needs a dataset rather than a handful of records.

Which one fits your team?

choose weavori when

Prisma projects that need a realistic dataset, not just reference rows
Teams whose tests depend on production-shaped skew
Anyone who would rather not maintain a growing seed.ts
CI pipelines that rebuild a database on every run
Seeding a PostgreSQL database that Prisma does not manage
Anyone who wants to try it on their own schema first — free tier and a 14-day trial, no credit card

choose prisma db seed when

Default and reference data the application needs at startup
Prisma-native projects that want seeding in the same toolchain
Fully deterministic, hand-specified fixtures
Small, static datasets that rarely change

Install Weavori and run it on your database

Free tier with unlimited runs, or the full-Pro trial for 14 days — no credit card either way.

Frequently asked questions

The questions we hear most from teams evaluating Weavori against prisma db seed.

Try Weavori against your own schema

Connect any PostgreSQL database and see the plan before a single row is written.

$npx --yes @weavori/cli generate postgres://localhost:5432/mydb

No credit card required. 14-day full-Pro trial, then free tier or subscribe.

Also compare: Tonic.ai · Mockaroo · Faker · How realistic test data is made