Pricing

Callstats.io has 4 plans to choose from. And we offer a free developer plan, of course!

DEVELOPER

Free - no credit card
required
  • 1 simultaneous session1
  • Maximum of 25,000 data points
    every day
  • 24-hour data retention
  • 1 app
  • Simple Notifications
  • Works with WebRTC-compatible browsers 3
  • Email support: Response time best effort

BASIC

185 € / month + volume-based costs
  • 50 simultaneous sessions1
  • First 50,000 data points free
    every month
  • 7-days data retention
  • 3 apps
  • Simple Notifications
  • Works with WebRTC-compatible browsers 3
  • Email support: Response time 48h on weekdays

ENTERPRISE

Custom price
Contact us
  • Custom simultaneous sessions1
  • First million data points free
    every month
  • Custom data retention
  • Custom no. of apps
  • Complex Notifications
  • Works with WebRTC-compatible endpoints4
  • Email and phone support

Volume-based costs for Basic and Pro

Data points (dpts) are calculated on a monthly basis for each app. The price per data point (dpt) reduces as the volumes increases as shown in the table below.

Number of dpts per month Price per dpt
Under 1 million 0.000200 €
1 - 10 million 0.000075 €
10 - 100 million 0.000050 €
Over 100 million Custom price
Our pricing model ensures that the cost is moderate even with a larger volume.

Monthly data point cost calculator

Note that calculation is per app and per month. This means that as a Pro customer you get the free data points monthly for each app.

total number of data points

Available for Pro customers: Infrastructure integration 4

Measure the performance of your media relay servers, media gateways, conference bridges etc. in real-time.
  • 1 A session represents a single conferenceID and may have multiple participants (indicated by unique userIDs).
  • 2 A data point represents a single measurement event sent to callstats.io via the javascript or any other integrated library. For example, if the measurements are sent every 10 seconds, there are 6 data points generated by each participant every minute.
  • 3 A WebRTC browser are capable of executing the WebRTC API natively or by utilizing the Temasys plugin. See full list of browsers with native WebRTC support.
  • 4 WebRTC-compatible endpoints (e.g., TURN servers, SFU, MCU, etc.) implement WebRTC-related networking protocols (e.g., SRTP, SRTCP, STUN, DTLS, ...) and not necessarily the API.