Video Platform Vendor Lock In: What It Costs Universities and How to Avoid It

Ask a university media services team why they are still on their current video platform and the honest answer is rarely that it is the best option on the market. It is that leaving would mean a project nobody has the time, budget or appetite for. Thousands of lecture recordings, embeds scattered across years of courses, quizzes and discussions built inside the vendor's player, and analytics that would vanish on the day of the switch. That is vendor lock in, and in higher education video it is more common than in almost any other part of the campus technology stack.

This guide explains where video platform lock in comes from, what it actually costs, and how institutions can keep their options open without ripping out what already works.

What vendor lock in means for video

In cloud computing, vendor lock in describes the point where moving to another provider costs more than staying, even when the alternative is better or cheaper. The same idea applies to video platforms, with one important difference. In cloud infrastructure the lock in mostly sits with engineers. In education video, it sits inside thousands of courses that instructors and students use every day.

A university video platform usually does four jobs at once:

• Storage and delivery of the video files themselves.
• Integration with the LMS, so videos appear inside Canvas, Moodle, Blackboard or Brightspace.
• Interaction, such as quizzes, comments and assignments attached to a video.
• Reporting, meaning who watched what, how far, and how they did.

When all four live with one vendor, changing the first one means losing the other three. That is the root of the problem.

Where the lock in actually comes from

Embeds and links inside courses

Every course that embeds a video points at the vendor. Some institutions have tens of thousands of these references across current and archived courses. Moving the files is the easy part. Finding and repointing every embed, course by course, is what turns a migration into a multi year project.

Interactions built inside the player

In video quizzes, timestamped discussions and reflection prompts that were built with the vendor's own tools usually cannot be exported in a form another platform can use. Instructors who invested hours building them are the first to object to a switch, and they are right to.

Gradebook connections

Graded video activities are wired to the LMS gradebook through the vendor's integration. Change the vendor and those grade passbacks break, often in the middle of a term.

Analytics history

Viewing and completion data lives in the vendor's reporting. When the contract ends, years of engagement trends usually go with it, which matters for program reviews, accreditation and research.

Training and habits

Faculty learn one recording and publishing workflow. Help desks build their documentation around it. Every switch resets that investment.

What lock in costs

The cost of lock in rarely shows up as a line item. It shows up in three places.

• Renewal leverage. When a vendor knows that leaving would take one to two years, renewal conversations are about how much the price goes up, not whether you stay.
• Duplicate tools. Institutions often pay for a video host and then add separate tools for in video quizzes, video discussion and skills assessment, each with its own contract and integration.
• Migration projects. When a switch does happen, it consumes staff time for a year or more, and instructors lose work they built in the old system.

Four ways to reduce video platform lock in

1. Separate the video host from the learning layer

The single most effective step is to stop treating the video host as the place where teaching happens. If quizzes, discussions, completion tracking and analytics live in a layer above the host, the host becomes a replaceable part of the stack. This is the idea behind a Multi Video Platform: courses connect to one layer, and the video can sit on any host underneath.

2. Keep one LMS integration, not one per vendor

Every vendor specific LTI tool is another integration to maintain and another thing that breaks when you switch. A single LTI 1.3 connection to a platform that works across hosts means adding or replacing a host does not touch your Canvas, Moodle, Blackboard or Brightspace setup. Our LTI 1.3 procurement checklist covers what to require.

3. Own your interaction and analytics data

Ask every vendor two questions in writing: can we export every quiz response, comment and viewing record in a usable format, and what happens to that data on the day the contract ends? If the answers are vague, the data is part of the lock in.

4. Write the exit into the contract

Exit terms are easiest to negotiate before you sign. Ask for data export commitments, a transition period, and clarity on how long recordings stay accessible after termination. Our video platform renewal checklist lists the questions.

Running more than one host is normal

Many universities already run more than one video platform. Lecture capture sits on one service, marketing video on another, and some departments still use YouTube or Vimeo for public content. Lock in thinking usually treats that as a mess to clean up before anything else can happen. It does not have to be. If the learning layer is shared, a mixed estate is simply a fact of life, and each host can be chosen for what it does best.

How Annoto approaches it

Annoto is built so that courses depend on Annoto rather than on any single video vendor. It can wrap the video services you already use, such as Kaltura, Panopto, Brightcove, Vimeo or YouTube, or host and deliver video itself. Quizzes, timestamped discussions, peer review, notes, completion and analytics are stored in Annoto, so they stay in place when a video moves. When an institution does decide to move, the Annoto team runs the transfer, while course links, embeds and LMS integrations keep pointing at Annoto.

You can read how it works on the Multi Video Platform page, or see the full list of supported hosts on Annoto for any video host.

Frequently asked questions

Is vendor lock in always bad?

No. Deep integration with one vendor can be efficient. The problem is when the cost of leaving becomes so high that you can no longer negotiate, choose better tools, or respond when the vendor changes direction.

How long does a typical university video platform migration take?

Institutions commonly plan for one to two years, mostly because of course embeds, rebuilt interactions and faculty retraining rather than the file transfer itself.

Can we reduce lock in without switching vendors?

Yes. Moving interactions and analytics into a host independent layer reduces lock in immediately, even if you keep your current host for years.

Book a demo to see how your current host would sit under Annoto, and what a future switch would look like for your courses.