Prisma · schema.prisma · seed data

Seed data for Prisma — straight from your schema.prisma.

Paste your schema.prisma and get a populated database where every relation resolves. @relation fields, scalar FK pairs and @unique one-to-one constraints are understood — export SQL/CSV/JSON or push to your database.

Generate test data — free See the live demo

Free tier · no card · EU-hosted · zero trackers

From Prisma schema to populated database

Paste your schema.prisma into the web app. The parser reads models, @relation(fields: [...], references: [...]) pairs and uniqueness constraints, and maps them to foreign keys with the right cardinality — one-to-many relations get realistic skew, one-to-one relations stay collision-free.

schema.prisma in — SQL out
model Post {
  id       Int  @id @default(autoincrement())
  author   User @relation(fields: [authorId], references: [id])
  authorId Int
}

# → INSERT INTO "user" ... then "post" —
#   author_id always resolves, 1–10 posts per user

What you get

FK-consistent

Every foreign key resolves

Children reference parents that exist — including self-references (parent_id) and one-to-one relations. Inserts come out in topological order, so the SQL loads into a constrained schema as-is.

realistic

Distributions like real life

Not every user has exactly 5 orders: long-tail and normal distributions create the skew where pagination and N+1 bugs actually show up.

current

Time-aware data

Timestamps generate relative to today — "last 30 days" dashboards stay populated instead of going empty as fixtures age.

reproducible

Deterministic per seed

Same seed, same data — reproducible CI runs. Export the generation config as JSON and commit it next to your migrations.

FAQ

Does it understand @relation fields?

Yes. The @relation(fields, references) pair maps to a foreign key; the scalar field's type and optionality carry over. @unique scalar fields produce one-to-one relations that stay collision-free.

What about implicit many-to-many relations?

Explicit join models work fully. Implicit many-to-many list fields (Category[] on both sides) don't generate the hidden join table yet — that's on the roadmap, and the docs say so honestly.

How do I load the result with Prisma?

Download SQL and load it with psql/mysql before running your app, or push directly to the database your datasource points at. The inserts come in FK order, so constraints stay enabled.

Is this a replacement for prisma db seed?

It complements it: prisma db seed runs your hand-written script, SeedBase generates the dataset so you don't have to write one — useful when the schema is large or non-TypeScript services share the database.

Two minutes to a fully populated database

Sign up, import your schema, generate. No sales call, no credit card — the free tier is enough for a real first impression.

  • FK-consistent
  • Realistic distributions
  • SQL / CSV / JSON
  • EU-hosted
Start free