CDNBye / SwarmCloud

www.swarmcloud.net · China

A WebRTC-based P2P delivery service that lets viewers share media segments. Browser and native SDKs work alongside an existing CDN or origin.

P2P deliveryWebRTCLive and on-demand videoPlayer SDKs
Service marketsMultiple regions
BillingPlans / Packs / Custom quote
Free trialSupported
Payments
AlipayPBank transferCredit / debit cardCryptocurrency
Overall rating
★★★★★★★★★★3.5

On-site interest
3,200index
01

Company introduction

About CDNBye / SwarmCloud
Founded
CDNBye project history since 2018
Co-founders
Not disclosed
Headquarters
Not disclosed
Company
深圳市佑游科技有限公司 (Chinese-site operator); SwarmCloud Inc. (international terms)

CDNBye and SwarmCloud

SwarmCloud continues to use CDNBye technology, developer resources and console entry points for peer-assisted media delivery. The Chinese service agreement names 深圳市佑游科技有限公司 as the provider, while the international terms name SwarmCloud Inc. The selected site and order determine the contracting arrangements.

Public SDK records trace the CDNBye project to 2018. A 2020 Shenzhen University project profile identified Mijat Kustudic as the founder and leader of the CDNBye project, a historical project role distinct from the incorporation details of the current operators.

Client SDKs form groups of devices watching the same content. A player can retrieve segments from other viewers, then use the existing CDN or origin when peers are unavailable, upload capacity is insufficient or a peer request times out. Publishers still arrange content hosting, conventional CDN capacity and the player itself.

Integration and operating conditions

Register a website domain in the console and complete the required DNS or file validation. Native applications and Electron use a matching AppId and token with the appropriate SDK. The dashboard provides P2P and CDN traffic statistics. Deployment zones, tracker configuration and signaling addresses must match: data in separate zones and peers using different signaling services are not automatically shared.

Savings depend on simultaneous viewers of the same content, available segments, upload bandwidth, NAT, firewalls, devices and player compatibility. Sparse audiences, fragmented viewing or networks that block WebRTC require adequate conventional CDN and origin capacity.

Protocols, authorization and content control

HLS, DASH and native-platform support vary by integration. Current Web HLS and native SDK documentation lists LL-HLS as unsupported. Service Worker integrations require HTTPS and the necessary script on the website’s own origin; that requirement does not apply to every hls.js integration.

Publishers retain responsibility for authorization, DRM and content rights. Tokenized streams can require configuration by support. User-specific segments and personalized ads need appropriate bypass rules. Encrypted WebRTC transport does not replace segment-content validation, device-cache management or privacy assessment.

02

Who is this provider for?

Video businesses with concentrated audiences

A fit for teams with many simultaneous viewers of the same live or popular on-demand content, seeking to reduce part of their CDN or origin delivery traffic.

Evaluate actual audience distribution, upload capacity and playback metrics while retaining conventional delivery and fallback capacity.

Teams that can modify players or applications

A fit for projects able to integrate JavaScript, Android, Apple-platform or cross-platform SDKs and manage domains, AppIds, tokens and releases.

Choose the SDK for the actual player, protocol and OS version. Integration requires client changes rather than only a DNS switch.

Enterprise networks and managed devices

The eCDN documentation provides a route to evaluating video-segment sharing within an enterprise network, subject to scheduling and network configuration.

WebSocket, UDP and local discovery policies need network-team involvement. Self-hosted signaling or server-as-peer components are distinct from a private deployment of the entire platform.

Peer-assisted delivery adds viewer-to-viewer sharing to an existing content-delivery system. Budget for the SDK service, conventional CDN/origin traffic, deployment zone, integration and operations. A P2P traffic package does not include complete origin hosting or a conventional CDN service.

03

Services and products

Core products from official sources

Explore products by use case: what they do, how to use them and whether they are billed separately.

Web and Electron P2P delivery SDKs

Browser P2P delivery

Adds peer-assisted delivery to supported HLS, DASH and browser-player integrations, including Video.js, Shaka Player and Dash.js. Web HLS offers hls.js and Service Worker paths. MP4/MP3 uses a separate Service Worker integration requiring HTTPS, a same-origin script and origin support for CORS, OPTIONS and Range. Electron integrates through an AppId and token.

Traffic packages / PlansOfficial product information

Mobile and TV native P2P SDKs

Native application delivery

Integration options include Android, iOS/tvOS/macOS, Flutter and React Native. Android documentation supports HLS/DASH; the native Apple SDK supports HLS, and DASH in the cross-platform wrappers is limited to Android. The native SDKs handle one stream at a time and do not support LL-HLS. Check each platform’s minimum OS before integration.

Traffic packages / PlansOfficial product information
Sources: CDNBye / SwarmCloud official product pages and developer documentationVerified: 2026-11-17
04

Plans and pricing

Official public pricing
Website delivery and security plans · monthly and annual billing shown separatelyUSD / CNY

CNY plan: 2 TB/day

Accounts purchasing under the Chinese price list

CNY 190/ 30 days

30-day plan

  • Daily P2P allowance of 2 TB
  • Top up with a traffic package when the daily allowance is insufficient
  • Monthly-plan allowance is used before traffic-package allowance
  • Existing CDN and origin charges remain separate

