The 6 Reasons for StacksWare’s 15 Minute Deployments
When we tell IT administrators that our deployment times rarely exceed 15 minutes, they naturally respond with skepticism. Administrators are overwhelmed with marketing material from vendors that describe their deployment times in ambiguous ways like “we deploy in record time” or “we have blazing fast installation speeds.”
To separate ourselves from the noise, StacksWare was designed to have a simple and seamless deployment process. Here are the 6 reasons our deployments are so fast.
Reason One: Docker Containers
When your StacksWare deployment spins up for the first time, we leverage Docker containers from our cloud service to deploy the most fully-featured code into your datacenter. As our engineering team places the finishing touches on any new product features, containers with those latest features are immediately pushed to your infrastructure.
Reason Two: Leveraging the Hypervisor
For deployments with virtualized infrastructure, we leverage the hypervisor to avoid forward network requests that might prove complicated in highly firewalled environments with multiple layers of private networks. For example, we leverage VMware Tools in VMware ESXi environments to execute inventory commands in virtual machines. In this case, a connection from the endpoint back to our virtual appliance is the only requirement. From a firewall perspective, this client → server network request is far more achievable than a server → client network request. Client endpoints normally already have access to services (e.g. email servers, shared file datastores) in the management server network to which our virtual appliance is deployed.
Managed service providers (MSPs), who traditionally have the most difficult time understanding their application real estate, benefit greatly from this deployment process. Since each tenant in a MSP environment is normally segmented into its own VLAN, creating the necessary firewall rules to enable a traditional monitoring system to communicate with every endpoint is prohibitively difficult. With StacksWare, the MSP does not have to worry about forward firewall rules, saving administrators days of painful network configuration.
Reason Three: Utilizing the Cloud
We host our solution in the cloud to save hours of time and to avoid consuming on-premise storage, compute, and memory resources that are better allocated to your core business operations. Additionally as an IT administrator, you do not have to spend time backing up your StacksWare data or managing license keys.
Reason Four: Turnkey Datacenter Virtual Appliance (OVA)
Our datacenter component deploys as a self-contained 1GB virtual appliance that only consumes 512MB RAM and 1 virtual core. It serves as a simple turnkey cloud connector to forward information to our cloud service and requires very minimal configuration (e.g. one vCenter and one Active Directory service account) to properly extract data.
Reason Five: Agentless Installation Process
We support two different deployment options: our managed agent option and our agentless option. With our managed agent option, we install an agent on every endpoint and ensure that the agent is updated whenever we release a new version. With our agentless option, we leverage Powershell on each endpoint to retrieve application information. In either case, the administrator never has to manage and update agents. Our virtual appliance handles the heavy lifting.
Reason Six: Dedicated Deployment Engineer and Founder
To ensure that every deployment is seamless, we provide an engineer and founder as a resource for every installation and guarantee 24/7 support. After countless deployments, we are prepared to answer any questions you have. In fact, we normally walk administrators through the installation process via screen share to prevent confusion.