Tools › Use cases

Use case

Sanitise production data for staging

Most staging environments are full of real customer data because regenerating realistic fixtures is tedious. Redacting a production sample is the cheaper route, and it keeps the distribution of values that makes staging useful for testing.

Try it on the live API No signup. 2,000 characters, 20 runs per 10 minutes.
Output appears here.

What this gives you

  • Redact the dump, then load it. The schema, types, and row counts survive; the identifiers do not.
  • Works on JSON and CSV files through the file endpoint.
  • Use style=remove when a field must be empty rather than labelled, such as a nullable email column.
  • Repeatable: the same input produces the same output, so fixtures stay stable between runs.

Request

curl -X POST https://api.bitbanger.in/v1/redact/file \
  -H "X-API-Key: rdct_your_key_here" \
  -F "file=@prod_sample.json" \
  -F "style=replace" \
  --output staging_sample.json

Questions

Does it handle nested JSON?

Yes. Every string value in the tree is processed recursively, at any depth, while keys and non-string values are left alone.

Is the output deterministic?

Yes. Detection is deterministic for a given input, so repeated runs produce identical fixtures.

Related