From product to market compliance. With evidence at every step.
CHERT Regulatory brings products, regulatory cases, laboratory results, documents and CHERT-certified consultants into one bilingual platform — integrated with CHERT ERP, and built around the official SFDA process, never around shortcuts.
One platform for everyone who brings a product to market
Businesses own their products and cases, CHERT-certified consultants bring expertise, laboratories bring results — each in their own workspace, on the same records.
Manufacturers & importers
Keep every product’s regulatory file, evidence and case history in one place, and see what is ready and what is still missing before anything is submitted.
Quality & regulatory teams
Work cases through requirements, evidence and review with clear roles — a signer is never the approver — and a full audit trail.
CHERT-certified consultants
Offer services in the marketplace and work assigned cases under scoped, time-bounded engagements. CHERT Certificate — a private training and assessment certificate issued by CHERT; not a government accreditation or SFDA authorization.
Laboratories
Receive samples, run and verify analyses in CHERTREG Lab, and release certificates of analysis straight into the customer’s regulatory case.
The regulatory lifecycle
Every product follows the same journey — from registration to renewal.
Ten recorded stages, each an event with an actor, a time and a reason. Select a stage to see what happens and which parts of the platform make it work.
01Onboard continuous cycle
Stage 01 / 10
Onboard
Your organisation, your people, one sign-in.
Register the organisation, invite the owner, QA officer and regulatory specialist, and give each the role they need. Everyone signs in once and reaches every workspace their role allows.
Create the product or bring it from CHERT ERP: names in both languages, GTINs, composition and revisions. The CRPN stays the same while ERP codes and authority numbers are kept as references.
Know what is required before you start collecting.
A versioned rule pack turns the product’s category and claims into a requirement checklist. Packs pending a qualified reviewer’s sign-off are labelled as such and cannot freeze a package.
Upload to CHERTREG Documents or link existing files; each link records the source, version, SHA-256 and who linked it. Missing requirements stay visible until they are met.
Register samples in CHERTREG Lab, follow analyses through verification, and link the released report to the case as evidence. A lab release is a laboratory result — never an authority approval.
Expert help from a CHERT-certified consultant, scoped to the case.
Request a service in the marketplace, accept a quote, and the consultant is assigned to the case for the engagement’s duration — access ends when the assignment does.
When the evidence is complete and reviewed, the package is frozen with its rule-pack version, sign-offs and hashes. Any later change creates a new revision; the frozen one stays as it was.
Through the authority’s channel, by your authorized person.
Your authorized person submits through the SFDA’s official channel; CHERT Regulatory records the submission, reference and receipt as evidence. Nothing is submitted automatically.
The authority’s decision is entered from the official document with its source and date. Registrations are then watched for expiry, and renewals start as new cases.
Four separate state machines — so nothing is ever claimed early
Each one answers a different question and is owned by a different party. They are tracked side by side and never merged.
Product readiness
Internal readiness of the product record
1Unclassified
2Requirements known
3Collecting evidence
4Ready for review
5Ready for submission
ExceptionsNeeds rework
Regulatory case
CHERT Regulatory workflow — “submitted” means submitted with evidence, never approved
1Draft
2In progress
3Internal review
4Customer approved
5Submission prepared
6Submitted (with evidence)
7Completed
ExceptionsAction requiredWithdrawn
Official authority status
Changes only when official evidence is attached
1Unknown — pending verification
2Submitted (evidenced)
3Under review
4Approved (official evidence)
ExceptionsRejected (official evidence)
Marketplace engagement
The commercial relationship with a consultant
1Requested
2Quoted
3Accepted
4Active
5Delivered
6Customer accepted
7Closed
ExceptionsDisputed
Interactive architecture
Every layer of CHERT Regulatory — and the component that runs it
Select any component to learn what it does, or play a journey and watch a case move through the platform.
Select a component or play a journey.
01
Data & integrations
Where records live, and the systems CHERT Regulatory talks to — each keeps what it owns.
02
Engines
Proven open-source engines, branded and wired to one sign-in and one set of records.
03
Regulatory Core
CHERT-owned: the regulatory lifecycle, the CRPN and the rules that keep ready apart from approved.
04
Workspaces
One platform, a workspace for each role — Arabic right-to-left and English left-to-right.
S
Identity & trust
One sign-in, isolation in the database, an audit trail that cannot be rewritten.
O
Operations
A platform that watches itself and grants access from one place.
Details appear in the panel above the diagram.
Clear boundaries
Each system owns what it should — and nothing more
CHERT ERP owns product and quality master data. The SFDA owns official outcomes. CHERT Regulatory owns the regulatory cases, the evidence links and the workflow between them.
CHERT ERP
Owns: Products, formulas, batches, quality records
Product & quality data — read through the ERP service API
Regulatory status — written to CHERT Regulatory’s own table only
Package submitted by your authorized person, through the official channel
Outcome entered from the official document, with source and date
SFDA
Owns: Official submissions, decisions, registration numbers
The ERP connection is configured and verified per customer. No government portal is automated and no government credentials are stored.
One platform, many engines
Proven open-source engines around a CHERT-owned core
Each engine does one job well, keeps its own license and attribution, and answers to one sign-in and one set of permissions.
CHERT
Regulatory Core
The CHERT-owned heart of the platform: products and CRPN, cases and their state machines (with embedded Flowable workflow), rule packs, the evidence ledger, the marketplace and the audit ledger.
License: CHERT
Flowable (embedded in the Core)
Case workflow
The workflow engine inside the Regulatory Core: one process per case, pinned to its version.
License: Apache-2.0
Mayan EDMS
CHERTREG Documents
Document management with versions, previews, OCR and cabinets for each organisation.
License: GPL-2.0
SENAITE LIMS
CHERTREG Lab
Laboratory information management: samples, analyses, verification and certificates of analysis.
License: GPL-2.0
Apache Superset
CHERTREG Insights
Interactive dashboards per organisation, isolated in the database.
License: Apache-2.0
OpenSearch Dashboards
Ops Analytics
Health, audit, broker and backup dashboards for CHERT operators.
License: Apache-2.0
Keycloak
Identity
One sign-in for the portal and every engine, with roles per organisation.
License: Apache-2.0
PostgreSQL
Database
The system of record, with row-level security for every organisation.
License: PostgreSQL
SeaweedFS
Object store
Content-addressed evidence files with hashes and encrypted off-site backups.
License: Apache-2.0
OpenSearch
Search
Bilingual search across products, cases and consultants.
License: Apache-2.0
NATS JetStream
Event backbone
Durable events from a transactional outbox to notifications, search and dashboards.
License: Apache-2.0
Inside the platform
Real screens from the running platform
Not mock-ups: captured from the deployed platform with a reference organisation (illustrative data).
Organisation dashboard — products, cases, Lab samples and documents
A regulatory case with its four separate state machines
Lab / LIMS — samples by state, linked to product and case
Documents — every evidence link with source, version and hash
Insights — readiness, cases and official status at a glance
The same dashboard in Arabic, right to left
Why CHERT Regulatory
Built so that every regulatory claim can be traced to evidence
Ready is never approved
Product readiness, case progress, official status and engagement are four separate state machines. No screen can turn “ready” into “approved”.
Evidence you can prove
Versions, SHA-256 hashes, rule-pack versions and sign-offs travel with every frozen package; later changes become new revisions.
Isolation in the database
Organisations are separated by PostgreSQL row-level security, consultants by active assignments — proven by negative tests.
The official channel stays official
No portal automation and no government credentials stored. Submissions are made by your authorized person; outcomes come from the official document.
Your ERP stays the master
CHERT ERP owns product and quality master data. CHERT Regulatory reads it and writes back only its own regulatory status.
Arabic and English, one platform
Right-to-left Arabic and left-to-right English from one codebase, with identifiers that stay legible in either direction.
Bring your next product to market — with evidence.
CHERT Regulatory is opening to businesses, CHERT-certified consultants and laboratories in Saudi Arabia. Tell us about your products and we will set up your organisation.