BatesKit Reviews and Details

Questions & Answers

1. Which are the primary technologies used for building BatesKit?

   pdf-lib for PDF parsing and rewriting, pdfjs-dist for the render-based redaction and production-QA checks, tesseract.js for on-device OCR of scan bodies, React 19 + TypeScript + Vite on the client, WebCrypto Ed25519 for the offline licence, and Cloudflare Pages + Worker + D1 for static hosting and six anonymous counters.

2. What makes BatesKit unique?

   The entire PDF pipeline — parsing, numbering, writing and five production-QC checks — runs inside the browser tab. Files never leave the device, which for documents under a protective order is an eligibility requirement rather than a marketing feature. And it is checkable instead of promised: the only requests the page ever makes are six ~30-byte counters (page view, batch finished, check run finished, checkout opened, key verified, error type). Load it once, go offline, and a batch still runs.

3. Why should a person choose BatesKit over its competitors?

   Acrobat Pro's batch sequence does the numbering but is a subscription for one occasional task. Dedicated desktop Bates software works well and costs $99+, mostly Windows-only. Online PDF tools require uploading litigation documents, which disqualifies them for the sets that actually need numbering. BatesKit runs the whole job locally in any browser, one-time $19, no account. The honest cost is that it is a narrower tool than a processing platform — it numbers and checks, but does not redact or run a review environment.

4. Who are some of the biggest customers of BatesKit?

   None yet — the product is launching. There is no account system and no user data collected, so there is structurally no way for us to know who the customers are; that absence is itself part of the privacy design. The first honest conversion number will exist a week after launch.

5. How would you describe the primary audience of BatesKit?

   Paralegals and e-discovery staff who have to Bates-number production sets, small firms without an Acrobat subscription on every machine, and contract attorneys on laptops where privileged documents cannot be uploaded anywhere.

6. What's the story behind BatesKit?

   The chore is mechanical with non-mechanical stakes: numbering has to be continuous across every file, and the files are usually under a protective order, so "upload your folder to our server" is not an available answer. The existing options were a subscription, $99 Windows software, or an upload-based web tool. A browser can now do the whole job locally, so I built the one that assumes nothing leaves the device.