CloudChoose cloud when you need to prove the workflow quickly
Best when the fastest path is launch speed, managed operations, and a cleaner first estimate for playback, archive, and distribution.
Launch quickly for churches, webinars, virtual events, and sports coverage
Use buyer-facing estimates before deep infrastructure planning
Keep the next step simple: continue in cloud or launch on AWS
Good first fit for fast-moving teams and product validation.
Self-hostedChoose self-hosted when deployment control is the requirement
Best when your organization cares about private networking, infrastructure ownership, internal integrations, or data and region policy.
Keep the same workflow model on your own infrastructure
Model license, storage, CDN, and infra separately
Good fit when buyer intent is already operationally mature
Good fit when control beats launch speed.
EXAMPLE WORKLOADS
从你最接近的直播场景开始
这些不是套餐,而是帮助团队快速理解什么在驱动成本。
Church streaming
每周礼拜、SRT ingest 与几个社交输出
当重点是稳定进来、简单 restream 和较低运营负担。
SRT ingest2 outputsarchive optional
Church streaming
通常以少量并发观众和中等观看时长为主。
Virtual events
活动时段并发高,回放和 CDN 才是主要成本驱动
适合企业大会、网络研讨会、票务活动或大型线上会场。
peak viewersreplayCDN-heavy
Virtual events
这里更适合用观众数和观看小时来理解 CDN,而不只是用 GB。
Sports streaming
赛事直播、峰值观众与多平台交付
适合学校赛事、联赛、俱乐部频道和面向粉丝的持续直播。
high spikesmulti-destinationarchive useful
Sports streaming
体育场景往往同时拉高 CDN、录制保留和 restream 输出。
24/7 channel
连续交付、稳定并发和可预测的事件运营
适合新闻流、广播流、监控频道或 always-on 品牌频道。
24/7predictable concurrencyops-light
24/7 channel
当工作负载稳定时,自托管的固定成本优势会变得更明显。
Internal / partner delivery
私有或受限观众工作流,控制比规模更重要
适合内部直播、合作伙伴交付或受限浏览器播放。
limited audiencecontrolled accessstorage optional
Internal / partner delivery
这里通常更关注访问控制、录制和稳定性,而不是超大 CDN 账单。
API / product workflow
在同一实时引擎上构建浏览器播放和事件交付
适合同时需要产品界面和 API 自动化的团队。
browser playbackautomationworkflow scale
API / product workflow
这里的成本常常来自交付、存储和自动化规模,而不是单一功能。
PRICING ESTIMATOR
把使用场景转换成云端或自托管决策
根据观众、观看时长、输出、存储和 CDN 假设,快速理解成本形态。
Pricing estimator
Start with the workload, not the infrastructure diagram
Use a real live workflow first: hours, viewers, restream outputs, and archive needs. We will turn that into a cloud monthly estimate and a self-hosted cost shape.
Estimate mode
Decision focus
Use-case presets
Open advanced assumptions for provider and infrastructure details.
Church streamingWeekly SRT ingest with a few social outputs and replay archive.
Cloud monthly estimate
Church streamingWeekly SRT ingest with a few social outputs and replay archive.
Church streamingSame workload, infrastructure-first view.
Control the stack, keep the same workflow model
Equivalent infrastructure benchmarkUS$8
CDN and storage add-onsUS$101
Callaba license / supportChoose your plan
Self-hosted price is usually the combination of your infrastructure, your delivery/storage add-ons, and the Callaba self-hosted license that matches the control and support level you need.
Use buyer language first, then translate it into delivery and storage assumptions
Pricing becomes clear once you explain what changes the estimate fastest: audience delivery, runtime shape, archive policy, and how many outputs need to coexist around the same live contribution.
Compute
托管 runtime 或自托管算力
基础计算决定工作流能承载多少并发流和多重职责,但它通常不是唯一大头。
CDN / delivery
观众数、观看时长和覆盖区域会决定交付账单
对于虚拟活动和体育场景,按观众和观看小时思考往往比只盯 GB 更符合业务感觉。
Archive
录制保留、对象存储和回放资产
一旦你保留 VOD 或活动回放,S3、Backblaze 或其他对象存储就会变成长期成本的一部分。
Provider assumptions
Make the provider math visible without letting it hijack the buying decision
These are the practical public benchmarks to keep nearby while reading the estimate. Use them as planning anchors, not as the only story.
Self-hosted pricing is a stack decision, not a single number
The right self-hosted conversation is not only CPU and RAM. It is license, runtime benchmark, delivery at your audience size, storage and retention, and the support model your team actually needs.