Video Hosting Costs for 100,000 Minutes: The Math Most SaaS Teams Miss

Video hosting costs can look wildly inconsistent when a course, SaaS app, or membership library reaches 100,000 minutes of viewing per month. But the apparent gap between Vimeo, Wistia, Kinescope, Mux, Cloudflare Stream, and Bunny Stream is not just about who is “cheap” or “expensive”—it is about whether you are comparing the same unit of usage.

A recent post in r/SaaS argued that paying for familiar video platforms was unnecessary for a course with 100,000 minutes of playback, pointing to Kinescope’s visible pricing and warning founders not to buy enterprise features they do not need. The most useful reply was also the shortest: “Have you tried Mux.com?” That exchange captures the real decision founders face. The answer is not a single vendor; it is a better framework for calculating the total cost of video.

The 100,000-minute video hosting debate

The original Reddit post makes an understandable case: a course creator or SaaS operator may need reliable, private video playback without webinars, advanced team workflows, production tools, sales enablement features, or a large enterprise contract. When that is the use case, a platform whose price is built around broad marketing or collaboration functionality can feel disproportionate.

That frustration is especially common because video-hosting products are not all sold the same way. Some charge a fixed monthly subscription with a bundle of seats, storage, and bandwidth. Others bill directly for video minutes stored and delivered. Still others charge by gigabyte of CDN traffic, which means the final cost changes with playback resolution, bitrate, viewer location, and adaptive streaming behavior.

The Reddit author highlighted Kinescope as an example of a provider that publishes a starting price and emphasizes usage-based infrastructure pricing rather than per-user licensing. Kinescope advertises video hosting starting at €10 per month, with no per-user fees, while positioning its platform for education, SaaS, media, and e-commerce use cases. (kinescope.com)

That does not automatically mean Kinescope will be the lowest-cost option for every 100,000-minute workload. It does mean the author identified a legitimate purchasing problem: founders often compare a visible subscription price against an invisible metered bill, or compare an infrastructure product against a marketing suite without separating the included capabilities.

Why 100,000 minutes is not enough to calculate video hosting costs

“100,000 minutes of views” sounds like a clean input. It is a useful starting point, but it is not a complete cost model.

Before comparing providers, define what the number means:

• Is it 100,000 viewer-minutes per month? For example, 2,000 learners watching 50 minutes each.
• Is it the duration of the hosted library? A catalog containing 100,000 minutes of uploaded video is a very different storage problem.
• Does it include live video? Live events can add ingest, recording, latency, and concurrent-viewer considerations.
• What quality do viewers receive? A 720p lesson and a 4K product demo may consume radically different bandwidth.
• How many distinct videos are stored? A platform’s free tier may cover delivery but cap the number of stored assets.
• Do viewers need access controls? Signed URLs, domain restrictions, DRM, password protection, and SSO can determine the viable vendor before price does.

The key distinction is between stored minutes and delivered minutes. Stored minutes are the length of the source library retained during a billing period. Delivered minutes are the total time audiences actually watch. A 50-hour course library can easily produce 100,000 delivered minutes in a month, while only requiring 3,000 stored minutes.

Cloudflare Stream makes this separation explicit. Its current documentation says it bills for minutes stored and minutes delivered, with encoding and ingress included. Storage is priced at $5 per 1,000 stored minutes, and delivery is $1 per 1,000 delivered minutes. (developers.cloudflare.com)

For a video-on-demand catalog with 3,000 minutes stored and 100,000 minutes delivered monthly, that particular model would produce a simple baseline of approximately:

That is not a universal price quote, nor does it cover optional workflow, player, support, or security requirements. It demonstrates the main lesson: when delivery is metered by viewer-minutes, 100,000 minutes is economically meaningful. When a provider meters CDN traffic in gigabytes, it is only part of the picture.

The hidden variable: bandwidth and bitrate

The word “minutes” can create a false sense of precision. A provider that charges per delivered minute makes forecasting easy because the final resolution does not change the basic delivery unit. A provider that charges for bandwidth requires you to estimate the amount of data each minute consumes.

Here is a deliberately simplified example. If viewers receive an average stream of 2 Mbps, 100,000 minutes of playback equals roughly 1.5 TB of transferred data. At an average of 4 Mbps, the same audience behavior becomes roughly 3 TB. Adaptive bitrate streaming means real usage can land between—or outside—those estimates because viewers may shift between quality renditions during playback.

The calculation is:

Delivered minutes × 60 × average Mbps ÷ 8 = megabytes transferred

Using 100,000 monthly viewer-minutes:

1. At 2 Mbps: 100,000 × 60 × 2 ÷ 8 = 1,500,000 MB, or about 1.5 TB.
2. At 4 Mbps: 100,000 × 60 × 4 ÷ 8 = 3,000,000 MB, or about 3 TB.
3. At 6 Mbps: 100,000 × 60 × 6 ÷ 8 = 4,500,000 MB, or about 4.5 TB.

