Clear comparisons. Inspectable sources.
See how the comparison is assembled, what each label means and where to inspect the official evidence.
Journey’s comparisons are supplier-authored, evidence-linked evaluations of specific buyer workflows. They distinguish documented capability, scope that needs checking and details not established by the reviewed sources. Missing public evidence is never treated as proof that a feature does not exist.
A comparison of specific work, with the evidence attached.
This comparison is published by Journey to help apprenticeship providers evaluate the platform. It is a supplier-authored comparison, not an independent ranking, laboratory test or certification. We compare tasks that matter to providers, learners, employers and assessment teams, using official supplier documentation and reviewed Journey implementation and release records.
The current matrix was reviewed on 9 September 2026. It covers Aptem, Bud, OneFile, OneAdvanced and Tribal MAYTAS. OneAdvanced references are limited to the suite, AI offer or product named by the source. Do not assume every suite feature is included in every standalone PICS or Smart Assessor contract.
What the labels mean.
Documented means an official source describes the capability in the stated scope. It does not mean our team has tested the supplier’s platform or that the feature is included in every package.
Scope matters means a related capability is documented, but the exact workflow, package, setup or acceptance evidence needs to be confirmed. For Journey, this label also identifies controlled migration and assessment-connection work with important setup and verification boundaries.
Confirm in your demo means the reviewed public sources do not establish the exact capability being compared. It is not a cross, a claim that the supplier lacks it or proof that Journey is uniquely capable.
Supported workflow identifies a Journey capability supported by the implementation or release documentation reviewed. It is not a promise that every customer has the same configuration, that a current live acceptance test has been completed or that the public website demonstration uses real customer data.
Compare like with like.
Use the same standard, role, data example and expected result in each supplier demonstration. Distinguish a learner assistant from provider-wide operational retrieval; a record citation from a general explanation; a reusable template from a generated plan; and a supported profile import from a complete historic migration.
For assessment, name the receiving platform and organisation. Check the fields and files in the pack, the approval, receipt, corrections, status updates and released result. Aptem publishes a Proficient integration and OneFile lists EPAPro and Summit connections. Journey’s native Meritura exchange is therefore evaluated on its specific workflow and controls, without claiming it is the only assessment integration.
For identity and infrastructure, ask for configured controls and service evidence. Clerk, Neon and Cloudflare R2 are parts of Journey’s reviewed architecture. Other suppliers use their own managed services, and Bud publicly documents Cloudflare and Supabase use. A technology name does not establish a security or scalability advantage.
For price, ask for a written scope including licence, implementation, migration, support, AI, storage, connections, annual changes and exit. Journey Core’s free licence applies to verified UK providers with up to 50 counted apprentices and the published conditions. Advanced is quoted per provider. Do not compare a restricted starting package with another supplier’s full service.
How Journey’s evidence is treated.
The Journey review examined conversational record access, programme import, draft learning and delivery builders, session resources, the Aptem migration route, native Meritura exchange and the recorded Neon, Clerk and R2 architecture. Source implementation, targeted tests, release documentation and a live customer acceptance test are different forms of evidence.
Implementation supports explaining the workflow. The release record can report a deployment. Neither is a substitute for demonstrating the configured workflow with the organisation’s authorised users and data. The website’s conversations, learner records, animations and handover examples are illustrative. Consequential decisions remain with named people.
The Aptem route is a staged, reviewed import for its supported profile scope. Dedicated direct Bud and OneFile importers were not confirmed. The Meritura connection uses versioned native HTTP/events; a current live default MCP pairing is not established by the reviewed evidence. These boundaries remain visible beside the relevant claims.
Source review and corrections.
Each supplier cell links to the official page used. Source notes below explain the scope or limitation that matters. A supplier may change its product, package or documentation after review. We refresh the comparison when the relevant information changes and record the review date. This is an editorial process, not a claim that an automated system continuously verifies every cell.
Every source in this comparison is re-checked on a 30-day cycle: each source’s access date, the matrix’s overall review date and its next review date are all recorded. The two headline dates, when the matrix was last checked and when it is next due, are published machine-readably at /comparison-evidence.json so they can be verified independently of this page.
If a detail is inaccurate or incomplete, use Contact Journey and identify the row, supplier, current official source and correction you propose. We assess the evidence and amend the comparison where appropriate. Supplier silence, an inaccessible page or an older deployment is never sufficient reason to mark a capability as absent.
Journey’s editorial team is responsible for maintaining this comparison. Read our editorial approach. A named independent practitioner review, customer outcome study or certified security assessment will be identified separately when such evidence exists.
Journey’s platform controls
Every Journey alternative page links back here for the detail on how Journey itself is built, rather than repeating it on each page. The controls below apply across Journey, not to any one competitor comparison.
Tenant-scoped access controls
Tenant-scoped access controls are designed to keep each provider’s records separate on reads and writes.
Controlled audit history
Significant application state changes are recorded against the person who made them, supporting a traceable history.
Published funding-rule packs
Journey applies supported, versioned DWP funding-rule packs selected from the apprentice’s start date, including 2026/27 version 3, to support provider review.
Bounded AI assistance
Use the same operational question in any product demonstration. Ask which records the assistant can read, whether sources can be opened, which edition is required and which actions remain subject to approval.
Evidence-led security controls
Tenant isolation, access controls, audit records and governed operations are designed into the platform.
Your data and employers stay yours
Export options are available under the applicable terms, and employer relationships remain with the provider.
Journey is independent software and is not DWP, DfE or Ofsted approved. It does not guarantee funding or inspection outcomes.
Official supplier sources.
Aptem
- AVA overview
Enterprise learner assistant; live learning-plan, review and action context. Read-aloud is early access. Does not establish unrestricted provider-wide operational querying. Reviewed .
- Aptem Enhance
Embedded learning, marking and review AI. Tutor-visible conversation history and human review described. Do not infer response-level source citations from audit history. Reviewed .
- Proficient/epaPRO integration overview
Automatic registration and learner updates; assessment records return hourly or daily by configuration. A specific integration, not universal AO interoperability. Reviewed .
- Proficient integration setup
Requires active account, per-AO connection and standard/specialism mapping. Help labels it an add-on; current pricing lists integration quotas, so confirm commercial scope rather than resolving ambiguity in Journey's favour. Reviewed .
- CSV learner import
Documented bulk learner CSV import with validation, duplicates review and results. Does not establish full historical evidence migration. Reviewed .
- Programme Builder
Existing programmes can be cloned and customised; tokens configure learning plans, documents, reviews, workshops and ILR. Direct standard-to-complete-programme generation was not established. Reviewed .
- Apprentice product
Published unified delivery, integrations, resource centre, Teams event workflow, SSO and MFA/MFV. A general calendar/resource claim alone is not an exclusive Journey difference. Reviewed .
- Apprentice pricing
Essentials, Pro and Enterprise with quote-based prices; service tiers and add-ons. Historic ILR transfer has per-year charges. Do not read missing visual ticks in extracted tables as absent features. Reviewed .
- June 2026 release notes
Documents maintenance of Skills England standard minimum-hour data. Reference-data maintenance is distinct from one-click curriculum generation. Reviewed .
Bud
- Bud Assist
Assistant and Insights use delivery-system context and real learner data; trainer drafting, reviews, activities and risk signals. Broad marketing scope is wider than the older trainer-chatbot support article. Reviewed .
- Bud Assist for Trainers
Enterprise trainer chatbot: funding/standards guidance, feedback and support planning. The article alone does not prove cross-record operational retrieval. Reviewed .
- Getting started with Bud Assist for Learners
Embedded learner chat uses programme, activities, progress and criteria. Supports follow-ups and chat history controls; cannot produce assessment answers for learners. Reviewed .
- Bud Assist for Learners webinar FAQ
Published limitation: assistant cannot open files, hyperlinks or SCORM content; can signpost. Trainer conversation view described as in development. These limits apply to this learner assistant, not every Bud AI feature. Reviewed .
- FAQs
Standards-mapped programme templates; Standard Migration uses ILR plus additional extracts; Advanced Migration is bespoke. Per-learner enrolment and monthly charges described. Full archive migration scope requires agreement. Reviewed .
- Creating a programme for standards
Users search/select standards and configure programmes. Provider must first request needed standards/qualifications; exact generation step count is not established. Reviewed .
- EPA Overview
Gateway checklist, sign-off, assessment log and automatic learner/ILR updates after an outcome is logged. A named external AO transfer and automatic released-result return were not established here. Reviewed .
- Technical and compliance information
Azure, Supabase for Bud Mark, Cloudflare edge; scaling, backups, MFA/SSO, encryption, tenant filtering, security testing and ISO27001 described. Bud-hosted data in UK; page notes subprocessors may process elsewhere. Vendor logos cannot establish Journey superiority. Reviewed .
- MFA Overview
TOTP MFA documented with Premium-plan condition; confirm current package and user coverage. Reviewed .
- Activity configuration
Reusable activity library and manually authored activities; this article specifically concerns OST programme configuration, so do not apply every detail to apprenticeships. Reviewed .
OneAdvanced
- AI for Education
Intelligent Chat for authorised assessors, curriculum, finance and leaders uses on-screen records. Subscription includes contextual input and plan/activity agents; evidence-feedback and OTJ-checker workflows described. Do not credit every standalone PICS/Smart Assessor licence automatically. Reviewed .
- Apprenticeship Management
Unified PICS/bksb/Smart Assessor experience; SSO/MFA, migration support, standards configuration, AI activities/review summaries. Standalone products remain available; suite scope matters. Reviewed .
- ePortfolio (Smart Assessor)
Gateway tools, evidence portfolio, personalised ILPs, OTJ and connections to PICS/bksb/ProMonitor. Exact AO pack transfer/released-result loop not established. Reviewed .
- Learner Management System (PICS)
Core MIS/ILR and progress management; connects with Smart Assessor/bksb. Do not confuse standalone MIS scope with full Apprenticeship Management subscription. Reviewed .
Tribal
- MAYTAS for training providers
MAYTAS 6 with ePortfolio, learner/staff/employer hubs, SSO to learning resources, ILR and OData read/write connectivity. No record-chat or direct Skills England generation established in reviewed page. Reviewed .
- MAYTAS Hub
Gateway tracker/showcase portfolio, scheduled skill scans, evidence review and IQA. Not proof of a named external AO transfer and released-result return. Reviewed .
What we checked in Journey
The Journey entries combine a review of application implementation and release records with the public product descriptions linked from the comparison. The implementation review was completed on 9 September 2026. It establishes how a supported workflow is represented in the reviewed application; it does not establish that every organisation has enabled it or passed its own production acceptance checks.
The website demonstrations use synthetic learner information. They explain the intended sequence without connecting to your live workspace, importing a provider’s data or sending a real assessment pack. A demonstration is useful for understanding the interface. Organisation-specific acceptance requires the real permissions, configuration and representative records agreed with your team.
Conversational answers
We checked the native Vercel AI SDK integration and the application-controlled tools used by Journey AI. The reviewed tools apply provider and role boundaries and return supported facts, evidence references, as-of information and routes into the relevant work. The comparison does not promise unrestricted database queries, perfect answer accuracy or an immutable copy of every source record. In your walkthrough, ask which tool and records support the answer, then repeat the task with a user whose access is narrower.
Programme, learning plan and delivery
We checked the flow from a selected Skills England standard and version into a draft programme; the learning-plan builder’s use of a published programme; and the delivery builder’s use of plan and schedule inputs. The reviewed source includes focused integration cases for the plan builders. These are development evidence, not a claim that this website review reran the whole live application test suite. Your acceptance should inspect the imported provenance, draft structure, KSB context and resulting dates, including how a tutor changes the draft before approval.
Calendar-linked resources
We checked session details for joining information, attached resources and inherited module materials, together with authorised file access. The useful question is whether a learner can reach the material for the next session using their own role. Check a session with attached resources, one without them and a user who should not have access. The comparison does not imply automatic discovery of files elsewhere in your organisation or confirmed external calendar synchronisation.
Migration and assessment exchange
We checked the Aptem-specific read-only connection, sample, mapping, preview, duplicate checks and staged application. Supported profiles are narrower than a complete provider history. We also reviewed the native Meritura exchange for versioned packs, integrity information, named approval, receipt and correction/result events. Neither review substitutes for reconciling the first authorised Aptem sample or pairing and testing the receiving assessment organisation. Those checks belong in the written implementation acceptance plan.
Infrastructure and operational assurance
We checked the release-record descriptions of Neon database hosting, Clerk identity and Cloudflare R2 file storage, and the application boundaries associated with them. We have not turned a supplier’s certification, regional product option or scalability claim into a Journey certification. Ask for Journey’s current configuration, contractual data locations, access policy and operational recovery evidence. A modern infrastructure component is useful only when the service around it is configured, tested and maintained for your needs.
Record the result of your own comparison
For each priority, keep the exact task, product and edition, date, participating role, data used, expected outcome and observed outcome. Mark a task as accepted only when the agreed evidence is available. Record limitations and work still required alongside the result, with an owner. This creates a decision record your delivery, quality, finance and leadership teams can revisit, instead of relying on a favourable screenshot or an unexplained tick.
“Not located” describes the evidence reviewed.
A feature may exist without appearing on the pages we inspected. Our comparison therefore names the reviewed sources and their dates. “Not located in reviewed pages” means that the exact workflow or configuration was not established by that public material; it does not mean the supplier lacks it. Some suppliers provide additional evidence through a Trust Centre or during procurement.
We compare equivalent outcomes and configurations. Cloudflare on a public marketing website does not establish its use for the signed-in product. OWASP secure-development practice is not the same as deploying the OWASP Core WAF Ruleset. A ruleset in logging mode is not blocking. Bud explicitly documents Cloudflare, OWASP, DDoS and rate limiting, and the comparison recognises that.
The additional security review was completed on 10 September 2026. Earlier capability references retain their individual 9 September review dates. Journey’s own column distinguishes source implementation, automated tests and dated operations records from independent live acceptance. Supplier names and their modules remain separate: Tribal MAYTAS is not OneAdvanced.
See what changes
when it all connects.
Bring your learners’ journey, your team’s questions and your next ambition.