Deniable

About Deniable

Build your tests around the cases that matter.

Deniable is a focused library of pre-generated synthetic documents for AI systems, software, and workflow testing. We make difficult inputs easier to inspect without putting production data into the test loop.

Browse datasetsContact Deniable
Deniable

Why Deniable exists

A practical middle ground for test data.

The useful question is not whether data is synthetic or real. It is whether the input exposes the behaviour your system needs to handle, and whether your team can inspect that behaviour safely and repeatably.

The reason

Production data is the wrong place to discover basic test gaps.

Real records carry privacy, access, and operational constraints. At the other extreme, tidy fixtures can make a workflow look reliable while leaving missing context, conflicting details, and unusual structure untested.

The approach

Pre-generated cases with a clear testing job.

Deniable organises synthetic documents around the behaviour a team wants to inspect. Packs are prepared in advance, documented by category and format, and made for repeatable runs rather than on-demand generation.

The human part

Automation helps produce the material. People define what matters.

Every Deniable pack combines human input with creative scenario design. That involvement gives each case a reason to exist and keeps the collection focused on useful variation instead of random noise.

The boundary

Useful test data should be clear about what it is not.

Deniable documents are synthetic. They are not customer records, legal advice, financial records, or a promise that a test suite represents every production situation. The catalogue describes the scope of each release so teams can decide where it fits.

Why I built it

I built Deniable after my own parser hit the wall.

I built my own email parser and quickly ran into a practical problem: there was no straightforward place to buy realistic, edge-case-heavy email and document test data. The options I found were mostly enterprise-grade systems or tools that expected teams to generate and maintain everything themselves.

Deniable is the simpler route. Choose a fixed pack, use the files or the API, and spend your time testing the product instead of assembling another data pipeline. I dislike subscriptions for one-off work, so the model is built around fixed packages and prepaid API credits rather than a monthly commitment — designed as something I would buy myself.

We run a controlled local generation workflow for tighter data control and predictable production costs. Enterprise-scale cloud token usage would make this work slower and more expensive for everyone, so Deniable packages the finished, reviewed material instead. The hard part is the complete workflow around it: deciding which failure modes matter, shaping the context, reviewing the result, handling multiple formats, and packaging everything for repeatable use.

Where it fits

One library, more than one testing job.

The same synthetic documents can support different teams. The right use depends on the workflow, the release contents, and the question you need to answer.

Machine-learning teams

NLP training and evaluation for sentiment, intent, entities, clustering, and classification.

Conversational-AI developers

Dialogue context, interruptions, slang, and response workflows without real conversations.

RAG and LLM evaluation

Retrieval, grounding, citations, and long-context behaviour across structured documents.

Email and anti-spam developers

EML parsing, headers, threading, encoding, and unusual message structure.

CRM and support software

Ticket flows, routing, priorities, automations, and support dashboards.

Data and BI teams

Text aggregation, topic analysis, sentiment trends, and reporting pipelines.

Privacy and compliance teams

Safe synthetic patterns for reviewing redaction, masking, and sensitive-field handling.

Load and performance testing

Repeatable document volumes for stress runs when the selected release supports that scale.

Education and research

Clear, repeatable material for NLP, data science, and software-testing exercises.

Marketing and text-analysis tools

Controlled reviews and social-style text for themes, sentiment, and trend workflows.

How we work

Make the difficult input inspectable.

01

Start with a testing question

A case begins with a behaviour to inspect: retrieval, extraction, classification, routing, summarisation, or a workflow boundary.

02

Shape the variation

Human input and creative scenario design establish the context, conflict, omissions, and format changes that make the case useful.

03

Keep the release reviewable

Each published pack is described by its category, included formats, language, package tier, and verified document count when available.

Dataset packs

Get the complete case set.

Fixed dataset packs for teams that want a ready-to-download collection.

Browse datasets

API credits

Retrieve cases in your workflow.

Retrieve pre-generated cases as JSON with prepaid credits. No monthly subscription, and no generation pipeline to maintain.

BUY API CREDITS