This is why a course creator cannot safely compare a minute-priced platform with a bandwidth-priced platform by reading only the lowest displayed monthly price. The former may be easier to model. The latter may be cheaper at a particular quality profile—but only if the assumed average bitrate and regional CDN rates match real viewing behavior.

Bunny Stream is one of the providers that separates several usage dimensions, including storage, CDN delivery, DRM licenses, transcription, and encoding tiers. That model can be compelling for cost-sensitive teams, but it demands more accurate usage tracking than a single bundled plan. (bunny.net)

Why Vimeo and Wistia can look expensive—and why that is not the whole story

The Reddit post frames Vimeo and Wistia as costly options. For a narrow “securely host course videos and play them on my site” requirement, that conclusion can be reasonable. Both products sell more than raw video delivery.

Vimeo’s current plans package seats, storage, a no-ad player, privacy controls, collaboration, recording, editing, AI features, marketing elements, and, on higher tiers, live-event tooling. Its listed Starter, Standard, and Advanced plans include 2 TB of monthly bandwidth, with prices starting at $12, $25, and $75 per seat per month respectively; the higher plans also include a larger number of users and additional capabilities. (vimeo.com)

Wistia similarly positions itself as a marketing video platform rather than simply a video CDN. Its Business plan is listed at $79 per month when billed annually and includes three users, 250 GB or more of storage, hosting, analytics, marketing features, and related video-production functionality. Its Automation Suite is separately positioned around using video engagement signals in campaigns and revenue workflows. (wistia.com)

That product packaging matters.

When the higher subscription is rational

A higher-priced platform can save money if it replaces multiple tools or improves a high-value conversion process. For example:

• A B2B marketer may value in-video lead capture, CRM integrations, attribution, and heatmaps more than shaving $50 from monthly delivery costs.
• A distributed content team may need review workflows, role-based collaboration, brand controls, and a polished library interface.
• A company that runs webinars or live events may prefer an integrated workflow over assembling a player, encoding service, analytics stack, and event platform.
• A sales team may use video engagement data operationally, making the platform a revenue tool rather than a hosting utility.

When the subscription is probably overbuilt

The opposite is also true. A founder may be overpaying if the business only needs:

• a branded embedded player;
• reliable adaptive playback;
• private or signed access for paid members;
• basic viewing analytics;
• an API for uploads and video management; and
• predictable delivery at moderate scale.

The practical mistake is not choosing Vimeo or Wistia. It is paying for a broad video-marketing suite while evaluating it solely as commodity hosting. The right question is: Which included features are used often enough to justify the premium over infrastructure-first video hosting?

The Mux question from the community is the right one

The top community suggestion—try Mux—deserves more attention than a one-line reply usually gets. Mux is aimed at developers building video into products, rather than teams looking for an all-in-one content workspace.

Mux currently offers a free tier with 100,000 monthly delivery minutes, up to 10 stored videos, and on-demand video only. Its pay-as-you-go offering includes a $20 monthly usage credit, while paid credit plans bundle additional usage and include 100,000 delivery minutes per month. (mux.com)

For the hypothetical 100,000-minute course workload, that is immediately relevant. A small catalog with fewer than 10 videos may fit the free-tier storage limit, subject to the product’s eligibility and feature constraints. But most serious course libraries will exceed 10 individual videos quickly, which means the free tier should be treated as a development or pilot option—not a guaranteed production cost forecast.

Mux’s bigger appeal is architectural. It provides video APIs and infrastructure-oriented components for uploads, processing, storage, playback, analytics, and workflows. That makes it a strong contender for SaaS products that need video to feel native rather than embedded from a separate creator portal.

Mux is a better fit when

• Video is part of your product experience, not just a marketing asset.
• You have developers who can implement upload, playback, access, and lifecycle workflows.
• You want to control the customer-facing UI while relying on managed transcoding and delivery.
• You expect a need for event-level observability, quality-of-experience insight, or product-specific video logic.
• Usage can fluctuate and a consumption model is preferable to buying a larger bundle in advance.

Mux may be a worse fit when

• You want to upload videos, make a gallery, and launch without engineering involvement.
• Your team’s primary requirement is marketing automation and no-code lead capture.
• You need a highly opinionated webinar or video-collaboration experience out of the box.
• You cannot tolerate variable usage bills without firm internal caps and monitoring.

The community instinct is correct: a developer should put Mux on the comparison list. But “have you tried Mux?” is the beginning of the analysis, not the conclusion.

Kinescope’s appeal: transparent infrastructure without enterprise theater

Kinescope is central to the original poster’s thesis because it presents itself as a middle ground: more video-specific functionality than stitching together raw storage and CDN services, but less seat-based enterprise packaging than familiar video suites.

