Open source, free or hosted: understand the difference.
A £0 licence price and access to source code are different things. This guide helps apprenticeship providers compare ownership, operation, support and total cost before choosing a system.
An open source apprenticeship management system provides source code under a licence that permits specified use, modification and redistribution. A free hosted edition does not automatically provide those rights. Journey Core is a hosted commercial product with a free eligible-provider edition; Journey is not offered as an open-source system.
Ask three separate questions.
First, what does the software licence allow? Second, who operates the system and protects the records? Third, who maintains the apprenticeship-specific workflows as standards, collection specifications and funding rules change?
These questions apply whether you select an open source project, a managed service built on open source components or a commercial cloud platform. The presence of open source libraries inside a product does not make the complete product open source.
| Choice | What it means | What the provider must establish |
|---|---|---|
| Open source, self hosted | Source code is available under its published licence and your organisation arranges operation. | Licence terms, maintainers, deployment, updates, security, backups and support. |
| Managed open source service | A supplier operates software based on an open source project. | What the service contract covers, access to data and code, and responsibility for changes. |
| Free hosted commercial edition | The supplier operates a product with a free tier subject to its published terms. | Eligibility, included features, limits, export options and the route to paid service. |
Check the apprenticeship work, not just the learning screens.
A general learning platform may provide courses, assignments and grades. An apprenticeship provider also needs a coherent approach to programme versions, employers, prior learning, off-the-job activity, progress reviews, funding data, quality and assessment handover.
List those requirements before selecting a codebase or service. Decide which capabilities are already available, which require configuration and which require ongoing development. A repository with recent commits is useful evidence of activity, but it does not prove that your operational requirements are covered.
- Programme and standard versions, including the applicable assessment plan.
- Learner, employer and provider access with clear record boundaries.
- Evidence, off-the-job activity, reviews and change history.
- ILR preparation and a maintained official-submission workflow.
- Backups, recovery tests, updates and a support route.
Build a cost model for the whole service.
For a self-hosted system, include infrastructure, monitoring, backups, security updates, testing, support and the staff time needed to maintain apprenticeship-specific changes. For a hosted system, include subscription terms, migration, training, integrations and any usage charges.
Compare the same period and learner volume. Add the internal work your organisation still owns under each option. A low licence fee can be attractive, but the better decision is the service your team can sustain and your learners can rely on.
Where Journey Core fits.
Journey Core is free forever for verified UK providers with up to 50 counted apprentices, subject to application review. Active learners and learners on a break count towards that limit. The hosted edition provides the connected operational record; Journey Advanced adds Journey AI and the agreed advanced service.
Choose Core because its capabilities and terms fit your provider. If your requirement is a right to inspect, modify and redistribute the complete application source code, a free Core account is not a substitute for an open-source licence.
Make the decision testable.
Choose one programme and a representative learner record. Follow enrolment, planned delivery, learning evidence, a review, a funding return and assessment preparation. Record what works, what needs configuration and what still needs development.
Before committing, agree who will operate the system, how records can be exported and how your team will recover from an outage. These answers are more useful than a broad claim that one licensing model is always better.
See what changes
when it all connects.
Bring your learners’ journey, your team’s questions and your next ambition.