Earlier this year we introduced the Dedrone Cloud, enabling customers to get started protecting their airspace quickly and easily. Although the Dedrone Cloud is the right deployment architecture for many customers, we’ve heard from customers who want to carefully weigh the pros and cons of each. This blog post outlines the principal differences between DroneTracker software’s cloud and on-premise deployment models.
The Dedrone Cloud enables customers to protect their airspace without the need to provision, manage, maintain on-premise IT infrastructure. Customers deploy sensors to detect and classify drone activity in their airspace, and those sensors connect to the Dedrone Cloud.
Dedrone the hosts and maintains the customer’s DroneTracker software, and access it through a secure connection over the public internet. The Dedrone Cloud is backed by a 99.9% uptime SLA, ensuring customers are protected and their data is available at any time they need it.
With on-premise deployments, customers install DroneTracker software on the server (or virtual machine) of their choice, and they are responsible for the provisioning, maintenance, availability, and overall management of the software infrastructure. In this model, the software is not accessible to anyone outside the network on which the software is installed (with the exception, naturally, to users accessing via VPN or other authorized routes), which is desirable or necessary in some environments. The software can still send email and text message alerts about drone incidents to users.
Here’s a high-level illustration that shows some of the difference in the deployment models:
If you’re curious to learn a bit more about the Dedrone Cloud, check out this overview.