Linqur vs Content Controller
These are the two products that genuinely do the same job: managing one content library centrally and delivering it to your clients' LMS platforms, with licences and reporting per client.
In short
Content Controller handles more formats. cmi5, AICC and a wide range of media sources are included, and you can self-host or run it on-premise. Linqur does none of those three.
Linqur is sharper on LTI and on data location. It converts between LTI 1.1 and LTI 1.3 Advantage in both directions, which Rustici documents nowhere, and it runs on servers in an independent Dutch data centre with ISO 27001 and ISO 9001.
The choice usually comes down to one question: is your constraint the format or the platform? If it is cmi5, AICC or self-hosting, Content Controller is the better fit. If it is LTI versions, European data questions or access for people without an LMS, Linqur is.
At a glance
| Feature | Linqur | Content Controller |
|---|---|---|
| Type | SaaS | SaaS, managed hosting or self-hosted |
| Formats in | SCORM 1.2, SCORM 2004, LTI 1.1, LTI 1.3 Advantage, video, files | SCORM 1.2, SCORM 2004, AICC, xAPI, cmi5, media, Zoom, YouTube, Vimeo |
| Formats out | SCORM 1.2, SCORM 2004 (2nd, 3rd, 4th), LTI 1.0/2.0, LTI 1.1, LTI 1.3 Advantage | SCORM 1.2, SCORM 2004 (3rd and 4th), AICC, cmi5, LTI 1.1, LTI 1.3 |
| LTI version conversion | Yes, both directions | Not documented |
| Built-in LRS | No | Not documented |
| Access without an LMS | Magic Link, included as standard | Content Portal, plus Launcher as a paid add-on |
| Client structure | Accounts and licences per client; client portal in Enterprise | Accounts per client, Content Portal per account, audit logging |
| Licence controls | Max users, validity window, allowed domains, remote revocation | Expiry date, learner count, registrations, alerts and renewals |
| Version control | Central updates, one source for every client | Central updates, plus changelogs and republishing earlier versions |
| Multilingual variants | Configured per course | Equivalents: multiple languages in one package |
| Webshop | Linqur WooCommerce plug-in | Not documented |
| Automation | REST API and Webhooks | Automation API and webhooks |
| Hosting | Independent Dutch data centre, EU | AWS in private VPCs for managed hosting; regions not documented. On-premise also available |
| Certification | ISO 27001 and ISO 9001 | ISO 27001, ISO 27701, SOC 2 Type II, TX-RAMP Level 2 |
| Support | Dutch and English | English |
| Pricing | On request | Not published |
Verified on 31 July 2026 against rusticisoftware.com, docs.contentcontroller.com and support.scorm.com.
Formats: Content Controller wins here
Let us start here, because it is the clearest difference.
Content Controller takes in SCORM 1.2 and 2004, AICC, xAPI and cmi5, plus media and sources such as Zoom, YouTube and Vimeo. It delivers as SCORM 1.2, SCORM 2004 (3rd and 4th edition), AICC, cmi5, LTI 1.1 or LTI 1.3. The delivery format does not have to match the source format.
Linqur takes in SCORM 1.2, SCORM 2004, LTI 1.1 and LTI 1.3 Advantage, plus video and files. It delivers as SCORM 1.2, SCORM 2004 in the 2nd, 3rd and 4th edition, and as LTI in all the versions named. No cmi5, no AICC.
Why it matters: if one of your clients requires cmi5 or AICC, the decision is made and it is Content Controller. We are not going to tell you that requirement can be worked around.
LTI: Linqur wins here
Both products deliver LTI. Content Controller is even certified by 1EdTech as an LTI Advantage tool, with Deep Linking, AGS and NRPS, and lets you pick LTI 1.1 or 1.3 per share.
The difference is what happens when the versions do not match. Linqur converts between LTI 1.1 and LTI 1.3 Advantage, in both directions, server side, without changing the source content. If a vendor only ships 1.1 while the platform requires 1.3, the launch still works. Rustici documents no such conversion, in either direction.
Why it matters: this is not a daily problem, but it is a problem that can block a go-live entirely. If you are mid-migration from 1.1 to 1.3 with existing connections that have to keep working, this is why the LTI Converter exists.
Client management and portals
The two products have moved closer together here than they were a year ago.
Content Controller has accounts per client with their own licence types and permissions. You limit by expiry date, learner count or number of registrations, per individual course or across the whole library. Access closes automatically when a limit is reached, you get an alert when a client is nearly through their allowance, and licences are reusable and renewable. Since 2025 there is the Content Portal, where your client picks content, picks a format and downloads it, including as LTI 1.1 or 1.3.
Linqur works with licences per client on maximum users, validity window and allowed domains, with remote revocation. The Enterprise model adds a client portal, LTI 1.3 deep linking with multi-tenancy and per-client reports.
Why it matters: if you want your clients to collect content themselves without involving you, Content Controller currently has the more developed story, and it sits in the standard product rather than a higher tier. If you mainly want to keep control over who gets what, both do that well.
Access for people without an LMS
With Linqur this is Magic Link, and it is part of the product. A temporary link without a password, capped by number of registrations, validity period and allowed email domains, with progress, completion, score and last access visible per link. Built for freelancers, externals, pilot groups and webshop customers.
With Content Controller this runs through the Content Portal or through Launcher, which Rustici documents as a paid add-on for delivery outside an LMS, with shareable links, SharePoint and SSO.
Why it matters: functionally they overlap. The difference is that with Linqur it is in the box and with Content Controller it is partly a separate module.
Selling from your own webshop
Linqur has a WooCommerce plug-in. Order in your own shop, access granted automatically, no more voucher codes. One training provider who set this up removed roughly one day of manual work per week.
Rustici documents no webshop or payment integration for Content Controller. The Automation API does give you a route to build it yourself.
Hosting, certification and the question your client will ask
Content Controller can run three ways: as a web application, through managed hosting at Rustici, or on your own infrastructure. Managed hosting runs on Amazon Web Services in separate private VPCs with a 99.9 percent availability commitment. Which regions are available, and whether there is a European option, is not documented anywhere. Rustici documents ISO 27001, ISO 27701, SOC 2 Type II and TX-RAMP Level 2, with reports available on request.
Linqur runs on servers in an independent Dutch data centre, deliberately not with a hyperscaler, and is ISO 27001 and ISO 9001 certified for both the platform and the hosting infrastructure. ISO 9001 does not appear in Rustici’s certification overviews. Self-hosting is not possible with Linqur.
Why it matters: this is a real fork in the road. If you want maximum control over the infrastructure, self-hosted Content Controller is the only one of the two that offers it. If you want a short, verifiable answer to “where does our data sit” without managing servers, Linqur is.
Speed and support
Most Linqur customers are operational within a day. Support is in Dutch and English, on working days, from people who build LTI connections daily. The biggest challenge with LTI is not building it but connecting it: not every platform implements the standard completely or correctly. Because of the many connections we have already made, most exceptions are known, and small adjustments for a specific client are possible.
Rustici has an extensive, publicly accessible knowledge base and API documentation, which is worth a lot to a technical team. Support is in English.
Where Content Controller is the better choice
You need cmi5 or AICC
as a delivery format. Linqur supports neither.
You have to or want to self-host,
on-premise or in your own cloud environment. Linqur is SaaS only.
You work with multilingual variants of the same course
and want to deliver them as one package. That is exactly what Equivalents does.
You need deep content analysis,
down to question level, including per-version changelogs and republishing an earlier version.
Your clients must be able to collect content fully self-service
and you want that in the standard product.
You are already in the Rustici ecosystem
with Engine or SCORM Cloud and want to keep one vendor.
Where Linqur is the better choice
You deal with different LTI versions
across vendors or platforms, or you are mid-migration from 1.1 to 1.3.
Your clients have requirements on data location and certification
and you want to answer in one sentence.
You regularly deliver to people without an LMS account
and want limits and reporting on that without an extra module.
You sell courses through your own webshop
and want access granted automatically.
You want to go live quickly
without an implementation project, with support that looks along when a platform gets awkward.
You do not want to manage infrastructure
and still want to know where your data sits.
What customers say
"Linqur gave us the ability to share our SCORM packages with clients over the LTI protocol, exactly what we needed."
Celine
Leerhuis Epilepsie
"We were looking for a reliable partner within the Netherlands and found Linqur a good match. The integration went smoothly and the support team really knows what it is talking about."
Henk
Netherlands Forensic Institute
Switching
Your content stays yours and remains exportable. Coming from Content Controller, these are the points to watch.
Format check first.
Are you currently delivering to anyone in cmi5 or AICC? That has to be resolved first, because Linqur does not take it over.
Move the content.
SCORM packages come across as they are. For LTI tools you decide per tool whether they run through the Provider Service or the Converter.
Rebuild clients and licences.
Limits, validity periods and allowed domains get transferred. This is manual work we do together with you.
Switch per client.
The old dispatch keeps working until you replace the wrapper or the LTI connection at the next update.
Frequently asked questions
Book a free demo
Bring your format requirements and your platform list. Half an hour is enough to tell whether this is a Linqur question or not.
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.