Its product pages emphasize global delivery, a customizable ad-free player, analytics, access controls, DRM-related protections, live streaming, APIs and SDKs, and use cases including education and SaaS. It also states that it has usage-based pricing and no per-user fees, with plans starting at €10 per month. (kinescope.com)

For an online course, that combination can be attractive. Course operators frequently need branded embeds, domain restrictions, viewer permissions, captions, analytics, and content protection—but do not necessarily need a full marketing-video suite. A video platform designed around those requirements can reduce both cost and implementation time.

However, “transparent” should not be confused with “universally cheapest.” A robust vendor comparison still needs answers to these questions:

1. What precisely is included in the base plan?
2. Is delivery measured in minutes, traffic, or a bundled allowance?
3. Are storage, streaming, transcoding, live recording, DRM, and analytics separately priced?
4. What happens when usage spikes beyond the plan?
5. Are certain delivery regions priced differently?
6. Which security controls require a higher plan?
7. Is support sufficient for a paid course where failed playback means refund requests?

The Reddit author’s broader point holds up: visible pricing changes buyer behavior. It lets a founder model alternatives before entering a sales process. Yet a transparent starting price is only the first line of a usable cost model.

A practical comparison of video hosting models

The best way to compare providers is to first classify them by business model, then assess individual products.

There is no single winner because each model makes a different trade-off between software convenience, implementation effort, feature breadth, and billing predictability.

Cloudflare Stream is unusually easy to model for this use case because its documentation states the stored-minute and delivered-minute rates clearly, includes encoding and ingress, and says bandwidth is included in the delivery charge. At 100,000 delivered minutes, delivery alone works out to $100 before storage. (developers.cloudflare.com)

By contrast, Vimeo’s published plans describe monthly bandwidth allocations in terabytes. That may be excellent value for a low-to-moderate bitrate library, but 100,000 viewer-minutes can cross 2 TB depending on playback quality. A founder needs actual analytics—not just total watch time—to know whether the allowance fits. (vimeo.com)

The overlooked costs beyond hosting

Video delivery is not the entire bill. In many projects, the highest cost is not CDN traffic but the operational work created by choosing the wrong level of abstraction.

Engineering and maintenance

A video API can reduce vendor spend while increasing build work. Someone has to create upload flows, handle failed uploads, manage webhooks, build an admin interface, issue signed playback tokens, map entitlements from billing to access rules, and respond when a customer says a video will not load.

If a developer spends 20 hours building and maintaining a custom workflow that a higher-level platform would handle, that labor can outweigh a year of modest hosting savings. On the other hand, once a product has thousands of customers, native integration can become a strategic advantage worth the investment.

Security and content protection

For paid courses, “private video” is not one feature. It can include domain allowlisting, signed URLs, expiring tokens, password protection, downloader friction, watermarking, DRM, SSO, and granular permissions. The right control depends on the threat model.

A course operator should avoid paying for Hollywood-grade DRM simply because it appears on a feature checklist. At the same time, relying on an unlisted link for a high-ticket certification program may not be enough. Match controls to the value of the content and the likely abuse pattern.

Analytics and business impact

Basic watch counts are easy to obtain. Useful analytics answer harder questions: Which lesson causes drop-off? Which customers never start onboarding? Does completion predict renewal? Did a campaign viewer become a qualified lead?

Marketing-oriented platforms may charge more because they package these answers into accessible workflows. Infrastructure platforms may provide detailed event data but require your team to pipe it into a product analytics or data warehouse stack.

Support, reliability, and migration

Video is a customer-facing dependency. A low monthly rate is less compelling if incident response is weak, documentation is incomplete, or a migration from your existing provider becomes difficult.

Evaluate uptime commitments, support channels, dashboard quality, export options, upload tooling, player customization, and migration assistance. Mux, for example, explicitly markets migration support alongside its infrastructure pricing. (mux.com)

How to build a defensible 100,000-minute estimate

Do not ask vendors for a generic quote first. Build a one-page workload sheet so every vendor receives comparable inputs.

Step 1: Separate the five meters

Record the following monthly figures:

1. Stored video minutes: Total duration of active source videos.
2. Delivered viewer-minutes: Total watch time across all viewers.
3. Average delivered bitrate: Use real player analytics where possible.
4. Number of assets: Include course lessons, trailers, clips, captions, and recordings.
5. Special processing: Live streams, transcodes, captions, translations, DRM, downloads, or AI features.

Step 2: Model normal, high, and spike months

A single monthly average can hide risk. Create three scenarios:

• Normal month: 100,000 delivered minutes.
• Launch month: 200,000 or 300,000 minutes after a promotion, cohort opening, or product launch.
• Spike event: A live session, affiliate campaign, or viral clip that concentrates usage into days or hours.

