Gumlet vs Cloudflare Stream

The real split: a selling host against raw delivery

These two get shortlisted together because both host video, hand you an embed and stream it worldwide. What they were built around is not the same thing at all. Gumlet is a managed media platform: it hosts and streams your video, protects it with DRM, carries in-player calls to action, lead forms and pixels, and on the same account optimizes the images on your website, serving AVIF and WebP to speed up your pages. Cloudflare Stream is developer infrastructure. You drive it through an API, it encodes and delivers on the world's largest network, and everything above the raw video, the selling, the tracking, the dashboard a marketer would use, you build yourself.

That difference decides most of what follows. Gumlet suits a marketer or a small product team that wants fast, protected playback, a selling layer that works out of the box and a bill they can read, and who may also want to speed up a content-heavy website. Cloudflare suits a developer who wants cheap, dependable global delivery and live streaming on one API and is happy to wire the rest by hand. Ask who will maintain the video and whether the clip has to sell on its own, and the pair usually sorts itself.

Where they actually differ

What comes in the box. Gumlet gives you adaptive streaming, a clean ad-free player, live streaming, AI subtitles and chapters, one-click DRM, and the thing no rival here matches: an image-optimization CDN that shrinks and reformats your site images automatically. It also has in-player CTAs, lead forms and Google and Meta pixels, so a video can capture an email or push a click without a second tool. Cloudflare Stream gives you resumable upload, automatic adaptive-bitrate encoding, HLS and DASH output, a customizable player or your own, and live streaming over RTMP and SRT, all through one API. What it does not give you is any selling layer at all. No CTA on the timeline, no form, no pixel, no marketing dashboard. For a seller, that is the gap that matters; for a developer building video into a product, the clean API is the whole appeal.

What you pay for, and how. This is the sharpest line, and the two make opposite bets. Gumlet meters storage and bandwidth against published plans, with a free-forever tier and paid plans from $6 a month on annual billing, and it bills bandwidth past your allowance per gigabyte. Cloudflare charges $5 per 1,000 minutes stored and $1 per 1,000 minutes delivered, with encoding and bandwidth included, so the bill is flat and legible per minute no matter the file. The catch for this audience is that Cloudflare's per-minute meter ignores bitrate: a 480p talking-head VSL costs the same per delivered minute as a 4K film. That is the exact profile most selling video fits, low bitrate watched by a large audience, and it is where Gumlet's per-gigabyte model is dramatically cheaper. The full worked example is in the pricing section below; the short version is that light files served to a big audience are punished by a per-minute meter and rewarded by a per-gigabyte one.

Keeping the video protected. Gumlet has the edge here for premium content. It offers certified Widevine and FairPlay DRM as a one-click $99-a-month add-on, plus dynamic watermarks, domain and geo restrictions and signed URLs on the standard plans. Cloudflare Stream relies on signed URLs and token authentication rather than studio DRM, and forum users report that shared signed links get handed to third-party players. For casual gating either is fine. For course video that genuinely must not leak, Gumlet's certified DRM is the stronger base and Cloudflare will have you building more of the protection yourself.

Reliability and reach. Here the advantage flips to Cloudflare. Stream runs on the same infrastructure that carries a large share of the world's web traffic, so playback holds up globally and under load without you managing a CDN, and developers on Hacker News call it an honest, well-run paid platform, if a touch expensive for on-demand. Gumlet scores extremely well in aggregate, around 4.7 across 357 G2 reviews and 4.9 across 202 on Capterra, and reviewers praise fast playback and value. But there are documented reliability incidents: a community thread where every embed on an account returned a dashboard-only error, and AppSumo buyers reporting an outage with no fix ETA and slow support when it broke. Whichever you pick, keep your own master files and test playback where your buyers actually are before you migrate.

Selling features, and the thing to be clear about. Gumlet covers the basics of making a video sell: CTAs, forms and pixels in the player. Cloudflare does none of it, by design. But it is worth being precise about the ceiling on both. Neither carries a per-second retention curve split by buyers and non-buyers, neither runs split tests decided on sales, and neither ties a play to a cart-verified sale or fires that confirmed sale back to the ad platforms server-side. Capturing an email and firing a pixel on a page load is engagement and retargeting; it is not revenue attribution, and that is a different job again.

If the video's job is a direct-response sale: TrackPlay