USD plan: 60 TB

Accounts purchasing under the international USD price list

USD 25/ 30 days

30-day plan

  • 60 TB total with a daily limit of 2 TB
  • Higher total and daily allowances are available
  • Supplement the plan with a traffic package
  • Contact support for the unlimited tier

Large-volume and custom procurement

High-concurrency services or businesses requiring a separate order

Contact sales

Custom quote

  • The Chinese price list offers average daily peak-concurrency billing above 50,000 peak concurrent users
  • International orders may specify bandwidth, minimum commitments and excess-usage rates
  • Confirm the deployment zone, support, taxes and payment terms in the order

Chinese documentation lists 150 GB per account per day and a one-month enterprise trial, while the English overview states 300 GB daily. Confirm enterprise-trial allowances, payment requirements and end-of-trial arrangements when activating.

How are separate products billed?

ProductAllowance / base feeUsage prices
CNY traffic package: 1 TBP2P media traffic;valid until consumedCNY 7
CNY traffic package: 10 TBP2P media traffic;valid until consumedCNY 68
CNY traffic package: 100 TBP2P media traffic;valid until consumedCNY 670
CNY traffic package: 500 TBP2P media traffic;valid until consumedCNY 3200
CNY traffic package: 1000 TBP2P media traffic;valid until consumedCNY 6000
CNY monthly tier: 5 TB/dayDaily allowance;valid for 30 daysCNY 450 / 30 days
CNY monthly tier: 10 TB/dayDaily allowance;valid for 30 daysCNY 880 / 30 days
CNY monthly tier: 25 TB/dayDaily allowance;valid for 30 daysCNY 1900 / 30 days
CNY monthly tier: 50 TB/dayDaily allowance;valid for 30 daysCNY 3500 / 30 days
CNY monthly tier: 100 TB/dayDaily allowance;valid for 30 daysCNY 6200 / 30 days
CNY monthly tier: 250 TB/dayDaily allowance;valid for 30 daysCNY 11800 / 30 days
CNY monthly tier: 500 TB/dayDaily allowance;valid for 30 daysCNY 17800 / 30 days
CNY monthly tier: 1000 TB/dayDaily allowance;valid for 30 daysCNY 23800 / 30 days
USD traffic package: 10 TBSupplementary traffic;confirm validity at purchaseUSD 9
USD traffic package: 100 TBSupplementary traffic;confirm validity at purchaseUSD 85
USD traffic package: 500 TBSupplementary traffic;confirm validity at purchaseUSD 400
USD traffic package: 1000 TBSupplementary traffic;confirm validity at purchaseUSD 750
USD monthly tier: 150 TB150 TB total;5 TB/day;30 daysUSD 58 / 30 days
USD monthly tier: 300 TB300 TB total;10 TB/day;30 daysUSD 108 / 30 days
USD monthly tier: 750 TB750 TB total;25 TB/day;30 daysUSD 240 / 30 days
USD monthly tier: 1.5 PB1.5 PB total;50 TB/day;30 daysUSD 420 / 30 days
USD monthly tier: 3 PB3 PB total;100 TB/day;30 daysUSD 700 / 30 days
USD monthly tier: 7.5 PB7.5 PB total;250 TB/day;30 daysUSD 1350 / 30 days
USD monthly tier: 15 PB15 PB total;500 TB/day;30 daysUSD 2000 / 30 days
USD monthly tier: 30 PB30 PB total;1 PB/day;30 daysUSD 2900 / 30 days

The Chinese price list quotes CNY daily allowances and 30-day plans; the international list separately quotes USD totals and daily limits. They are separate offers, not currency conversions. Chinese documentation defines billable traffic as P2P media delivery, excluding signaling, and states 1 TB = 1024 GB. Its traffic packages last until consumed; the USD page does not state the same validity rule. Confirm the allowance for the chosen zone/account; the amounts are not cumulative. Eligible noncommercial open-source projects and nonprofit organizations can request free support. Chinese purchasing supports Alipay or corporate bank transfer. The international price page lists PayPal, Alipay, payment cards and cryptocurrency, with cards processed through Stripe; individual card networks are not specified. The FAQ specifies CNY for Alipay and USD for PayPal.

Prices checked: 2026-11-17
05

CdnChart Selection Guide

GoodSelection verdict

A fit for teams with an existing video-delivery system, SDK integration capacity and concentrated simultaneous audiences

CNY and USD plans provide a basis for budgeting P2P traffic, while results depend on actual viewers and network conditions.

Use casesProductsPricing and termsDocumentationSupport resources

Why we recommend it

  • Web and native SDKs provide defined integration paths alongside an existing CDN.
  • Public pricing distinguishes daily limits, 30-day plans and supplementary traffic packages.
  • Domain, AppId, zone and traffic-statistics controls help developers manage integration.

Considerations

Validate player protocols, device versions, segment lengths and WebRTC connectivity, and retain CDN fallback. Confirm free allowances for the selected site and account. Personalized content, authorization, caching and endpoint upload need explicit design decisions; ultra-low-latency or sparsely viewed services require particular care.

Related articles

Explore CDNBye / SwarmCloud products, use cases and buying advice

No articles about CDNBye / SwarmCloud yet.