This matters because some plans have hard limits, while metered platforms keep serving traffic and generate a bigger invoice. Neither behavior is universally better. A hard cap is dangerous if playback stops; a no-cap model is dangerous if you lack billing alerts.

Step 3: Calculate an effective cost per 1,000 viewer-minutes

This normalizes radically different plans:

Total monthly video cost ÷ delivered viewer-minutes × 1,000

If a platform costs $150 per month at 100,000 delivered minutes, the effective delivery-inclusive cost is $1.50 per 1,000 viewer-minutes. If another costs $300 but includes analytics that helps retain two additional customers worth $100 each, the first calculation is not the entire business case.

Step 4: List features as “required,” “valuable,” or “unused”

This simple exercise stops feature-checklist theater.

Then compare prices only among vendors that satisfy every required item.

Which platform type should a course business choose?

For most course businesses with 100,000 minutes of monthly playback, the decision can be narrowed quickly.

Choose an all-in-one platform such as Vimeo or Wistia when your team values speed, polished management tools, marketing features, collaboration, and low operational overhead. Vimeo’s plans include substantial bundled bandwidth and creator-oriented tools; Wistia is more directly aligned with teams that treat video engagement as a marketing and automation signal. (vimeo.com)

Choose Kinescope when you want a course- and platform-friendly video layer with visible entry pricing, security and player controls, plus less emphasis on seat-based licensing. It is particularly worth evaluating when content protection, branded playback, and education workflows matter more than broad creative-suite features. (kinescope.com)

Choose Mux or Cloudflare Stream when video is part of your software product, your team can support an API-based implementation, and you want costs driven primarily by actual usage. Cloudflare Stream is especially straightforward for a watch-time estimate because its delivery price is explicitly per 1,000 viewer-minutes; Mux is a strong candidate when product-level video workflows and developer tooling are central to the roadmap. (developers.cloudflare.com)

Choose a bandwidth-priced service such as Bunny Stream when your team is comfortable forecasting GB delivered, optimizing encodes, and managing a more granular bill. It can be highly cost-effective, but only if you understand actual stream quality and optional feature charges. (bunny.net)

The bigger lesson for SaaS founders

The Reddit post is ultimately less about video than procurement discipline. SaaS founders routinely buy software based on a recognizable brand, an attractive feature grid, or a low introductory tier, then discover their actual unit economics only after usage scales.

Video is an unusually clear example because the units are tangible: minutes, gigabytes, seats, videos, storage, transcodes, and viewers. But the same principle applies to transactional email, observability, AI APIs, authentication, databases, and customer support platforms.

The best operators do three things before choosing infrastructure:

• They translate vendor pricing into the unit that tracks customer activity.
• They identify the features that produce business value rather than merely sound enterprise-ready.
• They model spike usage before the spike arrives.

For a 100,000-minute course library, that means resisting two easy but flawed conclusions: “Vimeo and Wistia are always overpriced,” and “the cheapest usage rate is always the right answer.” Both can be wrong.

A better conclusion is this: pay for the video layer your business actually uses, and make every provider show how its billing model behaves at your real storage, watch-time, quality, security, and growth profile.

FAQ

How much does it cost to host 100,000 minutes of video?

It depends on whether the 100,000 minutes are stored video or viewer watch time. As one current benchmark, Cloudflare Stream charges $1 per 1,000 delivered minutes, making 100,000 delivered minutes about $100 before storage. Other providers may bundle bandwidth or charge by gigabyte, seats, or feature tier. (developers.cloudflare.com)

Is Mux free for 100,000 video minutes?

Mux currently lists a free tier with 100,000 monthly delivery minutes, but it also limits that tier to up to 10 stored on-demand videos. A multi-lesson course library will often exceed that asset limit, so check the current plan rules before using it as a production cost assumption. (mux.com)

Is Vimeo cheaper than usage-based video hosting?

Sometimes. Vimeo includes 2 TB of monthly bandwidth on its listed paid tiers, so it may be cost-effective for a library whose actual data transfer remains within that allowance. But watch-time alone does not determine whether 2 TB is enough; average stream bitrate and video quality are crucial. (vimeo.com)

Why is Wistia more expensive than basic video hosting?

Wistia sells a broader marketing-video product that includes analytics, video SEO, lead capture, integrations, collaboration, and automation options in addition to hosting. It can be worth the premium when those capabilities are used, but may be excessive for simple paid-course playback. (wistia.com)

What is the best way to reduce video hosting costs?

Start by measuring stored minutes, delivered viewer-minutes, average bitrate, number of videos, and required access controls. Then compare providers on total monthly cost across normal and peak months. Lowering unnecessary output quality, removing unused source files, avoiding unused enterprise features, and choosing the right billing model are usually more effective than chasing the lowest starting price.