Stack Compatibility Guide
$27.00 USD
Stack Compatibility Guide
$27.00 USD
Most researchers running multiple compounds are asking the wrong question. The question is not what else to add. The question is whether what you are already running is creating interference.
The Stack Compatibility Guide covers the four categories every compound combination falls into. Each one is defined by mechanism, meaning how a compound actually works at the receptor level, not by its name or how commonly it is discussed. Understanding which category a combination sits in before making a protocol change is the difference between adding leverage and adding cost.
What this guide covers
Stack Logic
Why stacking only works when the problem is correctly identified first and what most researchers get wrong before they even pick a compound.
Four Categories
Additive, conditional, redundant, and either/or. Every combination fits one. Knowing which one changes the decision entirely.
Mechanism Reference Table
GLP-1 compounds, GHRH analogs, GHRPs, repair peptides, mitochondrial compounds. If two appear in the same class, that is a redundant stack.
Diagnostic Flowchart
Four questions that tell you whether your current stack is additive, redundant, unreadable, or unconfirmed before you change anything.
MOTS-c vs SS-31
Why this is not a stack question at all and how to identify which failure point is actually present before choosing between them.
Foundation Check
The four inputs that have to be stable before any compound decision is relevant. If any of them fail, this is the first intervention.
Timing and Sequencing
Why the order compounds are introduced often matters more than the combination itself and how to keep a protocol readable.
Three Diagnostic Questions
When a protocol has stalled, these narrow the variable faster than any addition will.
Who this is for
Researchers who are already running a protocol and not seeing the results the compounds should produce.
Researchers who have added a second or third compound and cannot tell which one is responsible for what they are seeing or not seeing.
Researchers who have stalled and are considering adding something new before identifying whether the current configuration is already creating interference.
Anyone who wants to understand why the same compound can perform completely differently depending on what else is running alongside it.
The four categories explained
Every compound combination falls into one of these. The mechanism reference table inside the guide tells you exactly where each combination lands.
| Category | What it means | Example |
|---|---|---|
| Additive | Different mechanisms, different problems. Each compound does something the other cannot. | CJC-1295 no DAC + Ipamorelin |
| Conditional | Additive only when the right problem is confirmed first. Without the diagnosis, it adds cost. | Retatrutide + MOTS-c |
| Either/Or | Not a stack question. A diagnosis decision. Running both before identifying which failure point exists adds cost without leverage. | MOTS-c vs SS-31 |
| Redundant | Same pathway, stronger feedback limitation. Neither compound performs the way it would alone. | Tesamorelin + CJC-1295 |
Diagnostic flowchart — preview
1
Are any two compounds in your current protocol doing the same basic job through the same basic mechanism?
2
Did you add your most recent compound before the previous one had produced a clear, readable response on its own?
3
Can you confirm which specific problem each compound is solving, and that no two are solving the same problem?
4
Has each compound in your current stack produced a clear response when run in isolation at some point in your research?
Result A — Redundant Stack
Two compounds competing for the same receptor. Remove the redundant compound and re-establish a clean baseline before adding anything else.
Result B — Unreadable Stack
Too many variables running simultaneously to produce a conclusion you can trust. Hold stable for a minimum of four weeks before any change.
Result C — Unconfirmed Conditional
You may be running the right compounds for a pattern you have not confirmed exists. The next step is diagnosis, not addition.
Result D — Defensible Additive Stack
Different mechanisms, different problems, clear individual responses. If results have stalled, the limiting variable is somewhere else in the protocol.
If the framework is not enough
This guide identifies whether a stack conflict exists and gives you the framework to act on it. There is a category of stall it cannot reach — where two variables are active at the same time, or where the stack looked correct but a second variable was running underneath the whole time. That pattern requires more diagnostic resolution than any general framework can provide. That is what the Protocol Audit is designed for.
For educational and research purposes only | Not medical advice | Not for human use guidance | Project Theo
Styled With
