Muranga OS
Built in Johannesburg
For pharmaceutical manufacturers

From the harvest to the pack, one chain of custody.

Each lot of plant material carries a certificate showing where it came from, who picked it and what the lab found in it. Permits are checked at the moment a harvest is declared. Certificates of Analysis are signed by your QC officer using a hardware key.

NEMBA
BABS permits checked
GS1
GTIN and pack serials
Hardware key
CoA signing
SAHPRA
Submission-ready
What you get

Built for your workflow.

BABS permits checked at harvest

Bioprospecting permits are looked up the moment a harvest is declared. Expired permit or wrong species, the harvest is rejected on the spot.

  • Permit reference required on every harvest
  • Conservation status checked against the IUCN list
  • Sustainable yield caps enforced for you

Lab integration

Your labs send results in by webhook. Results are compared to the spec automatically. Passes go to the QC queue for signing. Fails put the lot on hold and tell the healer.

  • Pulls results from your LIMS
  • Compared against the quality spec
  • Failed lots quarantined and the healer is notified

GMP batch records

Every extraction run, every step in formulation and every operator action is signed and recorded. Batch records can be exported as PDF when an inspector asks for them.

  • Each operator action is signed
  • Chain of custody is tamper-evident
  • Full batch-record PDF on demand

GS1 serialisation

GTIN per lot and a unique identifier per pack. The QR on the pack resolves to a public page with the certificate, but with no personal information about the contributors.

  • GTIN allocated per lot
  • Unique identifier on each pack
  • Public verification page, no personal data

Certificates of Analysis

CoAs are signed by your QC officer with a hardware key, carry your branding and link back to the harvest, the plot and the lab results that produced them.

  • Hardware key signing for the QC officer
  • CoA template branded to your company
  • Each CoA links back to its source data

SAHPRA and pharmacovigilance

Adverse event reports go straight into the SAHPRA template. If you have to recall a batch, you can scope it by the certificate ID instead of by spreadsheet.

  • Adverse event intake forms
  • SAHPRA template populated for you
  • Recalls scoped from the certificate ID

Compliance built in, not bolted on.

BABS, NEMBA, Nagoya and SAHPRA are part of the day-to-day workflow. Your QC team signs the CoAs. We keep the chain.