Schema in. Sealed dataset out.
Describe a dataset in one English sentence, get back a sealed synthetic CSV in under a minute.
With the contract, the seed, the cryptographic hash chain, and the same offline verifier as every other engine here. Same prompt, same seed: byte-for-byte equal across clusters, regions and years.
- Kind
- Mock Data
- Engine
- rapid_rrf
- Rows
- 40
- Seed
- 0x2A
- Contract Hash
- f9b9a4b4214198cb…
- Rows generated
- 100
- Artifacts
- 3
- Has output
- Yes
- Started
- 10:17:45 PM
- Completed
- 10:17:52 PM
- Duration
- 0m 7s
- Metered at
- 10:17:52 PM
| invoice_id | currency | grand_total | invoice_date | subtotal | tax | customer_id |
|---|---|---|---|---|---|---|
| 196 | USD | 0.00 | 2026-06-09 | 0.00 | 0.00 | 167 |
| 1288 | USD | 0.00 | 2026-06-11 | 0.00 | 0.00 | 432 |
| 1197 | USD | 40680.67 | 2026-07-02 | 37667.29 | 3013.38 | 167 |
| 926 | USD | 0.00 | 2026-06-07 | 0.00 | 0.00 | 918 |
| 1559 | USD | 2322.39 | 2026-06-11 | 2150.36 | 172.03 | 922 |
Six promises Mock Data keeps every time.
These aren't configuration toggles — they're how the engine was built. The engine simply behaves this way for every prompt, every tenant, every run.
Sub-minute, every time
Built for latency, not training. Most prompts complete in 20–60 s for up to 200 k rows — including evidence sealing — so it fits inside an interactive UX or a CI step. (The run pictured above sealed in 7 s.)
Deterministic by construction
Same prompt + same seed + same engine version = byte-equal output. CI re-runs 47 reference contracts and checks every cell against a stored hash; if one byte drifts, the build fails.
Any industry, on demand
Mock is LLM-driven schema fabrication, not a fixed template list. Describe a bank, an EHR cohort, a smart-meter feed, a retail basket — an LLM drafts a domain-aware sealed contract, and you can override any field per prompt.
Same evidence chain as the rest
Mock outputs join the same cryptographic hash-chained ledger as Synthesize, Virtual SCADA and ICS Security. The bundle is structurally identical — your downstream tooling treats them the same.
Two surfaces, one engine
Use the rady CLI for shell pipelines and one-off ops, or call client.mock(...) from the typed Python SDK. Same compiler, same contract; the audit log records who called it and from where.
Quality fail-closed
Even on the fast path we check distribution sanity, range bounds, enum compliance and nullability against the contract before sealing. A regression aborts — you never receive a quietly-broken dataset.
From a sentence to a sealed bundle in six stages.
Each stage writes a typed artefact into the chain. Even the prompt joins the audit trail — so an auditor can trace any byte back to the operator who asked for it.
One English sentence, an inline JSON schema, or a referenced YAML template. The compiler accepts all three and normalises to a sealed contract.
Schema, ranges, enums, constraints, seed, engine version and operator intent are sealed into one artefact before any row exists. Its hash is the dataset's identity.
The fabricator emits rows deterministically from the sealed contract — sampling rules, range/enum constraints and correlations. Row generation makes no external model call.
Distribution sanity, range bounds, enum compliance, nullability and constraint satisfaction are checked. Fail-closed — a mismatch aborts before sealing.
Per-step I/O hashed and chained; the final bundle is signed and ready to verify offline with the verifier CLI.
A .tar.zst lands on disk, in S3, in your tenant prefix, or as a stream. Re-run the contract anywhere and the dataset hash matches.
$ rady mock \
--prompt "200 SaaS customers, MRR 50-5000, plan
Starter/Growth/Enterprise, region AMER/EMEA/APAC" \
--rows 200 --seed 42 --output ./customers.csv
Mock · 200 rows · seed=42
✓ Sealed contract 9c10ab24 created
✓ Job e2f91b37 submitted (200 rows, seed=42)
✓ Wrote 23,487 bytes to ./customers.csv
→ verify offline: rady jobs evidence e2f91b37Same contract from the CLI or the typed Python SDK — client.mock(...).
Not just another faker with a UI.
Most 'mock data' tools are shell scripts behind a SaaS skin. RadMah treats every output as evidence — sealed, hashed, replayable and auditable on the same chain as the rest of the platform. No competitor is named; this is the honest category picture.
Four patterns teams use every week.
None require touching production data; all produce a bundle you can hand to anyone in the business.
Sandbox / demo data
A realistic demo environment for sales, CS or training without touching production. Re-seed in 30 seconds for a fresh run.
Load & soak testing
Millions of rows that pass your validation but exercise edge ranges your real data doesn't carry. Seed-pinned, so failures reproduce.
Test fixtures in CI
Drop rady mock into CI to generate fixtures per branch. The contract is in git; the bundle isn't — it rebuilds byte-equal on demand.
Rapid prototyping
Prototype a dashboard, an ML model or an API contract against data shaped like the real thing — before legal even joins the call.
This dataset was generated from the approved Contract K. The version chain below records every refinement the user applied.
Sealed, and yours to verify.
Every Mock run ships the same audit trail: a hash match proving the dataset is reproducible, the constraint checks, and the contract fingerprint. Four guarantees apply by default — none are paid add-ons.
- Tenant-isolated
Per-tenant keys at rest, per-tenant artefact prefix, ORM-level row filtering.
- Deterministic generation
Rows are generated deterministically from the sealed contract — no external model call at generation time.
- Tamper-evident
The offline verifier flags any in-place mutation of the bundle, however it travelled.
- Audit-ready
Caller, scope, contract hash and bundle root recorded on every call.
Bring a sentence. We’ll ship a sealed bundle.
A 30-minute working session: tell us the dataset shape you need and one downstream task you want to drive with it. We cut the contract, generate the bundle, and walk you through verifying it offline.
Mock Data is the fastest path from “I need a realistic-looking dataset for a demo, an integration test, or a pitch deck” to a sealed file you can hand a teammate. No database, no ETL, no warehouse ticket. A PM writes the prompt in English; the fabricator returns a deterministic CSV plus a bundle anyone can verify offline.
The prompt is parsed into a contract (columns, dtypes, cardinalities, business rules), the contract is sealed, and a domain-aware fabricator emits rows under a fixed seed. Re-run the same prompt with the same seed a year later and the output is byte-equal. CLI path:rady mock generate.