Compare
Moodle, Canvas, Thinkific and the rest all generate a certificate on course completion. The gap is not generation — it is what happens afterwards.
If your certificates are only ever read inside your own organisation by people with accounts, the LMS module is enough and adding anything is waste. If they are read by someone outside — an employer, a regulator, the learner three years later — the LMS is the wrong place for them, because its certificate is a file in a system that stranger cannot reach.
| The alternative | Here | |
|---|---|---|
| Generated on completion | Yes | Yes, via the API |
| Outlives the account | No | Yes |
| Checkable by an outsider | No | Yes, free, no account |
| Open Badges output | Sometimes 2.0 | 2.0 and 3.0 |
| After the learner loses access | The certificate is unreachable. | The credential is theirs and keeps working. | |
| After the course is deleted | Often the certificate goes with it. | Unaffected — the credential is a separate record. | |
| Expiry and recertification | Usually tracked in a spreadsheet alongside. | A property of the credential; the check page changes on the day. |
| A stranger checking it | No route — they would need an account. | A public check page and a QR code. | |
| Cryptographic signature | Rare, and usually not under your own domain. | Signed under the issuer’s own did:web. |
| Issuing on completion | Built in — it is the same system. | One API call from the LMS, with an idempotency key. | |
| Learner data already present | Yes, no transfer needed. | You send name, programme and date. |
| Certificate layout control | Template-based, often limited. | Your own artwork, fields placed in millimetres. |
A green tick favours this product, an amber one favours the alternative, and a dash means neither. If every row in a comparison table points one way, you are reading an advertisement.
No integration, no second system, no extra cost. If the LMS module covers your need, using it is the correct engineering decision.
Issuing externally means sending a name and a programme to another system. That is a real consideration, especially for minors — and the reason our data processing addendum spells out who is responsible for what.
Two systems is two sets of permissions and two places to look when something is wrong.
The free plan covers a first programme. Talk to us when you are ready for more.