Prisma seed data and test data, FK-consistent, straight from your schema.prisma.

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.

model Post {
  id       Int  @id @default(autoincrement())
  author   User @relation(fields: [authorId], references: [id])
  authorId Int
}

# → INSERT INTO "user" ... then "post" , 
#   author_id resolves (declared FK), 1-10 posts per user

What you get

Prisma seed data with prisma db seed and seedPrisma()

This is the closest thing to a hand-written seed script: a prisma/seed.ts that lives in your repo and runs through prisma db seed. Install the SDK with npm install @seedbase/client, then call seedPrisma(). Your migrations still own the schema, SeedBase only fills it with FK-consistent rows in dependency order.

// prisma/seed.ts
import { PrismaClient } from "@prisma/client";
import { SeedbaseClient } from "@seedbase/client";
import { seedPrisma } from "@seedbase/client/prisma";

const prisma = new PrismaClient();
const client = new SeedbaseClient({ token: process.env.SEEDBASE_TOKEN });

// FK-consistent rows, inserted in dependency order
await seedPrisma(prisma, client, {
  project: process.env.SEEDBASE_PROJECT,
  seed: 42,
});

Register the script under the prisma.seed key in package.json, then run the seed:

// package.json
{
  "prisma": { "seed": "tsx prisma/seed.ts" }
}

npx prisma db seed

The token is a free API key (it looks like dr_sk_...) from Settings, API keys. Same seed: 42, same rows, every run, so local and CI databases match.

In-memory Prisma test data fixtures with seededRows()

Want the rows for a test fixture or factory instead of a direct insert? client.seededRows(project, { seed, rows }) generates the dataset and returns it as a plain object keyed by table name, already in foreign-key-safe order, so a parent row exists before any child that references it.

import { SeedbaseClient } from "@seedbase/client";

const client = new SeedbaseClient({ token: process.env.SEEDBASE_TOKEN });

const rows = await client.seededRows(projectId, { seed: 42, rows: 100 });
// { user: [...], post: [...], comment: [...] }  // FK-safe order

for (const post of rows.post) {
  // post.authorId points at a user in rows.user
}

No database connection needed for this path: it is deterministic JSON you can feed straight into Vitest, Jest or a Prisma factory. Pass rows to scale the row count per table.

A SQL file for CI: generate() and download()

For a pipeline that loads SQL before the test suite, trigger a generation and download the artifact. client.generate(project, { seed: 42, wait: true }) polls until the generation finishes, then client.download(gen.id, { format: 'sql' }) returns the bytes.

// seed-sql.mjs, run in CI
import { SeedbaseClient } from "@seedbase/client";
import { writeFile } from "node:fs/promises";

const client = new SeedbaseClient({ token: process.env.SEEDBASE_TOKEN });
const gen = await client.generate(process.env.SEEDBASE_PROJECT, { seed: 42, wait: true });
await writeFile("seed.sql", await client.download(gen.id, { format: "sql" }));

# .github/workflows/test.yml
- run: node seed-sql.mjs
- run: psql "$DATABASE_URL" -f seed.sql

The inserts come out in FK order, so the file loads into a constrained schema with foreign keys enabled. Because the data is keyed off the seed, a failing test reproduces locally with the same seed: 42. The same flow covers raw SQL test data and Django test data projects.

Coming from @snaplet/seed and createSeedClient?

If you ran the @snaplet/seed workflow with createSeedClient(), this is the maintained equivalent: seedPrisma() for the prisma db seed step, or seededRows() when you want rows in memory. SeedBase reads the same schema.prisma, so the move is a few steps, not a rewrite, and your schema does not change. The full walkthrough is on the Snaplet Seed alternative page.