We build custom training corpora from public web data — product catalogs, reviews, Q&A, domain text — prepared to training grade: near-duplicate deduplication with reported rates, PII scrubbed at collection, consistent JSONL schemas, and per-source provenance documentation aligned with the EU AI Act's training-data transparency requirements (applicable to general-purpose AI since August 2025). You specify domain, languages and volume; we deliver the corpus plus the paperwork your legal and diligence reviews will ask for.
The difference between a crawl dump and a training corpus is everything that happens after the crawl: deduplication (the web repeats itself relentlessly), PII removal (reviews leak names and emails), schema discipline (batch 47 must match batch 1), and — since the EU AI Act's GPAI obligations took effect in August 2025 — documentation of where every source came from. Our AI-ready data checklist covers the full standard.
We deliver against that standard by default. One AI client closed an investor diligence question with exactly this paperwork — 38M documented records, provenance included. The corpus you can defend is the only corpus worth training on.
Commerce, food, travel, real estate, local business — corpora scoped to your model's actual job, not generic web text.
MinHash-class fuzzy deduplication with the rate in your delivery report — you see how noisy the source was.
Names, handles, emails, phones removed in the pipeline — personal data never enters the deliverable.
Domain, collection window, method and access basis per source — the inputs your AI Act training-data summary needs.
Clean JSONL shards, declared splits, schema docs and datasheets — load and go.
Beyond raw text: structured pairs (product Q&A, attribute extraction targets) built to your spec for fine-tuning.
Real sample structure from this feed. Your free 48-hour sample comes in your category, in this shape — CSV, JSON or straight to your warehouse.
| field | value |
|---|---|
| text | Product: Cotton kurta. Fabric is breathable and... |
| source_domain | example-marketplace.com |
| collected_at | 2026-05-14 |
| lang | en |
| pii_scrubbed | true |
| dedup_cluster | c_88421 |
| license_basis | public |
{
"text": "Product: Cotton kurta. Fabric is breathable and...",
"source_domain": "example-marketplace.com",
"collected_at": "2026-05-14",
"lang": "en",
"pii_scrubbed": "true",
"dedup_cluster": "c_88421",
"license_basis": "public"
}
| VOLUME | From ~1M to 100M+ records per corpus; sampled pilots available |
| FORMATS | JSONL/Parquet shards · datasheet + schema docs · dedup & provenance reports |
| LANGUAGES | English-first; major European and Indian languages on request |
| REFRESH | One-time corpora, versioned refreshes, or continuous additions |
| TIMELINE | Documented pilot sample in ~1 week · full corpus 2–6 weeks by volume |
| PRICING | Per-corpus, by volume × preparation depth; pilots priced separately |
| COMPLIANCE | Public data only · TDM opt-outs respected · PII-scrubbed · EU AI Act-aligned docs · NDA-first |
Every engagement is NDA-first and starts with a free sample — judge the data before any commitment.
| In-house DIY | Generic SaaS tool | iWeb Data Scraping | |
|---|---|---|---|
| Setup & maintenance | You build scrapers, fight anti-bot, fix breakages weekly | Rigid templates, breaks on site changes, slow support | Fully managed — we build, monitor and fix, you never touch a proxy |
| Data quality | Best-effort, no QA layer, silent failures | Generic parsers, frequent gaps | 99%+ field accuracy, QA-verified, monitored 24/7 |
| Coverage | Limited to what you can maintain | Only supported sites | Any public site or app, at scale |
| Compliance | Your legal risk to manage alone | Often opaque about methods | ISO-certified, PII-scrubbed, NDA-first, documented |
| Time to value | Weeks to months of engineering | Fast but inflexible | Free sample in 48h, production in days |
Commerce-domain corpora that teach the model your vertical's vocabulary, attributes and edge cases.
Provenance documentation that answers 'where did this come from?' per source, in writing.
The training-data question is now standard in AI diligence — arrive with the datasheet, like this client did.
Every delivery includes a datasheet (scope, collection windows, methods), per-source provenance (domain, window, access basis), the deduplication report (method and rate), the PII policy applied, and schema documentation — the artifact set that EU AI Act training-data summaries and enterprise diligence reviews draw on.
We collect public data, respect text-and-data-mining opt-out signals for corpus work, and bias corpora toward factual and structural content (catalogs, attributes, Q&A) over long-form creative expression. Per-engagement scoping documents the approach so your counsel reviews a method, not a mystery.
Yes — structured pairs are a standard request: product Q&A, attribute-extraction targets, review-summarization pairs and similar formats built to your task spec, with the same dedup, PII and provenance treatment as raw corpora.
Pilots start small deliberately: a documented sample (typically tens of thousands of records) in about a week, so your team can evaluate quality, run ablations and test the paperwork before committing to full volume.