Open Badge 3.0 · signed & portable
Learn it. Prove it.
Every course series on G8Academy ends in a graded assessment and a cryptographically signed credential. Anyone can check it in seconds — no account, and no need to take our word for it.
Verification is public. Learner data is not.
Competency
Secure Laravel Application Delivery
- Issuer
- Developers Hub Sdn Bhd
- Assessment
- Graded · 86%
- Standard
- Open Badge 3.0
urn:uuid:8f2c…4a91
Example of an issued credential.
Built on open standards, not lock-in
- Open Badge 3.0
- LTI 1.3 · Moodle & Canvas
- REST API
- SSO · SAML & OIDC
- WCAG 2.1 AA
Four steps from lesson to proof
Nothing is issued on attendance. A credential exists only after the work has been graded against a published rubric.
-
01
Learn
Work through a course series of video episodes, with captions on every one and notes that stay with you.
-
02
Be assessed
Sit the assessment that closes the series. Practical work goes to a human assessor and a published rubric.
-
03
Earn the credential
Pass, and the issuer signs an Open Badge 3.0 credential with its own key. Yours to keep and to carry.
-
04
Be verified
An employer checks the signature against the issuer's published key — no account, no login, no call to us.
One platform, six consoles
Learners, instructors, assessors, organisations and issuers each get a workspace scoped to what they are actually responsible for.
Learners
Study, sit assessments, and hold a wallet of signed credentials you can share as a link, a PDF certificate or the badge file itself.
- Course player with captions
- Personal notes
- Credential wallet
Instructors & assessors
Author series and versions, build rubrics and assessments, and grade practical submissions from a single queue.
- Series & version editor
- Rubric builder
- Grading queue
Organisations & issuers
Enrol cohorts, launch from Moodle or Canvas over LTI 1.3, pull progress through the REST API, and hold your own signing keys.
- Cohorts & SSO
- LTI 1.3 launch
- Signing keys & revocation
For employers & registrars
Check a credential without trusting us
Paste the ID, upload the badge file, or scan the QR on the certificate. The signature is checked against the issuer's published key, so a tampered badge says so — even for a credential we hold no record of.
Open the verifier-
Paste an ID or link
urn:uuid:… or the verify URL from an email signature.
-
Upload the badge file
The Open Badge JSON, checked cryptographically and offline of our records.
-
Scan the certificate QR
The QR on the PDF certificate opens the verification page directly.
Start with one series
Preview the first episode of anything in the catalogue before you pay for it.