Personliga mRNA-vacciner har ett tillverkningsproblem – och peptidanalys kan hjälpa till att bygga bättre arbetsflöden

Produktionsmodellen n-av-1 och dess strukturella paralleller i Peptide R&D

Tjänster Personliga mRNA-vacciner kräver en tillverkningssats per patient, per behandlingscykel. Varje batch involverar genomisk sekvensering, beräkningsbaserad neoantigenprioritering, mRNA-syntes, lipidnanopartikelformulering, och frisättningstest – allt inom ett behandlingsfönster mätt i veckor. A 2026 analys publicerad i BioPharma Dive noterade att utplacering i kommersiell skala av dessa vacciner skulle kräva "tiotusentals individuella partier," som "i grunden bryter mot den konventionella batch-tillverkningsmodellen."

Peptidprogram som verkar över neoantigenvaccinutveckling, MHC-peptidtetramerpaneler, eller högkapacitetsscreeningsbibliotek står inför en strukturellt identisk utmaning. Ett enda upptäcktsprogram kan kräva 15–30 anpassade sekvenser syntetiserade i milligram till multigram skala, var och en med sin egen modifieringsprofil, reningskrav, och releasespecifikation. Att röra sig effektivt över sekvenser – utan att bygga om analys- och dokumentationsinfrastrukturen varje gång – är ett kapacitetsgap som direkt kartläggs till vad mRNA-tillverkare arbetar för att stänga.

Fyra verksamhetsprinciper hanterar denna lucka. Var och en härrör från etablerad peptid CMC-praxis och från den framväxande modulära tillverkningslitteraturen för personlig terapi.

Peptidsyntes

Lektion 1: Modulär produktionsarkitektur minskar risken för sekvensförändringar

Varför det spelar roll. Monolitiska tillverkningsprocesser – designade från ände till ände runt en enda sekvenstyp – misslyckas förutsägbart när ett program stöter på en strukturellt utmanande peptid. I SPPS-baserad syntes, Vanliga fellägen inkluderar hydrofoba kopplingsfel i långkedjiga sekvenser, oväntad aggregering på hartset under förlängda syntetiska cykler, och utbyteskollaps vid avskyddningssteget när skyddsgruppsavlägsningsförhållanden aldrig karakteriserades mot denna specifika sekvensklass. När processen är monolitisk, varje fel kräver återuppbyggnad från början. När processen är modulär, varje fel kan isoleras till en specifik enhetsdrift och åtgärdas utan att störa de andra.

Hur man implementerar det. En modulär plattform för peptidsyntes organiserar produktionen i distinkt, omkonfigurerbara block: ruttval (SPSS, LPPS, hybridfragment-kondensation), kopplingskemi (aktiveringsreagens, cykeltider, temperaturkontroller), rening (förberedande RP-HPLC-gradientdesign, bråksammanslagningskriterier), och formulering (motjonbyte, lyofiliseringscykel, löslighetsscreening). Varje block har definierade ingångar, utgångar, och acceptanskriterier som inte beror på detaljerna för intilliggande block.

För sekvenser ovan 30 aminosyror eller som innehåller flera modifieringsställen, Neulands 2026 CMC utvecklingsvägledning rekommenderar ett strukturerat ruttscoutningssteg innan man bestämmer sig för någon syntesväg: utvärdera SPPS kontra hybridfragmentmetoder med användning av korta representativa delsekvenser, med renhet och utbyte som beslutet utlöser snarare än analogi med en tidigare framgångsrik molekyl.

En praktisk beslutsram för vägval:

Hur ett misslyckande ser ut. Ett program som hoppar över ruttscouting och tillämpar samma SPPS-cykel på en hydrofob sekvens med 40 rester som på en standardpeptid med 15 rester kommer att producera en föroreningsprofil som domineras av ackumulerade trunkationer och deletionsanaloger. Dessa arter liknar strukturellt målsekvensen och samelueras under de flesta standardgradientförhållanden. Retroaktiv metodutveckling i det skedet är dyr och försenar nedströms tidslinjen med veckor.

Lektion 2: Snabb metodutveckling kräver plattformsanalys, Inte per-sekvensanalyser

