Compound intelligence for the substances hiding in plain sight.
Search peptides, supplements, skincare drugs, aesthetic injectables, research chemicals, and edge-case compounds with evidence grading, split risk scores, and context that does not read like marketing.
StackTrack Today
Your stack is locked in.
Keep peptides, supplements, hydration, and recovery aids on the same disciplined schedule as your training.
Training-Day Log
Stack Protocol Notes
Research desk
A research-grade index for compounds, claims, and risk signals.
Built for evidence review, not hype. Each profile separates what people claim, what is documented, what is unknown, and where the sourcing or regulatory risk starts.
Compound Search
0 resultsEffects explorer
Search the outcome first, then compare evidence, compound risk, and sourcing risk.
Discovery mode for goals like fat loss, hair retention, skin quality, tanning, recovery, inflammation, sleep, and body composition without pretending every compound belongs in every bucket.
Effect Results
0 resultsForum preview
A community for logs, questions, and evidence checks.
The future forum should reward receipts: citations, lab context, adverse-event reporting, and before/after tracking without turning the site into a sourcing or dosing board.
Library ops
Build, review, and publish compound profiles.
Draft entries locally, import spreadsheet rows, export clean JSON, and publish to Supabase when your signed-in account has admin access.
Why this exists
People make safer decisions when the truth is easier to find than hype.
BioStackr is built around the idea that education should show the full picture: potential positives, potential negatives, unknowns, legal context, and quality-control issues. The goal is not to glamorize or scare people. The goal is to make clear information easier to find.
Library engine
Start manual, migrate cleanly to a real database.
The profiles are structured like database records already. That means we can curate entries by hand now, then move them into SQLite, Supabase, Postgres, or a headless CMS when the library gets large.
Fastest Way To Build The Huge Library
- Start with a spreadsheet or CSV template so adding compounds is as easy as filling rows.
- Import that file into a local JSON database during development.
- Review every new entry in an admin queue before it goes public.
- Move the same schema into Supabase/Postgres when search, accounts, and moderation matter.
Core Fields We Should Keep Stable
- Name, aliases, class, audiences, targets, and tags.
- Claimed positives, negatives, contraindications, and unknowns.
- Compound risk, sourcing risk, evidence grade, approval status, and citations.
- Structure image, PubChem query, admin notes, last reviewed date, and version history.