Question
Why is pricing the same for relayed and routed sessions?
Applies To
- Pricing
- Relayed Sessions
- Routed Sessions
Answer
Pricing is structured this way to account for:
- Abstractions required on top of webRTC to allow us to support a variety of endpoints.
- Managing and hiding the rapid changes in the webRTC spec, amongst various browsers, and device iterations.
- Developer tools and robust logging that allow for far more effective development and debugging.
- The relationships we have with browser vendors to work with them to resolve bugs on our customers' behalf.
- Our server infrastructure that is required for the signaling to create and maintain a session. This can be one of the most complex aspects of a video service and is not available as part of the core webRTC standard.
Articles in this section
- How to update service address and tax ID?
- How to use One Time Payment?
- How to update Billing or Invoice Address for Video API
- How can I calculate pricing for Audio Connector/Connect API?
- Billing Inquiries and Disputes - Video API
- Reading Your Video API Invoice
- Sales and Indirect Tax Charges for Video API Accounts Beginning July 2021
- Scenario: If one person is publishing audio/video to 100 people, who are only subscribing to that stream, is that charged as 1 streaming minute or 100 streaming minutes?
- Scenario: If two people are connected in a video call, both publishing and subscribing to video from each other for one minute, would that be charged as two minutes?
- Can I push my Vonage Video API-powered app to production during trial?