Varför det spelar roll. En av de avgörande utmaningarna för tillverkning av personlig mRNA-vaccin är att varje patientparti kräver sin egen frisättningstestcykel. Som MDPI Pharmaceutics 2022 utvecklingsrapport om RAMEN-001 kliniskt neoantigenvaccin dokumenterat, varje syntetiserad peptidsats krävde mellanliggande testning (utseende, område % renhet, identitet av UPLC-MS) och releasetestning (renhet, identitet, endotoxin, sterilitet) före poolformulering. Köra en anpassad metodutvecklingscykel för var och en av 20 peptider per patient i klinisk skala är inte genomförbart; lösningen är plattformsmetoder som gäller över sekvenser utan förlängning.

Samma logik styr peptidupptäckt och CMC-program med hög sekvensvariation. A platform analytical method has three properties: it covers the expected mass range and hydrophobicity range of the sequence class, it separates structural classes of process-related impurities from the main peak under a single gradient condition, and it produces a traceable chromatographic record that can be reproduced across lots and analysts without method-specific calibration.

Hur man implementerar det. The minimum viable platform analytical package for small-batch, high-variation programs:

• RP-HPLC or UPLC purity method: C18 wide-pore column (300 Å porstorlek, 5 µm particle or sub-2 µm for UPLC), linear gradient from 5% till 60% acetonitril i 0.1% TFA over 20–30 minutes, UV detection at 214 nm. Detektering kl 214 nm captures the amide bond absorbance of all peptide backbones and is the reference wavelength for accurate area-percent purity quantitation in sequences without aromatic residues.

• LC-MS identity method: Electrospray ionization (ESI), positive mode, reporting observed monoisotopic or average mass against the theoretical value, with mass error stated in daltons or ppm. The ionization mode and calibration standard must be recorded in the batch data—not merely “mass matches theoretical.”

• Method transfer protocol: When multiple vendors or testing labs handle different stages of a program, aligning column chemistries, mobile phase grades, and detection parameters before the first batch is manufactured avoids apparent impurity discrepancies that arise from method divergence rather than product variability. De harmonized analytical transfer protocols described in multi-partner peptide CMC programs consistently demonstrate that misaligned HPLC methods between an API manufacturer and a bioanalytical CRO generate additional characterization runs that add weeks to timeline without resolving actual quality questions.

Hur ett misslyckande ser ut. Detektering kl 254 nm eller 280 nm—commonly used in commercial labs for routine UV scanning—misses non-aromatic impurities entirely. A peptide batch reported as ≥95% pure at 280 nm can show a materially different impurity profile at 214 nm if it contains oxidation products or truncated sequences without aromatic side chains. For any peptide supplied as a biological tool reagent or clinical intermediate, this is not a calibration preference—it is an identity and purity gap that affects downstream experimental reproducibility.

What we see in practice. In our own peptide programs, de 214 nm versus 280 nm distinction rarely shows up as a single dramatic number—it shows up as a pattern. When we re-examine a batch that looked clean under a 280 nm scan, the chromatogram at 214 nm consistently reveals low-level species that the aromatic-only wavelengths never registered: early-eluting truncation clusters, late-eluting oxidation shoulders, and the broadened main-peak flanks that signal partial deprotection. The total area attributed to these species is often small, but their presence changes how we interpret the lot—and, more importantly, it changes the acceptance decision. This is why our working rule is simple: if a sequence has no aromatic residues, or if the customer plans to use the material in a structure-activity or stability study, we treat 214 nm as the reporting wavelength regardless of what a 280 nm scan suggests. The lesson for anyone specifying peptide analytics is not that one wavelength is “right” and the other “wrong”—it is that the detection wavelength is a scientific choice that should match the sequence and the downstream use, not a lab default inherited from an unrelated workflow.

Lektion 3: Identitets- och föroreningstestning måste vara ortogonal och skiktad

Varför det spelar roll. The most common analytical quality gap in small-batch peptide supply is conflating purity with identity. RP-HPLC area-percent purity establishes what fraction of the detected signal corresponds to the main peak—it does not confirm that the main peak is the intended sequence. Mass spectrometry confirms the molecular weight of the predominant ion—it does not rule out co-eluting isobaric impurities or sequence isomers that share the same nominal mass.

