saascode
education & learning·run 106 · May 2026

ScormRelay

Multi-LMS SCORM and xAPI middleware that versions content distribution and stitches learner completion evidence across two to five platforms without pretending a delivery receipt is a verified learning record.

Genesis score5.57/10
Make ScormRelay real.0/500
500 more votes and ScormRelay is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
2–5Target active LMS estate
8Named target adapters
PreservedCompletion conflicts
The case

The supplied research confirms established content-distribution services, public interfaces for major learning platforms and an unfilled completion-reconciliation gap at the stated scope. It also corrects the license of the proposed browser-automation component. ScormRelay has a credible enterprise wedge after mergers, but each connector must respect customer authorization and platform terms, and reconciliation must preserve conflicting source records rather than manufacturing one clean truth.

Who pays — and why

The learning-platform owner, enterprise learning-operations leader, integration director, or post-merger technology program owner managing several active LMS platforms.

What it unlocks
Versioned one-to-many course packages with per-target compatibility, delivery evidence and rollback history
A canonical learner and assignment map that preserves source identifiers, consent, conflicts and correction provenance
Reconciliation states separating package delivery, launch, learner statement, source acceptance, normalized completion and downstream use
How Genesis scored it
5.57across seven criteria
tension 6temporal 5blindspot 5buyer 5leverage 8convergence 5why-not 5
8
Asymmetric leverage

Adapters and normalized event handling scale, though customer-specific identity and access work remains substantial.

6
Productive tension

Enterprises want one learner record while legally and technically distinct platforms may disagree about identity and completion.

5
Why nobody did it

Fragmented interfaces explain difficulty, but the supplied record does not prove a newly removed barrier.

Why it scored well

The integration gap is specific, major systems expose interfaces and adapter plus reconciliation knowledge can compound.

What's holding it back

Enterprise access, identity matching, platform variance, browser fallback and long implementation cycles make the product materially hard.

Signals detected5 sources crossed
Signalcompetitive research carried in Genesis

Signalproduct research carried in Genesis

Signalcompetitive scan carried in Genesis

Signalintegration research carried in Genesis

Signallicense research carried in Genesis

Direction briefscormrelay.md
scormrelay.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.