The story
Mocktopus started as a frustration. Every project I worked on hit the same wall: thousands of lines of hand-written JSON fixtures, drifting from the real schema, silently breaking tests, and consuming engineering time that should have gone into shipping features. Generic data generators made it worse — they produced records that were structurally valid but semantically incoherent. An Order with a customerId that pointed at nothing. An Invoice whose total had no relationship to its line items. Data that lied.
The fix had to start at the domain model. Not the API schema, not the database — the domain itself: the entities your business operates on, the value objects that describe them, and the events that record what happens. Once the domain is captured in a form tooling can reason about, mock data stops being an artisanal craft and becomes a mechanical output.
The vision
Mocktopus is a domain-driven mock generation platform. You define your business domain visually, publish a versioned snapshot, and generate realistic, relationally coherent mock datasets — referential integrity intact, constraints satisfied, edge cases included. Your fixtures stop being hand-written. Your tests stop lying. Your team stops blocking on a stale schema.
V1 is free. No record limits, no entity limits, no seat limits. The goal is adoption, not revenue. If Mocktopus saves your team a day a sprint, the project is working.
Who builds it
Mocktopus is built by a small team led by a working backend engineer. We use the product on real domain models with real complexity — that is the only way to know if it earns its place in your toolchain. If you have feedback, the support page is the fastest way to reach us.