September 01, 2020//Kylie HoskenLast Updated: September 08, 2020
Not all software deployments are created equally! When it comes to purchasing and deploying new software, we know that not every organization will have the same wants or needs. Companies will differ with their infrastructure, resources, bandwidth, regulatory environments, or implementation timeframes. In order to meet those different requirements, we offer three different ways to deploy SecureLink.
Each method has its own benefits, costs, and requirements, which we’ll cover in more detail below to help guide you as you consider how SecureLink can fit in your environment. We offer different options to ensure that every company is able to choose what’s best for them, their needs, and their environment.
One option of deploying SecureLink, which is the most common option our customers choose, is via an appliance deployed on a virtual machine within your own environment or a cloud infrastructure such as AWS, Azure, or Google Cloud. Customers who choose to go this route typically already have the virtual infrastructure in place to support an additional application and have the IT staff and bandwidth to manage it.
This method is also a good fit for organizations in highly regulated industries that handle sensitive information, such as hospitals that store protected health information (PHI) and need to meet HIPAA requirements. These types of customers often prefer for their data to be physically stored in their environment and in their direct control to ensure compliance with their relevant regulations and data security.
Another option of deployment is via a physical appliance. In this instance, we will send you a physical server to set up in your environment (rather than deployed on a virtual machine). We find customers might choose this option if they have an overtaxed virtual infrastructure, or even no virtual infrastructure in place.
This method, as in the above, is another option for those highly regulated industries who prefer to have their data physically stored on-site and in their control.
A third deployment option is via SecureLink’s hosted offering. With this offering, each customer has their own dedicated appliance, so there’s no shared instance with other customers. This route is a good fit for those organizations with a small IT team or a team with limited bandwidth or infrastructure to deploy and maintain the SecureLink appliance in their own environment.
Going this route is typically the quickest and easiest way to get up and running with SecureLink, so it works well for those organizations with a tight implementation timeframe or who urgently need a solution in place (and a friendly reminder, we can get you up in running in less than 60 days with hosting options. So, this would be even quicker).
Finally, as SecureLink is hosting the appliance, organizations don’t have to worry about ongoing upgrades, monitoring, and patching; SecureLink handles all of those components, freeing up time and bandwidth for the IT team to focus on other areas.
SecureLink provides each of these options to be able to meet the requirements and needs of organizations across different industries and is flexible to meet your needs depending on your company’s size. We understand that each organization has a different infrastructure, regulatory environment and way of operating. So, no matter your preference, hosted or on-premise, virtual or physical, we can deploy SecureLink in a way that works for you. To learn more about how SecureLink works for different companies, check out our customer stories which highlights how our products have helped them with secure remote access and secure remote support.