A 2023 analysis of USP reference standards for synthetic peptide drug quality, published in the Journal of Pharmaceutical and Biomedical Analysis, is explicit on this distinction: identitet, renhet, innehåll, and impurity profiling are separate analytical objectives requiring different methodological approaches. Satisfying one does not satisfy the others.

For personalized programs, this orthogonality requirement applies at the lot level, not only at product validation. Each batch carries its own synthesis history and therefore its own impurity risk profile. A coupling failure at residue 14 of a 25-residue sequence produces a deletion analog that may share retention time with the target under a gradient optimized for the full-length peptide but has a different mass—invisible to UV detection alone.

Hur man implementerar det. A tiered testing protocol calibrated to batch risk:

For impurity profiling, the key SPPS-derived impurity classes to monitor are: trunkerade sekvenser (deletion of one or more residues, occurring in the C-terminal direction); oxidationsprodukter (Träffade, Trp, and Cys as primary sites, particularly after extended handling); incomplete deprotection species (Pbf persistence on Arg is common under abbreviated cleavage conditions); and insertion analogs from racemization at activated residues during coupling. LC-MS/MS can assign most of these classes by fragmentation pattern, but the prerequisite is a baseline RP-HPLC method that separates them from the main peak rather than co-eluting them into a single broad region.

⚠️ Critical distinction: “Purity ≥95% by HPLC” and “identity confirmed by MS” are two separate quality gates—satisfying one does not satisfy the other. For any peptide lot entering a biological assay or supplied as an active ingredient, both are required. Frameworks for what a complete analytical documentation record should contain are outlined in work on upgrading quality documentation in the research peptide market, where the same analytical completeness gap has been identified as a systemic quality concern.

De AxonVerified identity testing protocol documentation (2026) states the operational principle concisely: this two-method approach reflects the standard applied in established pharmacopoeial testing—purity quantification establishes how much of the sample is the target compound, while identity confirmation establishes what that compound is. Om

Lektion 4: Små batchdokumentation behöver en specialbyggd mall

Varför det spelar roll. Standard batch record formats designed for large-scale, single-sequence peptide manufacturing do not accommodate the workflow speed or sequence variability of high-variation programs. A review published by PolyPeptide on neoantigen peptide manufacturing workflows stated directly: standard batch records used in traditional peptide manufacturing do not allow the flexibility and speed needed for neoantigen peptide manufacturing, and a simplified but complete GMP batch record format must be developed and used. Peptidproduktion

The same conclusion applies to any small-batch, high-variation peptide program running under compressed timelines—whether a neoantigen peptide pool for an academic immunology lab, a custom isotope-labeled internal standard panel for a PK/PD assay, or a set of modified analogs being evaluated in parallel SAR studies.

Hur man implementerar det. A fit-for-purpose documentation package for small-batch peptide programs contains six traceability elements:

1. Sequence record: The full amino acid sequence, modification positions, protecting group scheme, and route assignment (SPSS, hybrid, etc.). Should include a crude purity acceptance criterion before the batch is committed to purification, so borderline lots are flagged rather than forced through.

2. Lot-specific analytical record: Raw RP-HPLC chromatogram (uncompressed, with integration report at 214 nm), LC-MS full spectrum (theoretical mass, observed mass, ionization mode, instrument, calibration standard), and where applicable, AAA or other orthogonal confirmation. The raw data files—not only the summary table—should be retained and transferable.

3. Chain-of-identity documentation: For programs where the peptide sequence derives from a specific biological source (patient biopsy, variant call, HLA genotype assignment), the documentation trail must connect the source identifier to the synthesis specification to the lot number to the release record. This is the peptide-side equivalent of the chain-of-identity requirement in mRNA manufacturing programs and is auditable under ICH Q10 quality system principles.

4. Release specification table: Explicit acceptance criteria for each tested attribute, stated numerically. “Purity: ≥95.0% by RP-HPLC area at 214 nm” is a specification. “High purity” is not. De EMA Guideline on the Development and Manufacture of Synthetic Peptides requires that purity and impurity limits be set with defined analytical methods and justified thresholds. That standard should be treated as a floor, not a ceiling, even in pre-IND work.

