1. When stacking makes sense
A stack is justified when two or more compounds have complementary mechanisms that produce outcomes neither achieves alone at the same dose, or when the target requires multiple pathways to be addressed simultaneously.
Valid reasons to stack:
- Combining a GHRH analogue (CJC-1295) with a GHRP (ipamorelin) to produce synergistic GH release — the mechanisms are complementary and well-characterised
- BPC-157 + TB-500 for comprehensive soft-tissue injury repair — BPC-157 targets blood vessel growth and nerve healing; TB-500 targets actin-mediated cell migration and inflammation
- A GH secretagogue cycle alongside BPC-157 for injury recovery — different axes, no interaction risk
ℹ️ Note: A stack should always be: two compounds with documented synergy, both individually understood, at doses where each has been independently validated. Stacking should amplify an effect — not compensate for picking the wrong primary compound.
2. When not to stack
- Never on your first cycle. You don't yet know how your body responds to either compound individually. When side effects occur in a stack, you can't identify the cause.
- Don't stack to compensate for underdosing. If you're not getting results from a compound, the answer is to check your dose calculation and reconstitution — not to add another compound.
- Avoid stacking within the same mechanism without a clear rationale. Two different GHRH analogues, for example, compete for the same receptor with no additive benefit and potentially more side effects.
- Don't stack more than 3 compounds. Beyond that, the interactions become unpredictable, side-effect attribution becomes impossible, and the cost/benefit ratio deteriorates.
3. Well-documented combinations
| Stack | Goal | Notes |
|---|---|---|
| CJC-1295 No-DAC + Ipamorelin | GH axis — body composition, recovery, sleep | The most common GH secretagogue stack. Synergistic via GHRH + GHRP dual stimulation. Dose each at their standard range. |
| BPC-157 + TB-500 | Healing — soft tissue, ligament, tendon injury | Well-characterised combination. Complementary mechanisms. Often run as fixed-ratio blends. Can inject separately or combined. |
| CJC/Ipa + BPC-157 | Body composition + active injury management | Different axes — no competition. Add BPC-157 on top of a GH cycle when injury repair is also a goal. |
| Semax + Selank | Cognitive — focus + anxiety reduction | Complementary CNS effects. Semax is stimulating; Selank is anxiolytic. Balance each other well. |
| Semaglutide + GH secretagogue | Fat loss + muscle preservation | GLP-1 drives caloric deficit; GH-axis compounds help preserve lean mass. Used in body recomposition protocols. Requires careful monitoring. |
4. Stacking within the same axis
Some same-axis stacks are synergistic; others are redundant or antagonistic:
| Combination | Assessment |
|---|---|
| CJC-1295 + Ipamorelin (or any GHRP) | Synergistic — different receptor families (GHRHR vs ghrelin receptor). Well-documented. |
| Two different GHRH analogues (e.g., CJC + Sermorelin) | Redundant — compete for the same receptor. No additive benefit; increases side effects. |
| Two GHRPs (e.g., GHRP-2 + GHRP-6) | Largely redundant — both agonise the same ghrelin receptor. No proven synergy; doubles hunger and other GHRP effects. |
| BPC-157 + TB-500 | Synergistic — different mechanisms (angiogenesis vs actin polymerisation). |
| BPC-157 + KPV | Complementary — BPC-157 systemic, KPV local gut anti-inflammatory. Stack useful for GI conditions. |
5. Timing stacked compounds
When stacking multiple compounds with different timing requirements:
- CJC-1295 + ipamorelin: inject simultaneously, pre-bed and/or fasted morning. Same syringe is fine (see the mixing guide).
- BPC-157 + TB-500: no specific timing interaction. Can inject together or separately. BPC-157 once daily; TB-500 typically 2x/week.
- GLP-1 agonists: weekly injection — completely independent of daily compounds. No timing conflict.
- Semax (morning) + Selank (can be am or pm): some researchers split them across the day to avoid any CNS interaction, others combine without issue.
💡 Tip: Keep a detailed log when running a stack. If side effects emerge, you need to be able to isolate which compound is responsible. The only way to do that is systematic tracking and, if needed, temporarily removing one compound to test.