An objective directory for public U.S. clinical trial records.
This website helps English-speaking U.S. users search and browse public clinical trial records from ClinicalTrials.gov without recommendation language, medical interpretation, or eligibility judgments.
What the site does
Search by condition, location, sponsor, intervention, recruitment status, phase, study type, sex, age, or NCT ID.
Display objective public record fields such as status, phase, study type, sponsor, interventions, age range, sex, location count, and last updated date.
Link each result to the official ClinicalTrials.gov study record.
What the site does not do
No medical advice. No treatment recommendations. No eligibility checker. No credibility score. No “best trial” or “likely qualify” labels.
No AI-generated medical summaries, patient stories, or subjective interpretation of trial quality or risk.
No collection of user medical history for the directory experience.
Data and sync model
Data is sourced from official ClinicalTrials.gov public API records. Always review the official ClinicalTrials.gov record for the latest information.
The implementation is designed for Astro + TypeScript on Cloudflare Workers, with D1 for structured trial records, optional KV caches when enabled, R2 for raw API snapshots plus generated sitemap files, and scheduled sync jobs for refreshes.
Saved search email alerts are limited to new matching public records entering the local index and do not provide medical recommendations or eligibility determinations.
This site is an independent directory and is not affiliated with ClinicalTrials.gov, NIH, NLM, FDA, study sponsors, hospitals, or investigators.
How search and storage work
Does the site store trial data? Yes. The site stores objective public fields from ClinicalTrials.gov in Cloudflare D1. It does not store user medical history for the directory experience.
Is search live or cached? Search is hybrid. The live ClinicalTrials.gov API is the primary source for result lists, and normalized public fields are synchronized into D1 for local indexing and browse-page summaries.
What are KV and R2 used for? KV can be used for optional search and aggregate caches when enabled. R2 stores raw API snapshots and generated sitemap files.