Check out our Amazon Connect solution! Learn More

How to Create a Proof of Concept with WebRTC Monitoring Using

By Alex Beardsley on September 7, 2018

At, we believe in the long-praised startup idea of failing fast. It is one of the many reasons we build an effective WebRTC monitoring service and try to help companies build better real-time communication products. Failing fast extends to every facet of our company, from the marketing team to the engineering team. We try to prioritize it as much for ourselves as we do for our customers.

Many of our customers and potential customers follow the dogma of failing fast as well. We regularly talk to young, ambitious companies that are developing and improving a new product or service, as well as large corporations that are in the process of switching from old-school telephony systems to WebRTC. They share a similar concern: they are worried about improving their service and scaling quickly. They want to arrange a proof of concept (PoC) with so they can identify exactly what they need to focus on when it comes to making their service even better and scaling their product even faster.

What is the Best Way to Implement a Proof of Concept with WebRTC Monitoring?

We provide several different kinds of accounts to best meet our customers needs. This includes a free developer version, so teams can get started and see the immediate value of adding into their product or service.

The Basic Plan

Our basic plan is ideal for building, testing, and deploying a proof of concept application. It provides half a million user minutes, three applications, one user, and seven days of retention: an acceptable starting plan for a small product or service.

Pro Plus Plan

Our pro plus plan is ideal for building moderate size applications and operating secure, compliant services. It is most commonly used for a proof of concept with a more mature product that may have considerable traffic. This plan provides one million user minutes, three applications, five users, conference filters, access to ICE tables, fifteen days of retention, application and organizational roles, and the pre-call test.

These proof of concepts are typically arranged for a one to three month period. During this time frame, your product or service will be integrated with You will be able to use the dashboard to identify and resolve conference issues, as well as track your successful conferences. Some initial test traffic is sent, and then is ramped up as your company begins to roll out your service to a production environment.

Interested in getting started with a proof of concept with Take a look at our 100% hassle-free demo dashboard.


Register for an account with, or email our sales team directly for more information on how you can improve your service with WebRTC monitoring.

Tags:, WebRTC Monitoring