Suppliers and packagers for rukobia

rukobia

Listed suppliers include manufacturers, repackagers, relabelers, and private labeling entitities.

Applicant	Tradename	Generic Name	Dosage	NDA	NDA/ANDA	Supplier	Package Code	Package	Marketing Start
Viiv Hlthcare	RUKOBIA	fostemsavir tromethamine	TABLET, EXTENDED RELEASE;ORAL	212950	NDA	ViiV Healthcare Company	49702-250-18	1 BOTTLE in 1 CARTON (49702-250-18) / 60 TABLET, FILM COATED, EXTENDED RELEASE in 1 BOTTLE	2020-07-02

Rukobia (Fostemsavir) Suppliers: How to Map Upstream API, Key Intermediates, and Finished-Dose Manufacturing

Last updated: May 31, 2026

Rukobia (fostemsavir) supply is anchored by the drug’s marketing authorization holder and its contract manufacturing network. The most reliable supplier mapping for Rukobia is via FDA labeling and manufacturing sites tied to commercial product, then cross-checking with the Orange Book manufacturing-change history and any CMC-related filings that identify contract manufacturers and API/intermediate sources.

Which companies supply Rukobia (fostemsavir) finished drug product?

Rukobia is marketed in the US by ViiV Healthcare. Finished-dose manufacturing is typically performed by one or more contract manufacturing organizations (CMOs) whose sites are reflected in regulatory submissions and US product labeling.

What supplier entities show up in US regulatory documentation for Rukobia?

For Rukobia, the US-facing supply chain is assessed by:

• Drug product (tablets) manufacturing sites listed in FDA review/CMC documentation and reflected in labeling or FDA database manufacturing records.
• API and intermediate manufacturing sites used in the fostemsavir process, which can be disclosed in CMC sections of NDAs and supplements.
• Commercial batch manufacturing changes, which can surface through FDA supplements tied to process validation, site changes, or scale-up.

Common supplier categories in the Rukobia network

Rukobia supply typically spans:

• API manufacturer(s) for fostemsavir (active pharmaceutical ingredient).
• Intermediate manufacturer(s) for key synthetic building blocks and late-stage intermediates.
• Formulation and tablet manufacturing (CMO/contract site) for finished-dose fostemsavir tablets.
• Secondary packaging and distribution logistics (often separate entities, depending on labeling and distribution contracts).

What suppliers provide the fostemsavir API (active ingredient) and key intermediates?

Rukobia’s API supply depends on the fostemsavir synthetic route and the availability of compliant GMP manufacturing for:

• Late-stage intermediates
• Solvated/crystalline forms used in isolation and final API specifications
• Impurity-control classes that drive batch release

How to identify fostemsavir API suppliers

The most decision-grade approach is:

• Pull NDA/CMC manufacturing disclosure for API and intermediate sites.
• Cross-check with site-specific GMP listings appearing in FDA submissions and inspection histories.
• Validate whether the identified sites are single-source or have qualified second sources for commercial continuity.

API supply risk signals for fostemsavir

Key operational risks that supplier mapping must cover:

• Single-site API dependence
• Limited intermediate capacity bottlenecks
• Reliance on one specialized step for impurity control or chiral purity
• Regulatory constraint if API is made in a site with narrower inspection history

Which contract manufacturing organizations (CMOs) make Rukobia tablets?

Finished-dose manufacturing for Rukobia is generally performed by CMOs under ViiV oversight or by ViiV-affiliated manufacturing sites, depending on the commercial strategy and scale.

How many manufacturing sites typically support Rukobia supply?

Tablet programs usually run on:

• One primary drug product site for commercial scale
• At least one backup site for contingency in later lifecycle stages or post-approval site additions

Supplier mapping should therefore enumerate:

• Drug product site count
• Site roles (primary vs. secondary)
• Change history (which site came online and when)

What is the Orange Book status of Rukobia and what supplier information does it reveal?

Rukobia’s exclusivity and patent estate are relevant to supply because it constrains generic entry, which in turn affects manufacturing utilization and supply planning for the originator’s network.

Orange Book as a manufacturing change tracker

The Orange Book does not list supplier names directly in all cases, but it can be used to:

• Track relevant patents and exclusivity linked to the marketed formulation
• Identify product change events (via associated listing changes)
• Correlate listing updates with known CMC supplements that often include site or process updates

How do you map Rukobia suppliers for litigation, Paragraph IV, and generic risk?

Even if suppliers do not change, supplier mapping informs litigation strategy because generic development often targets:

• Same dosage form manufacturing approach
• Equivalent API sourcing and compliance with impurity specs
• Knockout claims tied to method and formulation patents

What supplier mapping impacts for IP and settlement posture?

• If API is constrained, generics face higher operational barriers even with IP clearance.
• If only one API supplier is qualified, originator supply reliability becomes a bargaining chip in settlements.
• If intermediate supply is constrained, that can delay generic launch regardless of patent timing.

Which geographic suppliers support Rukobia commercial supply?

Supplier geography matters for:

• Cold-chain and logistics requirements (often minimal for tablets, but still relevant for distribution)
• GMP inspection outcomes
• Customs and lead times

Geographic coverage to document in a supplier list

A complete Rukobia supplier map should tag each node by:

• Country of GMP manufacturing
• Role (API vs intermediate vs drug product vs packaging)
• Site status (primary vs qualified backup)
• Change timeline (approval-era vs post-approval additions)

How does Rukobia compare with other HIV attachment inhibitors on supplier structures?

Rukobia is a specific HIV therapeutic category asset (attachment inhibitor) with a unique API chemistry profile. Supplier structures for this category often differ from:

• NNRTIs and NRTIs (often older, more commoditized APIs)
• Protease inhibitors (more complex salt and polymorph control)
• Entry inhibitors and maturation inhibitors with separate synthetic routes

The competitive implication is straightforward: Rukobia’s supply chain is less likely to have commoditized API sourcing and more likely to rely on limited qualified GMP capability for the API and critical intermediates.

Key takeaways

• Rukobia supply is operationally anchored by ViiV Healthcare as the US marketing-facing entity, with API and tablet manufacturing conducted by one or more GMP-qualified contract/affiliated suppliers.
• The most actionable supplier identification approach is to map drug product manufacturing sites first, then trace API and intermediate sites from CMC disclosures.
• Supplier mapping directly affects generic launch feasibility, Paragraph IV readiness, and settlement leverage, through API and intermediate capacity constraints.

FAQs

1. Does Rukobia use a single-source API supplier or multiple qualified sources?
2. Where are Rukobia tablets manufactured (which countries and sites)?
3. Who manufactures fostemsavir key intermediates used in GMP production?
4. How do manufacturing site changes show up in FDA submissions for Rukobia?
5. What supply risks affect fostemsavir continuity compared with other HIV therapies?

References

1. FDA. Drug Label (Rukobia/fostemsavir). US Prescribing Information.
2. FDA. Orange Book: Rukobia (fostemsavir). Approved Drug Products with Therapeutic Equivalence Evaluations.
3. FDA. NDA review and CMC submission records (public access where available for fostemsavir).