Pricing And Billing
Sariska's approach to pricing and billing our customers.
Background
Sariska's pricing model is based on the fundamentals that users should only pay for what has been used. Our pricing page gives you a detailed breakdown of how we approach pricing and how it differentiates us from per-minute-based offerings.
Resource Usage
When you use Sariska's APIs to build your applications, the major resource consumption is bandwidth. Things like publishing a stream, starting a multi-party conference, messaging, sending or receiving streams, or sharing your screen, those offerings use bandwidth. The billing is done on the basis of how much bandwidth has been consumed by each user.
Secondly, Importing streams in other formats, like RTMP, recording rooms, or exporting tracks to third-party live streaming services, consumes bandwidth in a data center but also a significant amount of CPU cycles to transcode streams.
Bandwidth
Bandwidth is metered in gigabytes (GB = 1000 MB). Our system tracks the amount of data transmitted from your application to our SFU (upstream), and data transmitted from our SFU back down to your application (downstream). When it comes time to tally your bill, we apply the following logic:
Take the greater of the upstream and downstream bandwidth.
Subtract the project's monthly free bandwidth allotment from the value determined in (1).
The result from (2) is your bandwidth overage in GB. If this number is greater than or equal to 1, the amount you owe is your overrage multiplied by your price-per-GB.
Transcoding
Metered in minutes of audio and video being transcoded. The minutes are the length of the video being transcoded and not the time is taken for the transcoding to get over.
When it comes time to tally your bill, we apply the following logic:
Take the total audio-only minutes transcoded and multiply by the price-per-minute.
Take the total video minutes transcoded and multiply by the price-per-minute.
Rates
Bandwidth
Transcoding
Last updated