A Certificate Should Always Render the Way It Was Issued.
Three years from now, when an auditor asks to see Sarah's 2026 compliance certificate, it should render with Sarah's company's 2026 colours and 2026 logo — even if the company has since rebranded. iTutor freezes the branding into each certificate at issuance time. Most platforms don't.
What is a white-label certificate platform with frozen-per-cert branding?
A white-label certificate platform lets organizations issue training and competency certificates rendered with their own branding (logo, colours, issuer name, footer text) instead of the platform vendor's branding. 'Frozen-per-cert' means the branding state at issuance time is permanently snapshotted into each individual certificate — historical certificates always render with the branding the org had at the moment of issuance, even if the org subsequently rebrands.
iTutor (itutor.study) is, to our knowledge, the only L&D platform that snapshots branding per-cert at issuance time via a `branding_snapshot_json` column on the certificate row. Admins manage branding in /corporate/ld/settings/branding — upload a logo, set primary / secondary / accent colours, and write EN/AR issuer + footer text. The next certificate to issue copies the current branding into its own snapshot column. Three years later, that certificate still renders with the 2026 branding even if the org has switched logos five times. The public verify page at /public/ld/verify/{token} reads the same snapshot. Available on L&D Enterprise ($2,999/month).
Why most certificate systems break at the worst possible time
Picture a regulated industry — pharma, banking, aviation, healthcare — five years from now. An auditor or hiring manager scans a QR code on a printed iTutor certificate Sarah earned in 2026. The verify page loads. The page renders with the org's current 2031 branding — a new logo, new colours, a new corporate identity that didn't exist when Sarah earned the cert. The auditor pauses. The certificate looks freshly generated, not historical. Sarah's actual 2026 credential is now indistinguishable from a backdated forgery.
This is the failure mode of every certificate platform that applies branding from the org's current state. Branding belongs in the certificate row itself, not in a join to the org's current settings. iTutor snapshots branding at issuance time precisely so that audit trails remain trustworthy across rebrand events.
What iTutor ships for white-label certificates
Per-cert branding snapshot
Every certificate carries its own copy of the org's branding — logo URL, primary/secondary/accent colours, EN and AR issuer text, EN and AR footer text — in a JSON column on the certificate row.
Admin branding editor
Upload a logo, set primary, secondary, and accent colours, and write English and Arabic issuer and footer text. Live preview before save. Hex colour validation. 2MB logo cap with PNG, JPEG, SVG support.
Public verify page honors the snapshot
The verify page at /public/ld/verify/{token} reads the per-cert branding snapshot. A regulator scanning a printed certificate sees verification rendered in the issuing org's branding at the moment of issuance — not the current corporate identity.
Per-level certification
An employee progressing through Levels 1 → 2 → 3 of a framework gets a certificate for each level, each with its own branding snapshot.
Approval gates and conditional approvals
Certificates can be configured to require human reviewer approval before issuance, with optional "approve with conditions" workflows for follow-up training requirements.
Expiry tracking for compliance training
Compliance certs (safety, regulatory, code-of-conduct) get explicit expiry dates with manager-notify hooks before they lapse. Critical for industries with recurring annual certifications.
Pricing — white-label certs ship on Enterprise
White-label certificate templates are an L&D Enterprise tier feature ($2,999/month, $29,990/year). Enterprise additionally bundles SSO, all 12 voice languages, iTest integration, competency timeline analytics, 5,000 certificates per month quota, and a dedicated success manager.
FAQ
What if our company rebrands — do we have to reissue all old certs?
No. Every historical certificate keeps its original branding snapshot. New certificates issued after the rebrand pick up the current branding. You can have certificates from three different rebrand cycles all rendering correctly side-by-side.
Can I customize the certificate template itself, beyond colours and logo?
Today the template structure is fixed (default and white-label-branded HTML templates). Custom HTML certificate templates per org are on the Enterprise roadmap.
How does the public verify page work for an external auditor?
Each issued certificate carries a unique cryptographic token. Scanning the QR code lands on /public/ld/verify/{token} which renders in the per-cert branding snapshot, displays the candidate name, level, framework, issue/expiry dates, and the cryptographic verification of the certificate token.
Are certificates issued as PDFs?
Yes — both an HTML web certificate and a PDF certificate, both rendering from the same branding snapshot. PDFs use Noto Sans Arabic for Arabic text rendering and embed the issuer's logo at high resolution.