Website · Documentation · Pricing

Cost calculator

Your traffic

Choose a workload. We’ll estimate traffic and requests for you.

Estimated monthly costs

USD per month, before tax. Load balancing and unpriced extras are excluded.

What’s included?

Estimates cover cacheable content. Origin and optional services are added only when you enter their rates. Plans differ in features and coverage; check their terms before buying.

Advanced settings
Split traffic between regions

Percentages must total 100%. The same split applies to bytes and requests. CloudFront charges by serving edge location; this is an approximation. Shared free allowances are allocated proportionally.

Origin and optional services

Paid tiers start with this workload; estimates do not include other account traffic. Enter your own effective rates after origin allowances. Reads use request misses; egress uses byte fill. Functions assume one invocation per viewer request. Zero leaves an extra out of the estimate; it does not mean your origin is free.

Compare a quote you received

This is your quote, not a published provider price. Use an effective rate for the selected traffic mix; tiers, included usage and commitments need to be reflected in your inputs. Sharing a scenario includes your quote details.

Presets are starting assumptions, not measured traffic. Video assumes one rendition and segment GETs; playlists, retries and extra audio tracks add requests. Fill is a byte ratio, not a request cache-hit rate. GB = 1 billion bytes; Google bills GiB = 1,073,741,824 bytes; CloudFront estimates use binary GB as a billing assumption.

Overview

System73 provides three related video delivery services through its Edge Services Platform. They solve different parts of a streaming workflow:

  • Edge Intelligence: SDK-based peer-assisted delivery.
  • Edge Delivery: content steering between configured CDNs.
  • Edge Analytics: performance and audience visibility.

Services must be activated on the account. System73 lists offices in the United States, Malta and Tenerife.

Network

Peer devices form a dynamic delivery tree, alongside the configured CDN paths. Viewer devices are not permanent cache sites, and a peer-node count is not a physical PoP inventory.

Coverage depends on the underlying CDN contracts, audience concentration and device/network compatibility. Test the expected audience and retain enough fallback CDN capacity for sessions that cannot share content. Check the connected CDNs for cache coverage and test peer availability with your viewers.

Features

FeatureSupported
Web application firewallNot listed
Bot protectionNot listed
DDoS protectionNot listed
Rate limitingNot listed
HTTP/3 (QUIC)Not listed
TLS 1.3Not listed
Tiered cachingNot listed
Origin shieldNot listed
Instant cache purgeNot listed
Serve stale while refreshingNot listed
Serve stale on origin errorsNot listed
Image optimizationNot listed
On-demand video✓ Supported
Live video✓ Supported
Digital rights managementNot listed
HLS / DASH packagingNot listed
WebSocketsNot listed
Signed URLsNot listed
Edge computeNot listed
Edge functionsNot listed
Key-value storageNot listed
Configuration API✓ Supported
Real-time logsNot listed
Log exportNot listed
Terraform providerNot listed

✓ Supported · Partial: limited or separate-product support · ✗ Not supported · Not listed: unconfirmed. Some features need a separate product or plan.

Peer-assisted video

Edge Intelligence uses WebRTC to share content through a centrally managed tree. It supports live video, on-demand video and DVR by matching viewers consuming the same segments. This is a delivery overlay, with SDKs and cloud orchestration.

Steering and analytics

Edge Delivery uses HLS/DASH Content Steering to prioritize configured CDN pathways. Its API manages resources and pathways and returns steering decisions. Edge Analytics provides metric access and dashboards; raw real-time request-log streaming is unconfirmed. Check which products and APIs your account includes.

Pricing

Fees, recurring commitments and billing currency are defined in the Service Order. Request a quote for the activated services rather than converting case-study savings into a tariff.

  • Separate platform and analytics fees from underlying CDN transfer.
  • Budget fallback delivery and regional audience traffic.
  • Confirm request charges, commitments, taxes and support.

Use the calculator’s manual USD quote for comparable transfer/request costs. Add other contract charges separately; peer offload and savings depend on the workload.

Developer tools

Player integration

The documentation includes HTML5, Android and iOS SDK guides, with player-specific examples. The HTML5 SDK requires an API key and can enable peer delivery and Content Steering independently. Test your exact player, device and media workflow.

Sharing policy

The SDK exposes NEVER, ONLY_ON_LAN and ALWAYS policies. Its documentation defines ONLY_ON_LAN using Wi-Fi/Ethernet connection types; the name alone does not guarantee sharing stays within the same local network. Review viewer upload use, network policy and fallback.

APIs

Edge Delivery publishes a versioned JSON API for resources, pathways and manifest decisions. Analytics endpoints need the customer and region; access to Lite or Advanced metrics depends on your account. Check authentication and legacy endpoint migration before reusing an existing integration.

When it fits

  • Broadcasters evaluating peer-assisted offload for concurrent viewers.
  • HLS/DASH workflows requiring explicit multi-CDN steering.
  • Teams able to integrate SDKs and measure audience-level performance.
  • Buyers who can compare platform fees with underlying CDN and fallback costs.

Before you choose

  • Test peer offload with the actual viewer concurrency, players and devices.
  • Budget the selected products separately and confirm they are enabled on the account.
  • Ask for raw-log delivery if dashboards are not enough.
  • Review viewer upload use and network policy before enabling sharing.
Sources