The Stack Compatibility Guide
Why some combinations add leverage and others just add cost. How to tell whether two compounds in your protocol are working together, doing the same job twice, or quietly fighting each other, before you add anything.
Not medical advice. Not a dosing recommendation. Not a sourcing guide. Every compound here is a research compound and every framework is an educational reference point drawn from published literature and documented research practice.
Are you a member?
This guide is part of the guides library. It is included with the guides library membership, the Protocol Builder, and Full Access. If you hold any of those, enter the email on your subscription to open the full guide. If not, you can read it as a guest and see exactly what every section covers.
Not a member yet? The guides library is available as a standalone membership at $19.99 a month. The Protocol Builder includes the full library, and Full Access opens every guide plus the Protocol Builder, the Stack Visualizer and the research search engine. See the options
The Core Distinction
A new signal versus a louder version of one you already have
Most researchers think about stacking the wrong way. The question they ask is what else can I add. The question that actually decides the outcome is whether the addition introduces something new, or just does more of what is already there. Those are not the same move, and confusing them is what turns a protocol into a slow and expensive experiment.
Every compound works by sending a signal down a specific pathway. A receptor, meaning a docking site on a cell, catches that signal and produces a response. Add a second compound that runs down a different pathway and targets a different problem, and the body gets two distinct signals and answers both. That is additive. Add a second compound that runs down the same pathway as something already in your protocol, and you have not added a new signal. You have turned up the volume on the one already playing, and the body has systems built specifically to turn that volume back down.
This guide sorts combinations into four categories, and each one is defined by mechanism, not by name or popularity. Additive means each compound works through a different pathway and each solves a problem the other cannot, so both conditions have to be true at once. Redundant means both compounds hit the same receptor or produce the same downstream signal, so the second one mostly triggers a stronger feedback response. Conditional means the pairing is only additive once a specific problem has been confirmed to exist. Either or means the two are not a stack question at all, they are a single diagnosis you have to make before choosing. Knowing which category a pairing sits in before you touch the protocol is the difference between adding leverage and adding cost.
One framing point worth setting down before the rest. The four-category model here is a research reference framework for reading combinations, not a clinical rule set, and the same is true of the phase and pattern language used later. It is a way to make a protocol readable, and it holds up well in practice, but it is a working model rather than settled fact. Reading it that way is what keeps it useful. When the body responds to a louder signal by activating its feedback systems, researchers who stacked two compounds on the same receptor frequently find that neither performs the way it did alone. The compounds are usually not failing. The stack configuration is creating interference.
Is Your Stack Working Against You?
Answer in order and reach a read in one pass, before adding anything
Start with your current protocol and answer each question honestly. Do not skip ahead. Most stalls get met with the question of what to add next, and the more accurate first question is whether something already in the stack is interfering. This runs that check. It is a reasoning aid, not medical advice, and it points to research reference approaches rather than directions.
Examples: two GHRH analogs such as Tesamorelin and CJC-1295. Two GLP-1 compounds. Two compounds both working on appetite through overlapping pathways. You do not need receptor pharmacology to answer, only whether two things are doing the same job the same way.
The point is whether each compound had a clean baseline before the next went in. If several went in close together, no single result can be traced to a single compound.
Different mechanism is not enough on its own. Two compounds can run down different pathways and still be aimed at the same problem, which is where conditional pairings quietly go wrong.
A compound that worked alone but is quiet in the stack points at the configuration, not the compound. One that has never produced a clear read on its own is a different problem.
When two compounds hit the same receptor, the body reads it as one stronger signal and activates the feedback systems that bring that signal back down. Research suggests neither may perform the way it would alone, which reads as both compounds underdelivering at once. The compounds are usually not the problem. The configuration is.
The defensible move is to remove the redundant compound and let a clean baseline reestablish before adding anything else. The mechanism table further down groups compounds by class, so if two of yours share a class, that is the redundancy to resolve first.
With compounds added close together, or one that never produced a clear read on its own, there is no control variable, so any result the stack produces is hard to attribute. This is not a protocol yet, it is an experiment without a baseline, and the honest conclusion is that the read is not valid rather than that a compound failed.
The research reference approach is to hold the current protocol stable for a minimum of four weeks with no additions, let a pattern develop, and only then decide whether the combination is the issue. Adding another compound into an unreadable stack makes the read worse, not better.
A conditional pairing is only additive once the specific problem it targets has been confirmed to exist. If you cannot yet say the problems are distinct, you may be treating a pattern that has not been established, which means the next step is diagnosis, not another compound. Confirm the pattern first, then judge whether the stack is correct.
This is the read the MOTS-c versus SS-31 section and the mechanism table are built to resolve, since both turn on identifying which failure point is actually present before choosing.
This configuration has the three properties an additive stack needs: each compound works through a different mechanism, each solves a problem the other cannot, and each produced a clear response on its own. Based on that, the configuration is not the thing holding you back. If results have stalled, research suggests the limiting variable is somewhere else in the protocol.
The foundation check and the sequencing section point at where that variable usually hides, since a clean stack can still be held down by sleep, stimulant load, stress, protein, or the order things went in.
Additive vs Redundant
The mechanism logic that every stack decision runs on
The full mechanism logic underneath the whole guide, laid out side by side: what makes a combination genuinely additive, what makes one redundant, and why a redundant stack so often leaves both compounds underperforming rather than producing a stronger result. This is the reasoning you apply before every addition, the part that turns a vague sense that something is off into a specific read on whether two signals are stacking or colliding.
Genuinely Additive Combinations
The pairings that actually add leverage, and the reason they work
The combinations that genuinely add leverage, worked through mechanism by mechanism: the growth hormone peptide pairing where one compound starts the pulse and a second sharpens it through a separate pathway, and the repair pairing where one acts at the site and the other works across the whole body. Each is explained so you can see the shared property, different mechanisms aimed at different problems, and apply the same test to any pairing you are considering.
Redundant Combinations
What actually happens when two compounds do the same job
The stacks that add cost without adding a mechanism, named directly: two GHRH analogs running together, two GLP-1 compounds stacked without identifying why the first one stalled, and the cagrilintide on retatrutide question that comes up constantly and usually points the wrong way. Each one explains what the body actually does with the redundant signal, and what the more defensible configuration looks like instead.
MOTS-c vs SS-31: Not a Stack Question
A diagnosis you make, not a pairing you run
Why the two compounds most often discussed together are not a stack decision at all, but a single diagnosis you have to make first. They address different failure points in the same energy system, and the section walks the specific pattern that points to one over the other, so you decide which failure point is actually present instead of paying for both and hoping. If you want the deeper standalone treatment, the MOTS-c and SS-31 guide covers it in full.
Timing and Sequencing
The order of introduction that makes any protocol readable
The part of stacking almost everyone skips: not which compounds to combine, but when to introduce each one and in what order. The sequence often matters more than the combination, because running compounds one at a time is what gives you a control variable and makes any result traceable to a cause. This section explains why a stack of several compounds started at once is an experiment with no control, and how sequencing turns the same compounds into something you can actually read.
The Mechanism Reference Table
Every compound sorted by class, so shared mechanisms are obvious
The working reference for the whole guide: every compound relevant to stack compatibility sorted into its mechanism class, so that spotting a redundancy becomes a single lookup. GLP-1, GHRH analogs, GHRPs, repair, mitochondrial and metabolic, and fat mobilization, each with what the class does and the notes that matter for pairing. If two of your compounds land in the same class, the table tells you at a glance that you may be running the same job twice.
Before You Add Anything
The four inputs that decide whether any stack can be read at all
The check that has to clear before any stacking decision matters at all. Four inputs, sleep, stimulant load, chronic stress, and protein intake, each either stable enough to proceed or not, because if any one of them is the real limiting variable then no combination of compounds will produce a clean result. This is the section that saves the most money, since it catches the stalls that were never about compound selection in the first place.
Every guide, one membership
This is one of seven guides in the library. The guides library is available as a standalone membership, and it is also included with the Protocol Builder and Full Access. Full Access opens every guide plus the Protocol Builder, the Stack Visualizer and the research search engine. One price either way.
Research Protocol Bible
The whole framework in one place. The phase model for deciding what to run and when, every compound sorted by what it actually does, the bottlenecks that stall a protocol, and a full reference section. If the other guides are chapters, this is the spine they hang off.
Unlock with membershipIntake & Output
Why a protocol stalls, and which side is actually failing, intake or output. The two failure modes that produce identical stalls, the self assessment that separates them, and the compound that fits each. The level above a single stack decision.
Unlock with membershipMOTS-c & SS-31
The two mitochondrial compounds most often confused for each other, in depth. Signaling versus structure, the energy pattern each one addresses, and how to tell which failure point you actually have before choosing. The standalone version of the either or call in this guide.
Unlock with membershipRetatrutide From First Dose to Full Protocol
Retatrutide start to finish. What the third receptor actually changes, what the early weeks tend to look like, how researchers read the thermogenic signal, and where it sits alongside the compounds people run with it. Built for the protocol being planned around reta.
Unlock with membershipRetatrutide, Tesamorelin, Ipamorelin
Three compounds read as one system. How a fat loss driver, a growth hormone signal and its amplifier get sequenced so they support each other instead of colliding, and the redundancy that quietly leaves one of the three doing nothing.
Unlock with membershipMOTS-c Guide
MOTS-c on its own, in depth. The mechanism in plain English, the energy pattern it addresses, the signs it is working, and the phase where it helps against the phase where it makes things worse.
Unlock with membershipThe rest of this guide, and everything above
The decision tool above is the whole guide in miniature. Same discipline, same refusal to sell you a compound you do not need. A guides library membership, the Protocol Builder, or Full Access opens the remaining seven sections here and every guide in the library.
See the options