All NetBeez Subscriptions Include:
Fully Featured Dashboard
- Real-time monitoring tests (Ping, DNS, HTTP, Traceroute)
- Scheduled performance tests (iPerf, Speed test, VoIP)
- Unlimited user accounts
- On-Premise or Cloud deployment
- Real-time up-down and performance alerts
- API and public dashboard
- Automated software updates and bug fixes
- 24×7 email and phone support
- Live chat support within the dashboard
- Dedicated Customer Success Engineer
- Access to best practices tutorial and documentation
- Quarterly Business Reviews
- Support for SMTP, SNMP, and Syslog notifications
- Public API
- Custom report templates
- Automated reporting
- Exportable reports in PDF format
- Unlimited data retention
- Support for public dashboard
No. We offer annual or multi-year contracts. NetBeez invests in our customers and find that the most value is gained when customers utilize us over a long period of time. Special discounts are available for multi-year contracts.
The dashboard runs on top of a dedicated server, which can be deployed on-premise at your datacenter as a virtual appliance, or in the cloud. The NetBeez server can run on any public cloud (e.g. Amazon AWS, Microsoft Azure, Google Cloud).
Yes. You can deploy your dashboard on a public cloud, or we can host it for you. The NetBeez server can run on any public cloud (e.g. Amazon AWS, Microsoft Azure, Google Cloud).
Generally, we advise installing one Ethernet and one WiFi per office or building. Larger buildings may require more sensors based on the size (e.g. number of floors) of the building and, in the case of WiFi sensors, based on the number of areas where users congregate.
Yes. NetBeez supports the Raspberry Pi platform. You can use your own Raspberry Pi or use the hardware that we include with each subscription. If you are using your own Raspberry Pi, you can install the NetBeez agent as a Linux package, or download the pre-installed image we have built. You can find more information on our online documentation.
Both sensors run the same type of tests. The only difference is that the WiFi sensor has two interfaces: one Ethernet, that is used to connect back to the central server, and one WiFi, that is used to run the monitoring tests.