Linqur vs SCORM Cloud

Three differences matter most. Linqur treats LTI as a full delivery route alongside SCORM and converts between LTI 1.1 and LTI 1.3 in both directions. SCORM Cloud has a built-in LRS and supports cmi5, which Linqur does not. And SCORM Cloud runs on Amazon Web Services in the United States, while Linqur runs on servers in an independent Dutch data centre.

Short version: if you need cmi5, AICC or an LRS, SCORM Cloud is the better fit. If you deliver structurally to European clients across mixed platforms and compliance requirements, Linqur is.

SCORM Cloud delivers content to a client LMS through dispatch. You create a dispatch file, your client uploads it into their LMS, and the content keeps running at Rustici. Their documentation describes that file as a SCORM 1.2 package, an LTI 1.1 connection you create in the interface, or an LTI 1.3 connection you configure through the API.

Linqur runs two products side by side on the same source. SCORM Proxy produces a wrapper your client uploads, at course level or activity level, in SCORM 1.2 or SCORM 2004. The LTI Provider Service delivers the same content as a live LTI tool, with AGS for grade passback and NRPS for users and roles. You pick the route per client without creating a second copy of your content.

Why it matters: if your client base is mixed, some on Moodle or Canvas and some on SuccessFactors or Workday, Linqur delivers both routes from one source. SCORM Cloud can serve both too, with the caveat that its documentation puts LTI 1.3 configuration in the API rather than the interface.

Both products can get people to content without an LMS account. SCORM Cloud does this with invitations, public through a link or private by email, with an expiry date.

Linqur does it with Magic Link. Alongside an expiry date you can cap the number of registrations, restrict allowed email domains, and see per link who started, who finished, with what score and when they last accessed it. A Magic Link is deliberately not an identity provider and does not replace SSO.

Why it matters: for the occasional invitation, both work fine. For a steady stream of externals, freelancers or webshop customers where you want limits per audience, Magic Link is built for it specifically.

According to Rustici’s infrastructure page, SCORM Cloud runs entirely on Amazon Web Services, primarily from the N. Virginia region, with failover to Oregon. That page lists no European region and no data residency statement. Rustici does document ISO 27001, ISO 27701, SOC 2 Type II and TX-RAMP Level 2, and publishes a GDPR page with a data processing agreement available on request.

Linqur runs on servers in an independent Dutch data centre, deliberately not with a hyperscaler. Linqur is ISO 27001 and ISO 9001 certified, for the platform and for the hosting infrastructure. ISO 9001 does not appear in Rustici’s certification overviews.

Why it matters: if you deliver to government, healthcare, education or public tenders, sooner or later someone asks where the data sits. With Linqur that answer is short. This says nothing about SCORM Cloud’s security. It is about where the servers are and which conversation you want to have.

Both use registrations as the unit. The difference is not the price per registration but when you have to commit to it.

With SCORM Cloud you pick a monthly tier upfront: a bundle of registrations, with a rate for anything above it. If you know how many learners are coming, that works fine. If you do not, you either pick too high and pay for air, or too low and watch the bill climb above the bundle. And if your volume fluctuates, you adjust your plan yourself at the start of each month.

This is the point at which most people arrive at our door, and it is almost never about the size of the rate. It is about having to guess upfront. Anyone delivering to the public sector, to large corporates, or from a portfolio where the client sets the pace simply cannot forecast that number.

Linqur uses three models. On the consumption model we look at actual usage at the end of the month and apply the matching tier; you set nothing in advance and there is no penalty afterwards. On the credit model you buy a bundle of registrations at the start of the year that stays valid for twelve months, and you settle per bundle rather than per registration. Enterprise includes all add-ons.

Ask for a calculation based on your own volume in both cases. Individual rates say little until you know how many registrations you create per year and how they spread across it.

Comparison verified on 31 July 2026 against the public documentation of Rustici Software. Third-party product information changes; let us know if you spot something that is no longer accurate.