5. Reference lot comparability anchor: Even in research programs, retaining one well-characterized batch per sequence allows future lots to be evaluated against a baseline. This is a low-cost intervention with significant downstream value when method robustness questions arise or when a supplier change requires comparability demonstration. A peptide IND CMC checklist developed for IND-stage programs provides a practical template for escalating documentation requirements as the development stage advances.

6. Deviation and escalation record: A field noting any synthesis deviation—coupling failure detected by in-process ninhydrin or UV monitoring, resin replacement mid-synthesis, gradient modification during purification—and the response taken. For programs using external CDMOs or multiple vendors, this record is the mechanism by which process drift becomes visible before it becomes a quality failure.

Hur ett misslyckande ser ut. A program that supplies peptide lots with CoA data limited to a single HPLC purity value and a nominal mass confirmation has no mechanism for detecting lot-to-lot drift in impurity profile, no basis for comparability claims, and no defensible quality system if an assay failure traces back to the peptide material. In academic programs, this typically surfaces as irreproducible dose-response data attributed to biological variability. In biopharma programs, it surfaces in toxicology deviations or IND correspondence with the agency.

Hur ett misslyckande ser ut. A program that supplies peptide lots with CoA data limited to a single HPLC purity value and a nominal mass confirmation has no mechanism for detecting lot-to-lot drift in impurity profile, no basis for comparability claims, and no defensible quality system if an assay failure traces back to the peptide material. In academic programs, this typically surfaces as irreproducible dose-response data attributed to biological variability. In biopharma programs, it surfaces in toxicology deviations or IND correspondence with the agency.

What our customers tell us. The questions we hear most often from research groups are rarely about synthesis at all—they are about documentation. Two recur with particular consistency. The first is a version of “the certificate says 98% ren, but is it the right peptide?”—the recognition, usually arrived at after a puzzling assay result, that a purity figure alone does not establish identity. The second is a comparability question: “we reordered the same sequence six months later and got a different result—did the product change, or did the assay?” In both cases, the underlying need is the same: a documentation trail that connects the sequence, the analytical raw data, the release criteria, and any deviation encountered along the way. Because we build a lot-level record for every manufactured sequence—including the raw RP-HPLC and LC-MS files, not only the summary line—these questions can usually be answered from the batch file rather than by resynthesizing and retesting. That is the practical value of fit-for-purpose documentation: it turns a recurring customer anxiety into a routine, auditable answer.

Koppla mRNA-lektioner till peptidarbetsflödesdesign: En praktisk sammanfattning

The table below maps the four manufacturing lessons from personalized mRNA vaccine programs to their operational equivalents in peptide analytics and CMC practice.

This comparison is not an argument for applying clinical GMP controls to early research peptides. It is an argument for applying the architecture of those controls—modular production thinking, ortogonal analys, tiered documentation—at the stage of rigor appropriate to the program. Research-grade programs frequently skip these controls not because the underlying logic is inapplicable, but because no one has translated the framework into practical defaults for a non-GMP context.

Vad du ska göra härnäst om ditt program sträcker sig över mer än fem sekvenser

If your current program is generating batches across more than five distinct sequences, or advancing materials toward functional assays and animal studies, three workflow decisions determine most of the downstream quality risk:

Route assignment before synthesis: Does your team or CDMO use a structured scouting protocol with explicit decision triggers, or is route selection determined by vendor default and sequence analogy to prior molecules?

Analytical completeness: Does every released lot carry RP-HPLC purity data detected at 214 nm (with raw chromatogram), ESI-MS identity data with mass error stated, and a retention of raw instrument files—or only a summary table?

Documentation traceability: Can a quality anomaly detected in an assay be traced back to the batch record, the synthesis deviation log, and the original raw analytical data in under 30 minuter?

De MOL Ändringar custom peptide synthesis platform issues lot-level documentation packages covering RP-HPLC chromatograms, high-resolution ESI-MS spectra, and mass-error-stated identity confirmation for every manufactured sequence—applying the same orthogonal testing discipline described in this article to both standard catalog sequences and complex custom modifications. Teams building or benchmarking their peptide workflows against this framework can request a technical feasibility assessment covering synthesis route selection, impurity control strategy, and documentation template design for high-variation programs.