Alternative · target: mockaroo alternative

Mockaroo Alternative for Customer records API Seed Data

User wants a local or CLI-based mockaroo replacement without uploading their schema.

Direct answer

SchemaSeed reads the Customer records API schema and writes loadable rows; Mockaroo generates values for one document, with no SQL and no invalid instances. The gap appears with cross-table references.

That gap only matters once the fixture has two or more tables that reference each other, or once a test suite must assert the API rejects malformed input; for one flat schema Mockaroo is usually sufficient.

The same Customer records API schema run through Mockaroo yields a JSON document whose child rows reference values that match no parent row; the reference engine rejected that shape with "CHECK constraint failed: length(country) = 2".

Data as of 2026-11-18 · source: 1 Stack Overflow questions, @linked365/pptb-mockaroo-data-munger at 842 monthly downloads · negative-case messages reproduced by executing the fixture against a local SQL engine (Node.js v24.22.0, engine 3.53.4) at 2026-11-18T11:53:54.233Z

What the incumbent does well — Customer records

Mockaroo is a mature tool and it is not going away. For a single flat schema it produces valid JSON faster than anything else, and its API surface is small enough to learn in an afternoon. If your Customer records API fixture is one table with no cross-table references, the honest answer is that Mockaroo is enough and this page will not change your mind.

The gap that matters for relational seeds

The gap appears the moment the fixture stops being one table. Mockaroo reads one schema and produces one document; it has no second schema to read, so it cannot know that the child table needs a parent row. The result is values that are individually plausible and collectively unloadable. The reference engine rejected exactly that shape with "CHECK constraint failed: length(country) = 2".

Side by side on the same fixture

The table below scores the two approaches against the identical Customer records API fixture. The rows are not opinions about architecture; each one is a property of the fixture that the reference engine can verify. The decisive row is the foreign key row, because a JSON document can carry a dangling reference without any tool complaining until the moment it is loaded.

Migrating an existing fixture

You do not have to rewrite your fixture. Keep the schema file, run the generator against it, and diff the output against the rows you already have. For Customer records API the diff is usually small: 1 tables, and the changes are the constrained columns, which are the ones a hand-written seed gets wrong most often. The negative case set is additive, so nothing you already depend on is lost.

How to decide in under a minute

Two questions decide it. Does your schema have more than one table that reference each other? Does your test suite need to prove the API rejects malformed input? If both answers are no, stay on Mockaroo. If either is yes, the missing piece is the same in both cases: a generator that reads the whole document and treats the constraints as part of the contract rather than as decoration.

SchemaSeed vs Mockaroo on the Customer records API fixtureEight criteria, each decided by a property of the fixture rather than by preference. The left column is what a schema-to-SQL generator does with it; the right column is what document generation leaves unresolved.
CriterionSchemaSeedMockarooWhat decided it
Reads a multi-file OpenAPI documentyesyesboth resolve local $ref chains
Honours NOT NULLyespartialboth read the required array
Honours enum, range and length declarationsyespartialthe fixture declares customers.country with char_length("country") = 2; the declaration is read out of the schema, the DDL carries it as a CHECK constraint and the value that breaks it ships as a negative case
Honours enum membersyesyesthe enum array is copied verbatim
Produces SQL, not just JSONyesnooutput format is the difference
Resolves foreign keys across schemasyesnoa single-schema faker has no second schema to read
Emits deliberately invalid instancesyesnonegative cases are a separate output
Same seed produces the same bytesyesyesboth are seedable
Real constraint failures for the Customer records API fixtureReproduced by executing the fixture against a local SQL engine (Node.js v24.22.0, engine 3.53.4) on 2026-11-18T11:53:54.233Z. The message column is verbatim engine output; the SQLSTATE column is the PostgreSQL error class for the same constraint class.
Failure classColumnSQLSTATEError nameEngine message (verbatim)
Missing required fieldcustomers.first_name23502not_null_violationNOT NULL constraint failed: customers.first_name
Out-of-contract valuecustomers.country23514check_violationCHECK constraint failed: length(country) = 2
The four checks that decide whether a schema tool is enough for Customer records APIApplied to Customer records API.
CheckResult on this fixtureConsequence
More than one table references anothernoa per-schema faker is sufficient
Output has to be SQL, not JSONyes — the target is PostgreSQLa document generator produces the wrong artefact
Tests must assert the API rejects bad inputyes — a negative case for every declaration in the schemanegative instances have to be generated separately
Same seed must reproduce the same bytesyes — seed 42 is fixedfixtures can be committed and diffed
mockaroo_crm.openapi.yaml

npx --yes @wenlu8848/schemaseed validate --input ./mockaroo_crm.openapi.yaml

Download mockaroo_crm.openapi.yaml

openapi: "3.0.3"
info:
  title: "Customer records API"
  version: "1.0.0"
  description: "The whole fixture is one table, so the only interesting constraint is the unique email. The country check constraint rejects full country names, which hosted generators often produce. A hosted generator sends the schema definition off the machine, which is the point of comparison on this page. The signup_date column is a timestamp and must be written in a form Postgres accepts without an explicit cast."
paths: {}
x-domain-id: "mockaroo_crm"
x-dialect: "postgres"
components:
  schemas:
    customers:
      type: "object"
      x-primary-key: "id"
      required: ["id", "first_name", "last_name", "email", "country", "signup_date"]
      properties:
        id:
          type: "string"
          format: "uuid"
        first_name:
          type: "string"
        last_name:
          type: "string"
        email:
          type: "string"
          format: "email"
          x-unique: true
        country:
          type: "string"
          minLength: 2
          maxLength: 2
        signup_date:
          type: "string"
          format: "date-time"

Frequently asked questions

Is Mockaroo still worth using?
For one flat schema, yes. The gap opens on Customer records API: Mockaroo produces values for a single schema, while this fixture has 1 related tables that have to load together.
Can I keep the fixtures I already wrote?
Yes. Regenerate against the same Customer records API schema and diff. On this fixture only the constrained columns move, and the negative cases are additive.
Does SchemaSeed replace Mockaroo entirely?
No. It is a different artefact: Mockaroo produces values for one schema, SchemaSeed produces JSON fixture files plus invalid instances for 1 related tables.
Is there a paid version?
No. The CLI is MIT licensed and free: unlimited local generation, no account, no telemetry and no usage limit, and it runs on your own machine. Sponsorship is what keeps it maintained.

Run it against your own schema

SchemaSeed is MIT licensed and free: unlimited local generation, no account, no telemetry and no usage limit. It reads your schema file on your own machine, so nothing is uploaded anywhere. If it saves you time, you can support the project.

Get SchemaSeed — free Support the project

Questions: support@schemaseed.drz8848.win