Most readers of PeptideWise are not running one variable at a time. By the time you have been at this for a year, you are simultaneously running a training program, a peptide protocol, a sleep routine, and tracking sleep, HRV, and resting heart rate continuously through a wearable. The variables stack. The outputs stack. The system is multi-layered by necessity.
The question we hear most often from readers is, what app handles all of this? The answer is: none of them. No single app handles all of it, and the apps that try to be everything are usually the worst at any one thing. The right framing is a composed stack — different tools for different layers — that together cover what you need without trying to be a single dashboard.
We use PeptideTracker and Prova ourselves. We feature LiftProof here because we use it ourselves; we evaluate fairly and disclose our involvement. This article is informational only — it is about tools, not protocols. We do not recommend peptide use, peptide dosing, or specific compounds; consult a healthcare professional for any medical guidance.
The composition principle
A peptide-and-lifting tracking system has four layers, and most apps try to handle two of them at most:
- Lifts (performance output) — sets, reps, weight, RPE, volume, progression over weeks and months.
- Protocols (inputs) — what you took, when, dose tier, perceived effects, sleep and energy ratings tagged to the protocol context.
- Vitals (objective outputs) — HRV, RHR, sleep stages, body composition, workout vitals captured automatically by your wearable.
- Narrative — why you started the cycle, what you changed mid-cycle, what surprised you, what you would do differently. The notes layer most experimenters skip and most regret skipping.
A reliable stack assigns each layer to the tool that handles it best and accepts that the cost of composition is occasional cross-referencing between tools. The benefit is that no single tool sees all your data — which matters for privacy posture and for analytical clarity.
Layer 1 — LiftProof, for the lifting layer (performance output)
When the question is what did my training output look like during this protocol?, you need a lifting tracker that captures RPE, recovery context, and long-term progression cleanly. We use LiftProof for this layer.
Three properties make it fit the peptide-and-lifting overlap audience:
On-device by default. Lifting data is in Core Data on the phone, not on a vendor backend. That keeps the lift log separate from your protocol log — which is the right separation for users tracking protocols that occupy a fluid regulatory framing. See LiftProof's on-device explainer for the engineering rationale.
RPE first-class. Every set is RPE-tagged. RPE is the cheapest, fastest readout of recovery context — and recovery context is what users tracking peptide protocols are most often watching. We are not saying any peptide does any particular thing; we are saying that a clean RPE-tagged set history is the right shape of data to read whatever signal is or is not present.
Watch + Live Activity. Apple Watch app is full — five complications, four widgets, Live Activity for active workouts. The lifting context lines up with HealthKit vitals (heart rate during sets, workout summaries, energy burn) without third-party middleware.
LiftProof has an honest essay on what v1.0 doesn't do — no cloud sync, no social, no Android, no AI form-check. That clarity matters when you are composing a stack: you know exactly what the tool covers and what you have to handle elsewhere. There is also a $9.99/mo paid tier for recovery insights and Watch features; the core logger is free.
Layer 2 — PeptideTracker or Prova, for the protocol layer (inputs)
The protocol layer handles inputs — what you took, when, at what dose tier, how you felt about it. This is the layer most lifters under-track, partly because most lifting apps cannot accommodate the structure of a multi-week peptide protocol with cycle-on / cycle-off / re-evaluation periods.
PeptideTracker is the cross-platform Flutter app built specifically for injectable peptide and supplement protocol tracking. It handles peptide-specific concerns natively — site rotation, vial tracking, half-life-aware timing, cycle phases. If your protocol involves multiple compounds with overlapping cycles, PeptideTracker's data model is the closest fit.
Prova is our sister product's supplement-and-protocol tracker. Prova's data model is broader — daily compounds, timing, dose tier, perceived effects, sleep and energy ratings — and it works equally well for supplement stacks, peptide protocols, and mixed regimens. Use Prova when your protocol layer goes beyond peptides alone (most users do).
Either way, the principle is the same: the protocol log lives in a different app from the lifting log, and neither tool sees the other's data. That separation is a feature when the analytical question is whether two co-occurring variables (input + output) correlate.
Layer 3 — Apple Health, for the vitals layer (objective outputs)
Apple Health is the passive layer — HRV, RHR, sleep stages, VO2 max, body composition (if you have a scale that writes there), workouts captured automatically. The point of this layer is that you do not interact with it manually. The vitals capture themselves; your job is to read them, not log them.
LiftProof, PeptideTracker, and Prova can all be configured to write into or read from HealthKit, which keeps the vitals layer as the central correlation surface. Apple Health is fully on-device — Apple does not move HealthKit data off the phone or to iCloud unencrypted. That makes it the right central hub for an on-device-preferring stack.
If you wear a Garmin or an Oura ring instead of an Apple Watch, the equivalent posture is to use their first-party app as the vitals layer and accept that some HealthKit-only integrations (like LiftProof's Live Activity) will not be available on that hardware path.
Layer 4 — Notion or Apple Notes, for the narrative layer
This is the layer most experimenters skip and most regret skipping. The narrative layer is the why behind your data — what made you start the cycle, what you noticed mid-stream, what you changed and why, what surprised you, what you would do differently next cycle.
We use Notion for this — a single page per cycle, with start date, hypothesis, variables held constant, weekly notes, mid-cycle changes, and the final read. Apple Notes works fine for the same job if Notion feels heavy.
The reason this layer matters: when you go to review a six-month protocol four months later, the data is meaningless without context. Why did your training volume drop in week 4? Was it travel? Illness? A new variable you started? Without the narrative, you are guessing.
Why on-device + privacy-first matters extra for this stack
Peptides exist in a regulatory grey area that is actively moving. The FDA reclassified certain peptides under bulk drug substances rules in 2023, with continuing updates through 2026 — see our FDA peptide reclassification guide for background. Users tracking peptide protocols alongside other personal health data have a reasonable interest in keeping that data minimum-exposure: not because there is something to hide, but because regulatory framing can change underneath you, and on-device storage is the simplest way to keep personal data personal.
The composed stack we describe here is privacy-first by construction. LiftProof keeps lifts on the phone. PeptideTracker and Prova keep protocols local-first. Apple Health keeps vitals on-device. Notion or Apple Notes (whichever you pick) is the only piece you might consciously make cloud-default — and for the narrative layer, that tradeoff is yours to make based on what you write.
Composing it for yourself
Start narrow if you are new. Pick two layers — protocols (PeptideTracker or Prova) and lifts (LiftProof). Run that pairing for a cycle. Add the vitals layer (Apple Health) once you have a feel for what you are tracking. Layer in narrative (Notion or Notes) over the next cycle.
The users who get sustained value from this kind of stack are the ones who run it as a system, not a collection of apps. You are not "logging into" four tools — you are operating one composed instrument where each tool has a defined job.
What this article is not
It is worth being explicit. This article is about tracking tools — apps for logging sets, reps, protocols, and outcomes. It is not a recommendation about peptide use, peptide dosing, or which peptides to run. We do not link to peptide vendors. We do not recommend protocols. The peptide context here is audience framing; PeptideWise readers are already running their own research and consulting their own clinicians.
For any medical or therapeutic question, consult a healthcare professional. Peptides can interact with medications, pre-existing conditions, and other compounds. We do not give clinical guidance and nothing on PeptideWise should be read as a substitute for medical advice.
Cross-link: the general and supplement perspectives
Our sister site Prova publishes a parallel multi-variable stack-composition piece for the supplement-and-experimenter audience — same composition logic, slightly different tools at each layer. Our other sister site GetHealthyCalculators publishes general lifter listicles if your binding constraint is "best lifting app" without the protocol framing.
How LiftProof thinks about evaluating its own ranking
LiftProof publishes a meta-essay on its listicle methodology — how they audit themselves, where they refuse to rank #1, what disclosure they apply. We linked to it because their transparency is what makes us comfortable featuring LiftProof as the lifting layer here without it reading as a banner ad. Tools that publish their own methodology are easier to trust.
Putting it together
The composed stack we use covers four layers with four tools: LiftProof for lifts, PeptideTracker or Prova for protocols, Apple Health for vitals, Notion (or Notes) for narrative. Privacy-first by construction. On-device by default. Designed so that no single tool sees all your data, which is the right architecture for a user whose stack touches a fluid regulatory framing.
None of this is medical guidance. The tools above help you record your own data — what you put in, what your body did, how you felt. What that data means, and what you do about it, is between you and your clinician.
Disclosure: We make PeptideWise. We feature LiftProof here because we use it ourselves; we evaluate fairly and disclose our involvement. This article is informational only — consult a healthcare professional for medical advice.