There is a third situation neither of these was built for. If your video is a VSL running on cold paid traffic, and the only number that matters is whether the play produced a sale, TrackPlay is aimed straight at that job. Where Gumlet shows you view counts and Cloudflare confirms the file was delivered, TrackPlay hosts the video behind one embed and ties every second watched to who actually bought, then posts the cart-verified sale back to Meta, TikTok and GA4 server-side, onto the play that earned it. It is built to tell you which ad, which play and which cut of the video produced revenue, which is a different job from hosting or moving bytes.

It backs that with a player made for cold traffic, sound-first autoplay, timed CTA cards and watch gates, per-second retention split into buyers versus non-buyers with the pitch moment marked, and split tests decided on real sales with statistical significance rather than on views or clicks. Billing is on plays, not bandwidth or minutes, every feature ships on every paid plan from $29 a month, and there is a no-card free plan of 1,000 plays a month, watermarked, plus a 14-day trial of the paid features.

The catch is real, and it is the flip side of that focus. TrackPlay is narrow by design: built for paid-traffic VSL conversion, it is not a general video host or a B2B content library, so it has none of the channels, SEO pages or webinar tooling of a marketing platform like Wistia, and it is a poor fit if the video's job is content marketing rather than a direct-response sale. If you are serving course lessons, optimizing site images or delivering a large public media library at the lowest possible cost, Gumlet or Cloudflare is the right home and TrackPlay is not for that work. It is also a very new product with thin outside proof: the testimonials are on its own site, there is little third-party review footprint yet, and signup is currently invite-only, which is what you would expect of a platform this recent. Weigh it when the sale, not the view, is the goal.

Read our full TrackPlay review for how the attribution and split testing hold up.

Which one for you

Choose Gumlet if you want a managed host with a bill you can read, a selling layer working out of the box, and content protection strong enough for paid courses, and especially if you also run a content-heavy website that the bundled image CDN can speed up. The entry price is low and the aggregate review scores are among the best on this site. Pilot it first and set usage alerts, because the reliability incidents and metered bandwidth are the two things to watch.

Choose Cloudflare Stream if you want cheap, dependable global delivery and live streaming on one API, you are comfortable driving it through code, and you will build the CTAs, lead capture and tracking yourself. It suits high-bitrate content, live at scale, and teams already inside the Cloudflare ecosystem. Just do the per-minute math against your view count first, because for light files served to a big audience it adds up fast, and remember it will not sell the video for you.

Choose TrackPlay if the video is a VSL on paid traffic and you are measured on sales: you want the play tied to the cart and the conversion fired back to the ad platforms, not a view count or a delivery log.

Pricing, compared

The two bill on completely different axes, and that is most of the decision. Gumlet meters storage and bandwidth against published allowances; Cloudflare Stream meters minutes stored and minutes watched.

Gumlet publishes its prices, which is half the reason to pick it. A free-forever plan gives you 60 storage minutes, 100 GB of bandwidth a month and one seat. Creator is $6 a month on annual billing, with 1,000 storage minutes, 3,000 GB of bandwidth, domain restriction and the Google and Meta pixel; Growth is $19 and Business $99, adding seats, storage and custom viewer analytics. Bandwidth past your allowance is billed per gigabyte, from $0.50 on the free plan down to $0.06 on Business, and certified Widevine and FairPlay DRM is a $99-a-month add-on on any paid plan.

Cloudflare Stream has no free tier for Stream itself and meters two dimensions only. Storage is $5 per 1,000 minutes of video held per month, prepaid, so once you store anything you are buying at least one $5 block. Delivery is $1 per 1,000 minutes watched, post-paid, with encoding, ingest and bandwidth all included and no separate egress line. Its Media Transformations bill $0.50 per 1,000 operations after a free 5,000 a month.

Put a number on it. Take a 45-minute VSL at about 480p, roughly a 0.4 GB file, and 10,000 people who watch it in full. On Gumlet that is around 4 GB stored and about 4,000 GB delivered, which sits inside or just past a low paid plan and costs single or low double digits a month once overage is added. On Cloudflare that is 45 minutes stored, one $5 block, plus 450,000 delivered minutes at $1 per 1,000, so roughly $450 for the same views. Your real figures move with watch-through and file size, but the ratio holds: the per-minute model charges the same for a light file as for a heavy one, and light files are what this audience serves. Move to high-bitrate 4K and the two converge, because Gumlet is then moving far more data for each minute watched. If the video is a paid-traffic VSL, note that TrackPlay bills on plays from $29 a month with every feature included, a different axis again, because you are paying for conversion tooling rather than raw hosting.

Prices checked September 2026. Verify on the vendor site before you buy.