Skip to main content
lost·end·found
← Back to SCORMBridge

Support — SCORMBridge

Need help with SCORMBridge? Learn more about the platform or browse the support documentation below.

About the Platform

SCORMBridge is a SCORM distribution platform for publishers. You upload a course once, license it to client organisations, and each client installs a small proxy package in their own LMS. The real course stays on SCORMBridge's infrastructure; every launch validates the licence and reports back to your dashboard.

The platform itself — sign-in, the publisher dashboard and the client portal — lives at scormbridge.app.

Getting Started

  1. Create an account at scormbridge.app/signup. The free plan needs no card.
  2. Upload a course — a SCORM 1.2, SCORM 2004 or xAPI .zip. The manifest is read server-side to detect the version and entry point, and the upload becomes the first version of that course.
  3. License it to a client — pick the organisation, set seats, start and expiry dates, and optionally lock the licence to the client's LMS domain.
  4. The client downloads the proxy package from their portal and uploads it into their LMS like any SCORM course.
  5. Watch launches arrive in your analytics dashboard.

Prefer a walkthrough? Book a demo.

How the Proxy Works

The proxy is a few-KB zip containing an imsmanifest.xml and a launcher page. On launch it:

  • finds the host LMS's SCORM API (API for 1.2, API_1484_11 for 2004),
  • checks its licence key with SCORMBridge (status, dates, seat limit, domain allowlist),
  • loads the real course from SCORMBridge's content storage inside a frame, and
  • relays every GetValue / SetValue between the course and the host LMS, so completion, score and progress land in the client's LMS exactly as if the course were hosted there.

Frequently Asked Questions

Q: Which standards are supported?

A: SCORM 1.2, SCORM 2004 and xAPI / Tin Can. Both SCORM versions have been verified end-to-end on SCORM Cloud.

Q: Which LMSs does it work with?

A: Any LMS that can import a standard SCORM package and exposes the SCORM runtime API — Moodle, Cornerstone, SCORM Cloud and the like. If your client's LMS plays regular SCORM courses, it will play the proxy.

Q: Does the client ever get the real course file?

A: No. They receive only the proxy package. The course content is served from SCORMBridge on each launch through signed, short-lived links bound to the licence.

Q: What happens when a licence expires or I revoke it?

A: The next learner launch is refused by the proxy — no client action required. Suspend, extend or revoke from the licence page at any time.

Q: How do I ship an update to a course?

A: Upload a new version and activate it. Every client sees the new version on their next launch. Nothing needs re-uploading into their LMS.

Q: Does the proxy work if the learner's browser blocks third-party frames or cookies?

A: The bridge talks between the launcher and the course frame with postMessage and does not rely on third-party cookies, so standard cookie blocking does not affect it. Hard corporate firewalls that block scormbridge.app / content.scormbridge.app would need those hosts allow-listed.

Q: What does it cost?

A: There is a free plan, and flat monthly / annual plans above it. Current pricing is on scormbridge.app/#pricing.

Q: Who is responsible for learner data?

A: The organisation operating the LMS is the data controller for its learners; SCORMBridge acts as a processor under the Data Processing Addendum. See our Privacy Policy for a summary.

Q: My course doesn't behave in a client's LMS — can you help?

A: Yes. SCORMBridge is built by lost end found, who build and fix SCORM courses for a living. Get in touch and tell us what you're seeing; our Mac debugger SCORM Lab is often the fastest way to reproduce the problem.

Support Contact

Links