Reads any schema
Postgres, MySQL, SQLite. It introspects columns, types, constraints and foreign keys — your migrations are the only source of truth it needs.
Every row in your dev database says test test test — so every bug that only appears with real names, real unicode and real nulls waits until production to introduce itself. DemoKit reads your schema and fills it with data that behaves like the real thing. One command, no fixtures to maintain.
You've done it before. A seeds.ts, a faker import, a free afternoon. Here's where the afternoon goes:
DemoKit is demokit seed. Four seconds, and it re-reads the schema itself.
Point it at a database URL. It introspects the tables and fills them — no config file, no fixtures, no ORM plugin.
Postgres, MySQL, SQLite. It introspects columns, types, constraints and foreign keys — your migrations are the only source of truth it needs.
Real names, addresses, unicode, plausible nulls, emails that are valid but safe to send nowhere. The edge cases that only bite in production show up on your laptop instead.
Every foreign key points at a row that exists. Join tables fill in the right order. --rows 100000 stays consistent all the way down.
--seed 42 gives everyone on the team the same database. Reproduce a bug from a coworker's exact row instead of a screenshot of it.
demokit seed with no flags does the obvious thing. Flags are there for the day you need them, not a tax you pay on day one.
It refuses any connection string that matches your PRODUCTION_URL or smells like one. The safety is on by default; you never have to remember to turn it on.
Found a unicode truncation bug in our billing-name column that had been in prod for months. It showed up the first time I seeded with real data.
Deleted 2,000 lines of factory code. CI dropped by 40 seconds and I stopped thinking about seed data entirely.
Onboarding a new dev used to mean a day of 'why is my local database empty'. Now it's one command in the README.
No subscription, no seats to count on the honour system. Buy it once, update it forever.
One developer, every project you ship.
one-time
Your whole team, one invoice.
one-time
Postgres, MySQL and SQLite today. Mongo and SQL Server are next. If yours isn't listed, reply to your receipt — refunds are open for 30 days and I'd rather you had your money than a tool that doesn't fit.
No. DemoKit refuses any connection string that matches your PRODUCTION_URL env var or pattern-matches a managed-host URL. Overriding that takes a flag you'll never type by accident.
Those hand you a library — you still write the inserts, wire the foreign keys, and keep it all in sync with the schema. DemoKit reads the schema and does that wiring for you. It uses a Faker-grade generator underneath; the work it saves is the plumbing around it.
Every future version, free, forever, for one payment. No renewal, no upgrade pricing. If DemoKit gets more expensive later, you still paid once.
Solo covers one developer on unlimited projects, personal and commercial. Team covers up to 20. You can't resell DemoKit itself — but anything you build with the data it generates is yours.
Thirty days, no questions, one reply to your receipt. See the guarantee below — it's the whole policy, not a link to a policy.
If DemoKit doesn't save you an afternoon in the first week, reply to your receipt and I'll refund you in full — and you keep the download. No form, no 'reason for return', no support-ticket maze. I'd rather have your trust than your $39.