Hey everyone, I am an Indie developer and I built SeedQL. Every team I've worked on had the same two problems with test data: volume and integrity. You either had a seed script with twenty hand-written rows that looked nothing like production, or a faker script that fell apart the moment two tables were linked by a foreign key. Both end with someone copying real customer data into staging, which is the outcome nobody wants. SeedQL introspects your actual schema, builds the dependency graph between tables, and generates rows in an order where every insert succeeds. Five thousand rows or five hundred thousand, the integrity holds. Big jobs run on a durable queue so nothing times out halfway through. Two things I care about as the only person on this: Your data stays yours. Generated rows stream into your database and are never stored on my servers. There's no VC and no checkout page. The free tier is free permanently. Bigger quotas are unlocked by supporting the project on Buy Me a Coffee. I honestly don't know yet whether patronage can fund a developer tool, but I'd rather run the experiment than sell ads or your data. PostgreSQL works today. MySQL and SQLite are next, and the engine was built adapter-first so adding them is the plan, not a rewrite. I'll be here all day. Ask me anything about the dependency-graph generation, the security model, or the funding experiment.

SeedQL

Schema-aware test data that actually feeds your Dev Tools

Schema-aware test data that actually feeds your Dev Tools