Content Controller alternatives for content distribution at scale
Content Controller is not a product you consider by accident. Anyone searching for this already has the distribution question clear: one library, many client LMS platforms, licences and reporting per client. Usually there has been a demo already, or a quote is on the table.
Why you are here
In practice there are four reasons to keep looking.
You do not know what it costs. Rustici publishes no pricing for Content Controller. You find out after a demo, by which point you have already invested time.
It is heavier than you need. Per-version changelogs, multilingual equivalents, content analysis down to question level: excellent if you are a publisher with hundreds of titles, overkill if you take fifteen courses to thirty clients.
Your clients are asking for LTI, and that is not where this product comes from. Content Controller can deliver LTI 1.1 and 1.3, so that is not a gap. But the core of the product is dispatch, and if your clients mainly want live connections, that is a different centre of gravity.
You have to explain where the data sits. Rustici publishes no hosting regions for the managed version. Self-hosting is possible, but then you take on infrastructure management too.
If none of this sounds familiar, Content Controller is probably a good choice. It is a mature product with the widest format range in this market.
The five questions that matter at this stage
You are past "what is dispatch". These are the questions that decide it in the quote phase.
Which formats do you genuinely have to deliver?
Content Controller does cmi5 and AICC, which most other products cannot. But that only counts if a client asks for it. Check your client list before you pay for it.
How complex is your licensing model?
If you work with expiry dates, renewals, reusable licences and alerts to your sales team, that is a real requirement. If you work with "this client gets a hundred learners this year", simpler products handle that too.
Who does the work when a new client arrives?
You configure it, or your client picks and downloads through a portal. That makes little difference across ten clients and half an FTE across a hundred.
Where may the data sit, and who manages the servers?
Self-hosting gives maximum control and maximum responsibility. A European SaaS vendor gives you a short answer without the management burden.
How predictable do you want the bill?
Not published, published tiers, consumption in arrears, or an annual bundle. This is a dealbreaker more often than functionality is.
Five alternatives
1. Linqur
Full disclosure: this is our own product. We wrote this page. Read this section with that in mind and verify the rest yourself.
Linqur is a Dutch integration hub for e-learning. You load your SCORM packages and LTI tools once and deliver them as a proxy wrapper (SCORM 1.2 or 2004), as a live LTI tool (1.1 or 1.3 Advantage, with AGS and NRPS), or as a Magic Link for people without an LMS. All three routes run on the same source.
Strong at: LTI as a full route rather than an extra output format, version conversion between LTI 1.1 and 1.3 in both directions (Rustici documents none), licences per client on user count, validity window and allowed domains, remote revocation, servers in an independent Dutch data centre, ISO 27001 and ISO 9001, and a WooCommerce plug-in. Not for you if: you need cmi5 or AICC as a delivery format, want a built-in LRS, or need to self-host. Also not if you want to pull LTI content in and pass it on as an LTI consumer; Linqur is the tool side, not the platform side. Model: consumption per registration where the tier is set afterwards based on actual usage, a credit bundle valid for twelve months, or Enterprise. Quoted per situation.
2. SCORM Cloud Dispatch (Rustici Software)
Content Controller’s lighter sibling, from the same makers. Rustici publishes its own comparison page listing what Dispatch lacks: no per-client account structure, no changelogs, no content analytics, no reporting APIs.
Strong at: you can start today, the pricing is online, and an LRS is included. For a limited number of clients on simple terms this is often enough. Watch out: the tier structure. You pick a monthly bundle of registrations upfront and pay per registration for anything above it. If you do not know how many learners are coming, you either pick too high and overpay or too low and watch the bill climb. This is the most commonly cited reason people come to us. Model: published monthly tiers with overage above the bundle.
3. Rustici Engine with Dispatch (self-hosted)
Not a service but an engine you build into your own application, with Dispatch as the distribution module. Runs on your own servers, in the country of your choice, or through managed hosting.
Strong at: complete control over where the data sits and how it runs, including a conformant LRS for xAPI and cmi5. If you were considering Content Controller for self-hosting, this is the more fundamental version of that same idea. Watch out: this is a build project. You need development capacity to implement and maintain it, and that cost does not show up in the licence price. For a training provider without a development team this is almost always the most expensive route. Model: term licence with initial and annual costs, depending on deployment and learner volume. Amounts not published.
4. scormPROXY (WelcomeNext)
Spanish product, running since 2018, entirely focused on SCORM distribution with licence control. Connectors per product and per client, licences with a duration and a count, distribution to the client LMS, to WordPress through shortcodes or by email. PDF, MP3 and MP4 are converted to SCORM automatically.
Strong at: simplicity, published consumption pricing, a customer portal included as standard, and personal data stored in Germany according to the vendor. If Content Controller feels too heavy, this is the lightest serious alternative. Watch out: LTI is deliberately not supported. WelcomeNext explicitly positions SCORM dispatch as an alternative to LTI. No cmi5, no AICC, no certification documented, and according to their own About us page the content servers sit in Germany as well as the US, Brazil and Singapore. Model: consumption based, billed in arrears, pricing published.
5. SCORM Dispatch (Aptitec)
Small British product that does one thing: dispatch links for SCORM 1.2 and 2004, with permissions, expiry dates, revoking access and per-client reporting.
Strong at: clarity and a published pricing model with monthly and annual plans. Watch out: LTI is not documented, nor is an LRS, and the site says nothing about data centre location. The company is based in the United Kingdom, which is a separate consideration in GDPR conversations since Brexit. Model: published, per licence per month or as an annual plan with overage.
The route that appears in no listicle: replacing your authoring tool
This is not a distribution product, but it is the trade-off we meet most often at organisations already on Content Controller or SCORM Cloud.
The reasoning goes like this. Your clients ask for LTI. Your authoring tool (Articulate Storyline or Rise, Captivate, Lectora) publishes SCORM and not LTI. So you consider moving to an authoring tool that does deliver LTI, such as Easygenerator or Genially.
Three things to weigh before you go that way.
You move the hosting problem, you do not solve it. Your content then sits with your new authoring vendor, with its own costs and a new dependency. Where the data sits and who manages it becomes an open question again.
It affects your whole content team. Switching authoring tools is not a purchasing decision but a migration: existing courses, templates, brand styling, and people who have to learn a new way of working. Licence cost is rarely the expensive part.
You often lose functionality. Tools built around LTI delivery are in practice less advanced in interaction and design than the established authoring packages.
The alternative is keeping your authoring tool and solving the LTI question in the distribution layer. That is exactly what Linqur and Content Controller both do: SCORM in, LTI out, without your content team noticing anything.
The comparison in one table
| Content Controller | Linqur | SCORM Cloud Dispatch | Rustici Engine | scormPROXY | SCORM Dispatch | |
|---|---|---|---|---|---|---|
| Delivers SCORM | SCORM 1.2 and 2004 (3rd, 4th) | SCORM 1.2 and 2004 (2nd, 3rd, 4th) | SCORM 1.2 | Yes | SCORM 1.2 and 2004 | SCORM 1.2 and 2004 |
| Delivers LTI | Yes, 1.1 and 1.3 | Yes, 1.1 and 1.3 Advantage | LTI 1.1 through the UI, 1.3 through the API | Yes | No, by design | Not documented |
| LTI version conversion | Not documented | Yes, both directions | Not documented | Not documented | Not applicable | Not documented |
| cmi5 and AICC out | Yes | No | cmi5 yes | Yes | Not documented | Not documented |
| Built-in LRS | Not documented | No | Yes | Yes | Not documented | Not documented |
| Client portal | Content Portal, standard | In the Enterprise model | Not documented | Build it yourself | Standard | Not documented |
| Licence renewals and alerts | Yes | Manual per client | Per dispatch | Build it yourself | Alert when nearly used up | Expiry and revocation |
| Self-hosting | Yes | No | No | Yes | No | No |
| EU hosting | Not documented | Netherlands | No, AWS United States | Your choice | Personal data in Germany | Not documented |
| ISO 27001 | Yes | Yes, plus ISO 9001 | Yes | Yes | Not documented | Not documented |
| Pricing published | No | No | Yes | No | Yes | Yes |
“Not documented” means the vendor publishes nothing about it. That is not the same as “cannot do it”. Verified on 31 July 2026.
Which one fits you
You need cmi5 or AICC.
Stay with Content Controller, or look at Rustici Engine if you want to self-host. Linqur, scormPROXY and SCORM Dispatch drop out, and that is not a matter of negotiation.
Your clients increasingly ask for LTI and you are stuck on SCORM.
Linqur or Content Controller. The difference is version conversion and data location against format breadth and self-hosting.
Content Controller feels too heavy and too expensive for your size.
Look at Linqur, scormPROXY or SCORM Dispatch, in that order of decreasing functionality and increasing simplicity.
Your clients have requirements on data location and certification.
Linqur (Netherlands, ISO 27001 and ISO 9001) or self-hosted Rustici Engine, where you decide where it runs.
You have a development team and want distribution inside your own product.
Rustici Engine, or a platform with a full API such as Linqur if you would rather skip the building.
You are actually considering replacing your authoring tool to get LTI.
Cost out that migration first and compare it with a distribution layer on top. In most cases the comparison favours the distribution layer.
Frequently asked questions
Book a free demo
Bring your format requirements and your client list. If the answer is Content Controller, we will say so.
All information about third-party products comes from their own public documentation, verified on 31 July 2026. If you spot something that is no longer accurate, let us know.