Postgres seed data, for your framework
Every framework has its own seeding ceremony — seed scripts, factories, fixtures. The schema underneath is the same. Generate FK-intact, distribution-true Postgres data for the framework you already use, without maintaining generator config.
Prisma seed data
Seed a Prisma + PostgreSQL app with FK-intact synthetic data — prisma migrate deploy, then one command. No seed.ts drift.
Prisma guide →
Drizzle seed data
Seed a Drizzle + PostgreSQL app with realistic rows — drizzle-kit push, then one command. Foreign keys resolve themselves.
Drizzle guide →
TypeORM seed data
TypeORM + PostgreSQL test data without writing entity factories. The schema drives generation.
TypeORM guide →
Django seed data
PostgreSQL test data for Django projects — beyond fixtures and factory_boy, with FK integrity by construction.
Django guide →
Rails seed data
Rails + PostgreSQL test data without maintaining db/seeds.rb — schema-driven generation that never drifts.
Rails guide →
Laravel seed data
Laravel + PostgreSQL test data beyond DatabaseSeeder and factories — distributions and FKs from the schema itself.
Laravel guide →
How it works, once
Every framework guide follows the same loop: migrate or push your schema, point Weavori at the database, generate. Foreign keys resolve in dependency order, distributions come from pg_stats, and there is nothing to maintain when the schema changes. The Postgres test data guide explains the approach; the framework pages show it in your stack.