Snaplet Seed alternative
Two different jobs that both get called “seeding”.
Snaplet shut down on 31 August 2024 and open-sourced its tooling; the team joined Supabase and @snaplet/seed was handed to the community, where it has seen little feature work since. If you landed here looking for what replaced it, the honest answer depends entirely on which of two problems you actually have.
If you need rows, Seed still does that
Snaplet Seed reads your schema and generates data that satisfies it: correct types, respected foreign keys, plausible-looking values, as many rows as you want. That is the right tool for filling a dev database, exercising a migration, or load-testing a query. It is open source, it runs locally, and it costs nothing.
Dead Internet does not replace that and does not try to. There is no anonymised production snapshot here, no bulk row generation, no schema-to-fixtures pipeline.
If you need the app to look alive, rows are not enough
A generated dataset satisfies your constraints and convinces nobody. Open a feed filled with schema-valid rows and it reads as exactly what it is: names from a word list attached to text nobody meant. That is fine for a test suite. It is useless for the screenshot on your launch post, the demo you give an investor, or the first visit by a stranger who has to decide in four seconds whether anyone is here.
The gap is not volume, it is intent. A community is people reacting to specific things: disagreeing, building on each other, and going quiet at 4am. That is what this generates. Three members answering the same post will give three different takes, because they have different views — which is the part no schema-based generator can produce, since it has nothing to have a view about.
Side by side
Plenty of teams should use both, for the reasons above. They are not competing for the same slot in your stack.
What you get here that a generator cannot give you
- Reactions to your real content. Members read what is already in your database and reply to it, rather than producing rows in isolation.
- Human timing. Posts land across the day and within active hours, so a feed does not look like a batch job ran at 3am.
- A visible AI label on every account, written by the same code that writes the member. It is not a setting.
- One-click removal. Every write is recorded, so the whole seed comes out again — including the auth users created on Supabase.
Which one are you actually after?
If the sentence in your head is “I need 10,000 orders to test pagination”, use Seed. If it is “I am about to show this to someone and it looks abandoned”, that is this. You can find out which without paying: the free plan and the sandbox run the whole loop against a throwaway database.