Case Studies

Production deployments of ALETHEIA

Real architectures, real numbers, real trade-offs — including where the API falls short for the use case. Each case study is reviewed and approved by the customer before it publishes; nothing here is invented and nothing here is a sanitized win.

Internal proving ground 2026-04-30 · consumer apps network

1,287 product safety profiles across 7 consumer apps, on one ALETHEIA integration

GeodesicNexus (operated by Holistic Quality LLC, the same team that builds ALETHEIA) runs 7 consumer-safety apps — baby, body, food, home, outdoor, pets, water — on a single production integration. Compound-as-shared-substrate architecture, regulator context next to claims, write-time cross-linking. We treat this as our public proving ground for the patterns we recommend to external customers.

1,287products

1,886compounds

~46 KBshared JS

4,492indexable pages

What we publish next (and why this section is empty for now)

Honest pipeline state, 2026-05-14. Third-party case-study outreach launched this week. We're targeting 2 published third-party case studies by end of Q3 2026 — one from the active-free-tier-user list, one from the compliance-guide-downloader list. We will not stand up placeholder cards for interviews that haven't happened yet. When a case study is real, it lands here.

Wave 1 outreach — active free-tier users
Wave 2 outreach — compliance-guide downloaders
First interviews scheduled
First draft in customer review
First third-party case study published

Already an ALETHEIA customer?

If your integration is in production and you'd be open to a 200-word quote plus permission to use your company name and logo, we offer 6 months of free Pro tier ($1,794 of usage) in exchange. The interview is 20 minutes by video; we draft the case study; you redline and approve everything before anything publishes. If the draft isn't right, the trade still holds — you keep the 6 months regardless.

Anonymized formats are fine ("Compliance Lead at a Fortune 500 retailer"). The only thing we won't do is make up names, numbers, or quotes — the value of this page is that everything on it is real.

Pitch your case study → Book a walkthrough first

What we look for in a case study

Our existing essays on why we built ALETHEIA and how it compares to PubChem and EPA CompTox include the "when not to use us" rows — that same honesty is the bar for the case studies we publish.

A real integration, in production. Not "we evaluated it." Live behind a real product or workflow that real users touch.
Concrete numbers. Volume, latency, time-to-integrate, or compliance surface covered. Even if the number is small, it's specific.
Trade-offs named. Where ALETHEIA falls short for your use case — what you wished it did and didn't. We publish that part too.
Reviewed by the customer. Two-round redline. Customer sign-off required before publish.
One technical detail we can cite. An endpoint, a payload shape, a number. Something other engineers can verify against their own context.

Adjacent reading

Why we built ALETHEIA — the essay-length argument for a curated synthesis layer over raw PubChem or CompTox.
ALETHEIA vs PubChem vs EPA CompTox — honest comparison including "when to use the other tool."
Marketplaces use case — the three-approaches framework (build / license / consensus API) most marketplace operators run into.
Use cases by persona — baby/pets/food/cosmetics/marketplace/research breakdown of what the API typically does in each.
Enterprise offerings — the six expansion paths beyond Pro tier (volume, on-prem, white-label, custom datasets, SLA, multi-region) for customers whose case study would be at Enterprise scale.