Operational visibility
Manage certificates, jobs, approvals, renewals, and audit activity from one command center.
Issuer operating system
Operating system for inspection and certification teams.
From job to verified certificate — on your brand, your types, your domain. Oryxen runs underneath. The market sees you.
Evidence before the PDFLive registry on your domainDrafts never verify as valid
See Oryxen in action
Structured certificate creation
Create certificates from linked job orders, approved templates, and controlled workflows.
Approval control
Review drafts, submit certificates, and track approval status from one queue.
Live in production
Running every day inside a UAE inspection and certification operation — lifting, access, exams, training, and the calibration path. Productized so another issuer can run the same discipline, on their brand.
3,840+ certificates issued in production
28 live subtypes · 4 families (L / C / T / E)
GCC proof · Pakistan expansion
The loop
Job to verified certificate
One chain. Your brand at the end of it.
- 01
Job
Created, assigned, accepted
- 02
Site evidence
Checklist, photos, dual sign
- 03
Approval
Role-gated. Drafts stay private
- 04
Branded certificate
Your types, your PDF
- 05
QR verify
Live registry on your domain
- 06
Expiry
The next job — or lost revenue
The certificate is the last mile. The liability sits in the chain.
Who it’s for
Issuers, not laboratories shopping an ERP.
The customer remains the issuer. Oryxen runs underneath.
TIC / inspection bodies
Lifting, access, NDT, third-party inspection — job to site truth to signed certificate.
Training academies
Courses, exams, and certificates with the same approval discipline as inspection.
Calibration labs
Calibration path without buying a full laboratory ERP to issue a certificate.
Multi-branch issuers
Same types, same registry rules, local brand on their domain.
Beachhead: mid-size firms still on Word, Excel, and WhatsApp — 10 to 40 people who issue every week and cannot absorb a LIMS project.
Why this, not another QR PDF
Four controls the issuer actually needs.
These are on the platform / rolling out on top of a live issuance spine — labelled honestly.
On the platform
Command home by role
CEO sees control. Engineer sees today’s work. The dashboard is the job description, not one scoreboard for everyone.
On the platform
Trust Ledger
Live verify and exceptions on the home screen — not a sticker QR. Date-change, revoke, issued-without-site-evidence.
On the platform
Cycle control
SLA on the real bottleneck: people and sites. Created → assigned → accepted → site complete → draft → approval → issued.
On the platform
Renewal radar
7 / 15 / 30 / 60-day expiry. Lost renewals with no follow-up job. Sales call list. Expiry becomes the next job.
Fifth, after commercial ships: quotes and invoices on the same job. Until then it stays labelled — not sold as live job-to-cash.
Trust / verify
Public QR. Live registry. Your name on the page.
White-label verify: the customer’s name, the customer’s domain. Oryxen is not the certifier the market sees.
- Scan hits issued, revoked, or not found — current, not a frozen PDF stamp.
- White-label: issuer name on the verify page.
- We are not PNAC / EIAC / ENAS. You hold the licenses and marks.
verify.your-domain.ae
Registry states
IssuedValid on the registry
RevokedMust not pass a gate
Not foundNo record — including drafts
Drafts stay private. A draft never verifies as valid — not as a courtesy, as a product rule.
See if Oryxen fits
Start with a work email — we’ll map your issuance loop
For inspection, training, calibration, and multi-branch issuers still on Word, Excel, and WhatsApp. GCC proof. Pakistan expansion. No generic deck.
Step 1 of 3
Book your certificate workflow audit
Work email preferred — we reply within one business day.
Issuance spine — live
The operating system behind the certificate.
The customer remains the issuer. Oryxen runs the chain: evidence, approval, branded PDF, live verify, expiry.
Job order
Create the job, assign the engineer, accept the visit.
Site evidence
Checklist, photos, dual signatures — captured once in the field.
Role-gated approval
Drafts stay private until the right role signs.
Branded PDF
Your layout, numbering, and letterhead — not a generic template dump.
Live QR registry
Issued, revoked, or not found — on your domain.
Expiry & audit
The chain after an incident, not a buried IT log.
Today
ManualJobs on WhatsApp
Word certificates
Sticker QR, dead link
Expiry in a spreadsheet
With Oryxen
LiveJob owned end to end
Evidence locked to the PDF
Live registry on your domain
Expiry becomes the next job
Never
Drafts verify as valid
Yes
Your brand on verify
You
Accreditation body
From job to verified certificate
The certificate is the last mile. The liability sits in the chain Oryxen keeps together.
Step 1 of 6·Created
Job order
Client, site, type, and scope captured once. Sequential numbering. Assigned to a named engineer — not a WhatsApp ping.
Job order
Engineer
Site
Job owned before anyone leaves the office
What we are not
Clear boundaries keep certificates honest and buyers unconfused.
Not an accreditation body
PNAC, EIAC, ENAS and the rest stay with the customer. Oryxen does not grant marks.
Not a fake-certificate printer
No draft-as-valid. No bypass of approval. No misleading public verify.
Not a lab ERP
No 20-module LIMS. No payroll, inventory, or HR suite required to issue.
Not “AI compliance”
AI is archive intake and search. It does not replace engineers.
On the platformCommercial module
Quotes and invoices tied to the job. Not an ERP.
Aging for the CEO. Export for your accountant. Engineers never see money. We do not claim job-to-cash until invoicing is live in your tenant.
- Quotes and invoices attached to the same job
- Payment aging visible to CEO / admin — not to engineers
- CSV / Excel export to the accountant
- Future handoff: QuickBooks, Xero, Tally
Not in scope
- Not SAP
- Not payroll
- Not inventory
- Not LIMS
- Not HR
Production deployment
Built from a live UAE issuance workflow.
Certificates processed
0+
Certificates issued, approved, and tracked through Oryxen in production — with full audit history on every record.
Active users supported
0
Certificate templates live
0
Workflows configured
0
First certificate issued in
0 hrs
Renewal records tracked
0+
UAE/GCC · Live production
Production metrics · May 2026
Your licenses. Your marks.
We are not PNAC, EIAC, or ENAS.
Oryxen shapes the workflow so your types, approvals, and PDFs can follow the frameworks you already hold. Customers remain the issuer. Oryxen is software.
ISO 17020
Inspection bodies
ISO 17025
Testing & calibration labs
ISO 9001
Quality management
ISO 45001
Occupational health & safety
OSHAD
Abu Dhabi OSH framework
EIAC
UAE accreditation
ADNOC
Vendor compliance
ACTVET
Technical training
Designed for
Inspection & certification teams across these markets
UAEUnited Arab EmiratesKSASaudi ArabiaGCCQatar · Oman · Bahrain · KuwaitPKPakistan
Oryxen is software, not a certifier. Customers hold their own licenses and marks (PNAC, EIAC, ENAS, or otherwise). Oryxen does not grant accreditation, certify equipment, or approve inspectors. Drafts never verify as valid.
Handoff, not a 20-module ERP
CSV/Excel to your accountant today. QuickBooks, Xero, and Tally as a later handoff. Not SAP, payroll, or LIMS.
- CSV / Excel export for your accountant
- QuickBooks / Xero / Tally — planned accountant handoff
- Email notifications and configurable alerts
- iCal feeds and optional Outlook / Microsoft 365 calendar sync
- Web push and PWA-friendly engineer views
- REST APIs for Enterprise tenants
FAQ
Frequently asked questions
Straight answers on what Oryxen is, what it is not, and what is live versus rolling out.
Book a demoNo. Oryxen is software — the issuer operating system. Customers hold their own licenses and marks (PNAC, EIAC, ENAS, or otherwise). We do not grant accreditation, certify equipment, or approve inspectors.
See how issuance would run on your types.
Book a demo. We’ll walk the loop — job, site evidence, approval, branded PDF, live verify — on your certificate families, not a generic deck.
No credit card · 30-minute walkthrough · Google Meet follow-up