OpenVPN Access Server Reviews

My use case for OpenVPN Access Server is infrastructure VPN for internal company usage. The main reason we use it is because of the user management UI and the visual representation of all the data related to it.

Overall, my best feature of OpenVPN Access Server is the user management, which is very nice because OpenVPN can be quite painful and not very visible. This tool gives absolute visibility and full control over the users, their access, and provides them with some dashboards. The administrator can see everything related to the VPN system.

I primarily utilize OpenVPN Access Server access control features for personal working desktops to access the infrastructure. We provide the key pair generated automatically, which I control, but I know that it has other features to deliver those credentials as well.

I find that connection speed with OpenVPN Access Server loses in comparison to WireGuard, which is very fast. However, compared to any other solution, they are pretty much the same, and they do not require a lot of system resources for encrypting traffic, so it's average—not bad.

I think speed has room for improvement in OpenVPN Access Server. If they can make adjustments to the protocol for better speed, identical to WireGuard for example, that would be really good.

I have been using OpenVPN Access Server for about a month, but with OpenVPN products in general, I have worked for several years.

I would rate the stability of OpenVPN Access Server about an eight or nine; it is pretty stable.

Our size of organization did not allow us to discuss scalability for OpenVPN Access Server, but one server handles everything, especially since it's for internal traffic. It is hard to say, but I doubt it should have any issues with this.

I would rate technical support for OpenVPN Access Server as not applicable because I have never talked with them. The documentation was absolutely fine for me; it was well-structured, and I did not have any difficulties with this solution, so I did not need the support.

I have tried other solutions including Cisco, FortiGate, and native IPsec solutions from Windows platforms, as well as an open-source version of OpenVPN without dashboards and the WireGuard open-source solution.

I find it extremely easy to install and set up OpenVPN Access Server.

As far as I remember, it takes about 10 or 15 minutes maximum to have a server ready.

OpenVPN Access Server requires really minimal maintenance, as it is basically dockerized and everything is automated, so it is even updated. It's absolutely simple to install.

Regarding pricing for OpenVPN Access Server, I don't remember all the details exactly, but I believe it is really flexible and even provides something like free trials, so anyone can try it. It was reasonable as far as I remember.

I compare OpenVPN Access Server to other solutions by noting that it is extremely easy to set up. Even someone who is non-technical or possesses technical knowledge will be able to install it and use it in a few minutes, which is almost not possible with any other solution, as they are much more complicated.

I do not use any role defining features because it is a really small organization, so it wasn't required, but it is there if needed.

I have seen OpenVPN Access Server integrations such as LDAP, RADIUS, PAM, and SAML, but again, due to the size of the company, it wasn't necessary and we didn't have it inside the company. However, it was nice that it is already embedded inside.

We haven't used much in terms of integrations with OpenVPN Access Server, so it's hard to say. We only used basic features there.

My advice for others looking to implement OpenVPN Access Server is that it is at least worth trying if you need a fast and easy implementation solution without technical overhead and you just need VPN access, which is supported by all operating systems and mobile operating system vendors. It is definitely worth a try.

OpenVPN Access Server was purchased directly from the website, not on the AWS marketplace or through a partner purchase. I would rate this product an overall eight out of ten.

My primary use case for OpenVPN Access Server is providing secure, centralized access to hybrid cloud environments. Whenever I set up hybrid cloud infrastructure for clients, deploying Access Server is a natural next step. It acts as a gateway, allowing us to securely connect to the private network for routine administration, system updates, and accessing internal dashboards and tools.

The main benefit I have seen from using OpenVPN Access Server is secure access to private resources over the public internet. That is the key benefit whenever it is set up, and it applies to all types of users. It applies to technical users who want to administer servers, internal users who are working, and executives who want to view internal dashboards. OpenVPN Access Server allows users to feel secure, and indeed, a lot of their traffic is secure. At the same time, if you configure OpenVPN Access Server correctly, users can continue to access non-corporate websites over the public internet, which is beneficial. If they are using Facebook or other personal activities on their phone, they can continue to do that, and that traffic will not be transferred over OpenVPN Access Server. Only when they try to access internal resources will that be accessed over OpenVPN Access Server. I really appreciate that aspect of OpenVPN Access Server.

The best features in OpenVPN Access Server for me are the integrations with single sign-on providers so that users can maintain a single corporate identity. I also appreciate the administration dashboard, which allows you to fairly easily provision subnets for different groups. Performance-wise, it is quite performant. OpenVPN Access Server supports both TCP and UDP protocols, and you can decide which to turn on or off. It is fairly performant and reliable. You can trust that once you are in the network, you will access your resources.

The user interface of OpenVPN Access Server is good but can be improved. I would prefer to see it become more intuitive. I use Twingate as an alternative, and in Twingate, you see resources, while in OpenVPN Access Server, those would be IP addresses. You get to see dashboards and access views of who can access a particular resource or subnet. You can see who can access what resources from the user view, but you can also see the reverse, which is which resource can be accessed by what users. That reverse view would be a nice addition to have in a dashboard. Additionally, access logs associated with that resource would be helpful, so it would be beneficial to have different views for the same content.

Beyond the positive aspects, I would like to see improvements in OpenVPN Access Server. Twingate offers a different approach to the same problem by moving more towards resource-specific resources and fine-grained zero-trust access, as opposed to entire subnets and entire networks. I would prefer to see views on resources. In the same way that we can define subnets, perhaps we could have views that describe what this particular subnet does and what this particular resource does. Then we can assign those resources and subnets to individual users and groups. It is more about granularizing the resources that can be accessed rather than simply bundling them under subnets or a list of subnets, which is the current approach.

Apart from that, I would like to see UI enhancements in OpenVPN Access Server in the future. Making it more modern would be beneficial.

I have been using OpenVPN Access Server for over eight years since 2018.

Regarding stability, I have not had any crashes, performance issues, or stability issues with OpenVPN Access Server. That is one thing I appreciate the most about OpenVPN Access Server. Once you set it up correctly, it works and continues to work reliably. I do not recall ever experiencing OpenVPN Access Server crashing or the OpenVPN Access Server client crashing personally.

Regarding scalability, I find OpenVPN Access Server scalable with some caveats. It is scalable on AWS because it is a matter of increasing the instance size and increasing the number of licenses. However, sometimes your license disappears or gets wiped out when you scale the infrastructure, which can be quite annoying, and requires reaching out to support to get set up again. Inherently it is scalable, but the process of scalability can be enhanced.

I would evaluate OpenVPN's technical support and customer service teams as providing standard support. You send a ticket or create a ticket, and somebody responds, and they seem to know what they are doing. The service is adequate. I would rate the technical support an eight on a scale of one to ten.

Positive

In comparison with other products and solutions such as Twingate or other VPN services, the key differences between OpenVPN Access Server and competitors include access to resources versus subnets, focusing on fine-grained access. Another difference is the ability to see logs specific to the resource that has been accessed. Compared to other products such as Cisco, the advantages include reliability and the protocol—OpenVPN Access Server uses HTTPS and UDP, which are universal. Some of the other protocols that other VPN providers use are not guaranteed. OpenVPN Access Server has advantages there. There should be a move more towards zero trust, where you are accessing a specific resource, defining a specific server or subnet, and assigning access to those resources to individual users or groups. That approach would be better.

The ease of installing and setting up OpenVPN Access Server within the organization depends on the skillset of the person conducting the setup. On AWS, I would say it is medium difficulty because you have to select the right license and the right instance size, and it is not inherently clear what instance size to use. On-premise, it is fairly easy to set up. The setup for clients depends on the client that the end user is using. On mobile devices, sometimes I find that Mac users and iPhone users find it easier to set up than Android users. Overall, I would characterize the setup difficulty as medium. It is not too difficult and also not too easy.

My experience with the pricing, setup cost, and licensing cost of OpenVPN Access Server is that the licensing is fair for the value provided. My experience is mostly on AWS, and there, I think the pricing is quite fair.

I utilize the Access Controls feature of OpenVPN Access Server by provisioning users into groups and then provisioning access to those groups. The effectiveness of OpenVPN Access Server in providing precise access to users, groups, or devices is quite effective and reliable. I would not say it is the most intuitive specifically because there are default access groups, then you have overrides, and it is not inherently clear for someone just getting started with the product. However, if you are more experienced, it is straightforward to set up. Once you set it up, it is reliable, and you have confidence that whatever access you provision for that group of users will be maintained.

I purchase OpenVPN Access Server for my clients through the AWS Marketplace. Given my extensive experience with OpenVPN Access Server, I would recommend that before any organization implements it, they really need to define what their networks and subnets are and what is connected to what. Consider whether your on-premise infrastructure is connected to your cloud and whether your cloud is connected to another cloud. It is essential to have a good understanding of your network. Make sure there are no overlapping subnets, and then decide where to provision OpenVPN Access Server. The key advice is to understand your network before you even provision this resource, because where you provision it will determine what users can access. You certainly want to have a good amount of coverage where possible so that you can access your internal resources securely. I would rate this product an eight overall.

My main use case for OpenVPN Access Server is to allow our employees to access the private network and external web services that are whitelisted to our network.

A specific example of how my team uses OpenVPN Access Server is that developers are accessing private development services, microservices, or resources on AWS, while the business team or sales has access to some specific services launched and implemented on our private network that are closed from internet access.

External parties or partners whitelist our IP addresses, and our employees use VPN to access those services as well.

I believe the best features OpenVPN Access Server offers are 2FA authorization and its connection with Google Workspace, which allows for good synchronization.

I use the 2FA authentication and Google Workspace synchronization, and the benefits of these features for my team are that Google accounts of our employees can be synchronized and authorized through SSO, which makes it easier to set up and configure VPN for our employees. If they have a Google account, they can connect to VPN easily. 2FA adds an additional layer of authorization that enhances security.

OpenVPN Access Server has positively impacted my organization by allowing access to our private services, enhancing security, and enabling remote work from anywhere, as I just need to connect to the VPN to have encrypted traffic to our private resources.

I think the most difficult part of OpenVPN Access Server that I would improve is the management of the network, particularly the configuration on the admin side of the network and subnets, which is quite complicated.

Some services, such as YouTube, occasionally become unavailable because it seems to be a bot detection issue from YouTube related to the VPN, and I believe that can be improved to ensure other services do not misidentify OpenVPN Access Server as a bot.

I would describe the user interface of OpenVPN Access Server as fine, but sometimes it requires reloading the whole page to see changes, which can be annoying. In cluster mode, I cannot see what node the user is connected to from the cluster without checking each node individually, which could be improved.

I have been working in my current field for seven years.

OpenVPN Access Server is stable.

OpenVPN Access Server's scalability is somewhat hard to manage, but it remains scalable overall, primarily due to its cluster mode.

We did not use a previous solution; however, I could mention WireGuard, which could have been an option but lacked 2FA authorization and Google authorization and operates only on Layer 3, while OpenVPN Access Server works on Layer 7, which is important for business users.

I find it easy to install OpenVPN Access Server, and there are no issues. It is just a couple of clicks or using the package from the Ubuntu package registry, and the documentation is clear on how to do that.

I did not purchase OpenVPN Access Server through the AWS Marketplace; it was set up manually as a self-hosted solution.

I have not seen a return on investment in terms of fewer employees needed, money saved, or time saved.

My experience with pricing, setup cost, and licensing for OpenVPN Access Server is that the license was for 10 people and it was fine on a yearly basis.

WireGuard was another option considered before choosing OpenVPN Access Server.

OpenVPN Access Server remains stable and works well despite a couple of things that can be improved or enhanced, and the documentation is good with no issues on that side. My impression of the connection speed when using OpenVPN Access Server compared to other VPN solutions is that it is medium; it is not fast and it is not slow, but in some cases, it could be slow.

My advice for others looking into using OpenVPN Access Server is to consider if they need a VPN or just zero trust network access. If they want to route traffic to specific domains, OpenVPN Access Server may not be suitable, but for a secure, safe, and stable VPN with good service integrations such as Google for SAML authorization, it works well and I would recommend it. I would rate OpenVPN Access Server an eight on a scale of one to ten.

I am currently working with OpenVPN Access Server for approximately 20 users. We use OpenVPN Access Server to connect to our company services from one IP address to secure these connections. OpenVPN Access Server is very lightweight, and the installation process is equally lightweight.

Single sign-on is very important for me because it is one of the principles of zero-trust architecture. In this architecture, each user has minimum privilege and uses one login and one password to connect to any services.

It is very easy to install and set up OpenVPN Access Server within the organization. Installing and using this service is very easy. OpenVPN Access Server provides a very detailed guide for installing it on your own server and integrating it with Google or Microsoft, making the process straightforward.

The best feature of OpenVPN Access Server is single sign-on, which is a very secure feature for information security.

Access control is effective in providing precise access to user groups and devices. In our company, we use a couple of services to control devices and users. One of these is a mobile device management solution such as Miradore or JumpCloud, and another solution to secure the channel to connect to company services is OpenVPN Access Server. Through the admin console, we can manage user rights and connections to company services.

I have no answer regarding what I would like to see improved in OpenVPN Access Server. I am not aware of future features, but the current features in the interface and the functionality of OpenVPN Access Server are very good. Everything in OpenVPN Access Server is very good, but the price is expensive.

I have been working with OpenVPN Access Server for around three years across two companies where I worked.

I find it very stable. All the issues were from my own mistakes, not from OpenVPN Access Server.

I find OpenVPN Access Server scalable and have not seen any limitations with it. The stability was very good, and I have no issues or problems. When we deploy and install OpenVPN Access Server, the principle is to install and forget.

Regarding technical support for OpenVPN Access Server, it is very good and very fast. Any issue was solved in five to ten minutes, or they sent me a description to solve my issue when I could not determine the problem myself. The technical support is very fast and very good.

Positive

I previously used L2TP/IPsec on my home router, and I am currently testing WireGuard for my home network because WireGuard is faster than OpenVPN Access Server.

The user interface of OpenVPN Access Server is very easy. It has two buttons: a download button and a cancel button, along with a checkbox to download only the profile. There are no additional settings, only log out and download options with the checkbox. This is a very simple interface that is very good for users, very good for admins, and very good for security.

We purchased OpenVPN Access Server directly from the OpenVPN market. I found it on the internet, researched it, connected to the company, and after testing, my chief decided to buy this solution for secure connection to our services. Our first purchase was from OpenVPN Access Server, and the next purchase was for the admin panel of OpenVPN Access Server, which was deployed on our rented server as a standalone server.

The main benefits that I have seen from using OpenVPN Access Server are that it is simple, easy, and secure.

I find it not cost-effective. It is not worth the money from a pricing perspective. However, it is a good investment for security and company information security. It is a good investment overall.

Apart from speed considerations, I use OpenVPN Access Server only for enterprise use and do not have a plan to use it for my home network. This is an enterprise solution and enterprise service, but not for a home user.

For authentication, we use SAML to authenticate users from Microsoft Entra ID or Google Workspace. SAML and single sign-on serve the same purpose. We use SAML and local authentication for the admin, and the admin can authenticate through SAML with a checkbox in the admin panel or user panel.

I have a recommendation that I can share with other organizations considering OpenVPN Access Server. From my previous job, we used OpenVPN Access Server, and when I moved to a new job, I proposed using OpenVPN Access Server, and the chief decided to implement it. In the future, when I see that my friends or friendly corporations or friendly structures want to use a VPN, I will recommend OpenVPN Access Server.

The main use case for OpenVPN Access Server is making internal web applications and using them within our organization. We have many internal apps, such as Re:dash for analytics, and internal peering and accessing different VM machines and internal servers.

I have hosted OpenVPN Access Server in my VM for one of those internal apps. From that VM, I have done the VPC peering to our different VPCs. And I have hosted, for example, Re:dash, an analytics tool for our internal company members. So we use VPN to whitelist them, and then they can internally use Re:dash for the analytics dashboard, querying, and connecting to the different databases and all.

The best features OpenVPN Access Server offers is whitelisting members in my company who have joined recently. It is really easy to use, and it is really easy to set up OpenVPN Access Server as an internal app.

When whitelisting members, I just add the name of the user. I go into User Permissions, add the name of the person I'm going to whitelist, and send them the credentials. They are able to log in and authenticate using an authenticator app and are easily able to onboard on OpenVPN Access Server and access internal apps.

It is easy to whitelist new apps that I'm going to host or when I've created a new VPC. I will do the VPC peering where I have hosted OpenVPN Access Server, and I can easily add the IP or CIDR of that particular new VPC or subnet which I'm going to use for my new app in the UI.

Before using OpenVPN Access Server, only developers mainly had access to databases. We can create read-only users for databases and internally give them access using OpenVPN Access Server. It has been really useful, as we don't have to give access to everyone, and just give access to OpenVPN Access Server, and they are able to access databases or internal websites.

The change has mainly led to the onboarding process being more smoothed out. It is really fast and saves developers' time. It saves my time as a DevOps engineer, setting up things for people.

The plan for OpenVPN Access Server could be improved. When adding new people, better plans for startups would be beneficial. I'm working in a startup and sometimes people think we should take the enterprise plan or not. If there was a dedicated plan for startups, it would be really helpful. For instance, providing store credit for OpenVPN Access Server through a startup program, similar to YC's program which gives credit to new startups.

UI-wise, OpenVPN Access Server is easy to manage, but the overall overview dashboard in the admin portal could be improved. Currently, you have to go through dropdowns to find where to add users or whitelist IPs. Creating an onboarding dashboard where an admin person can find these things easily would be beneficial.

I have been using OpenVPN Access Server for around two years.

OpenVPN Access Server has been stable since the last six months with no issues.

I have hosted OpenVPN Access Server in a VM. It does not utilize much memory or CPU on the VM. So far, I have been using around 40 users, and I did not need to scale it up. I think just scaling the VM would help in case it is needed.

I haven't used customer support from OpenVPN Access Server.

Positive

I haven't used any other solutions on the VPN side. OpenVPN Access Server was the first tool I have used for whitelisting people, but it did not give me any reason to move to any other product. It has been good.

I found some open-source documentation for setting up OpenVPN Access Server. It was really easy to set up initially. I got some networking issues from the VPC peering side, but it was resolved from open-source references.

I have utilized the access controls feature of OpenVPN Access Server, including an auto-login feature. For some developers who are heavily using OpenVPN Access Server, I allow an auto-login feature. For others, they still have to put the MFA code from the authenticator app.

I haven't seen exact numbers from the investment side, but OpenVPN Access Server has been really useful and saved a lot of time for developers.

The experience with pricing, setup cost, and licensing for OpenVPN Access Server is really good, not that expensive. I am easily able to add new users from the OpenVPN Access Server official website. I would suggest adding a startup plan for small startups would be really helpful.

Before choosing OpenVPN Access Server, I haven't evaluated any other options. Some of my colleagues recommended OpenVPN Access Server, and I went through it, and it has been really useful.

I would suggest for others looking into using OpenVPN Access Server, people find it difficult sometimes to self-host. Find the right documentation and go through it. Mostly it is all about networking. If your basics of networking are clear, you will be able to host it easily.

On a scale of one to ten, I rate OpenVPN Access Server a nine.

I use the solution for higher education resources.

The solution does its job and it is easy to customize.

The core VPN functionality is reliable and relatively easy to administer once it is deployed.

The licensing and purchasing workflow needs serious improvement. OpenVPN should provide clear documentation for customers who need multiple Access Server instances, different connection counts, AWS Marketplace subscriptions, PAYG licensing, and BYOL licensing under the same organization. Support and sales also need a clearer internal escalation path. We received guidance that pointed us back to AWS, then AWS clarified that OpenVPN needed to amend or handle the agreement, then OpenVPN proposed BYOL, then the BYOL setup ran into another account conflict. This was embarrassing for a paid enterprise product.

The product should include clearer in-app and portal-level guidance explaining what account types, billing models, and subscription models are compatible. Customers should not have to discover these limitations through a long email chain.

I have been using the solution for 7 months.

We have used OpenVPN Access Server previously and were trying to expand our existing deployment. The issue was not that we were switching from another vendor. The issue was that expanding an existing OpenVPN setup became unexpectedly difficult.

Do not assume the pricing or purchasing path will be straightforward, especially through AWS Marketplace. Confirm in writing whether your intended setup requires PAYG, BYOL, a Marketplace amendment, a separate AWS account, or a separate OpenVPN account. Also, budget staff time for the licensing process itself. The sticker price may look clear, but the real cost includes the time spent untangling subscription limitations, account conflicts, sales handoffs, and unclear guidance.

We considered continuing with OpenVPN because we already had operational familiarity with it and expected the expansion path to be simple.

The technical product is usable. The purchasing and licensing experience was the problem. Our organization needed a simple answer to a simple question: how do we run one 10-connection server and one 50-connection server? Instead of a clear path, we got days of back-and-forth, repeated explanations, conflicting assumptions, AWS/OpenVPN finger-pointing, delayed responses, and a final BYOL path that still ran into account conflicts. For an infrastructure product, that is not acceptable.

Customers should not need to coordinate between vendor sales, vendor support, AWS Marketplace, AWS account teams, and internal billing just to buy more capacity. OpenVPN should make this process dramatically clearer, faster, and more accountable.

In my day-to-day work, we deal with customer tickets related to VPN access, such as VPN password resets, regardless of the region they are from.

Beyond user support, we typically handle these tickets with a single request every three days, provide secure encrypted options, give remote access, and utilize multi-factor authentication, along with cross-platform support that includes Windows, Linux, and macOS, while also implementing split tunneling to manage company traffic through the VPN.

For example, if an employee is working from home, they need OpenVPN Access Server to connect to the office network, which allows them to handle database servers and other resources securely while working from anywhere in the country, improving security through encrypted access.

OpenVPN Access Server governs secure and compliant VPN access through centralized user management, allowing admins to manage user accounts, monitor activity, and enforce access policies efficiently.

In my organization, OpenVPN Access Server is deployed as a centralized VPN gateway in my Azure cloud, which is a public cloud environment, enabling secure access to company resources.

The best features OpenVPN Access Server offers include the ability to grant employees access to office applications quickly; without OpenVPN Access Server, employees would need to travel, but once access is granted, they can reach all office resources within a minute, reducing the resolution time from one to two hours to just one minute.

We reduce VPN bandwidth consumption by providing OpenVPN Access Server connection access based on specific geographical regions, with separate VPN access for West, Central, and Canada, ultimately lowering our overall bandwidth usage.

I find the verification of credentials against Active Directory crucial; if credentials are not verified, access policies should define user groups, IP restrictions, and route-based access meticulously.

Regarding other features, I believe we can improve OpenVPN Access Server by implementing high availability through load balancing between multiple servers, which increases access control and user administration capabilities, while also adding stronger multi-factor authentication and continuous monitoring using tools like Splunk.

While it is easy to use, I would suggest regular updates to OpenVPN Access Server software, particularly before SSL certificate expirations or OS upgrades to protect against vulnerabilities while optimizing split tunneling for efficient bandwidth usage.

I have been using OpenVPN Access Server for four years in my current company, PowerSchool.

The setup process in my organization was straightforward as it was already pre-set up when I joined, and I experienced no complex issues during installation.

In terms of cost savings, there are tangible benefits, although specific numeric values were not specified.

OpenVPN Access Server has positively impacted our organization by enabling remote issue resolution in minutes where previously critical alerts required hours of travel to fix, alongside improved productivity as employees can quickly access internal resources, file servers, and collaborate with teams.

I would rate OpenVPN Access Server as a 10 out of 10 because it significantly reduces downtime, enabling employees to address issues promptly.

For instance, if each engineer saves one hour daily on commuting, granting access with OpenVPN Access Server leads to significant productivity gains of around 300 hours saved monthly for the organization.

My overall review rating for this product is 10 out of 10.

My current use case for OpenVPN Access Server is for the security aspect, so I access the servers through the VPN. I disable the public access and only enable the private access.

In my opinion, the most useful function in OpenVPN Access Server is the user management feature, which I regularly use to manage the users and the concurrent sessions. When I have a very small number of connections and users, I used to manage it from OpenVPN Access Server from the UI, discarding or canceling the open connections and unused connections.

I am satisfied with the access control features of OpenVPN Access Server; that access control is a good feature for OpenVPN Access Server.

I have been using the role-defining feature with OpenVPN Access Server. There are different roles: the admin role and the normal roles, so I provide the regular operations roles to the regular users, and admin access is restricted to a few people.

I find the user interface of OpenVPN Access Server to be good; it is an intuitive user interface, so I appreciate that.

At the moment, I do not have any improvements I could think of on top of my head, but it is good; I do not have any improvements or suggestions on the product at the moment.

I have been working with OpenVPN Access Server for around seven to eight years so far.

I would rate the stability of OpenVPN Access Server as six out of ten.

The ability to scale with OpenVPN Access Server is again a six out of ten.

I do not have any complexities with scalability; it is not complex to scale or to increase the number of users or devices.

In my opinion, I have no idea about competitors; I have not considered any other options to compare OpenVPN Access Server.

The initial setup for OpenVPN Access Server is simple.

I confirm that I purchased the product directly from the vendor, OpenVPN.

I rate the price for OpenVPN as overpriced at the moment.

I can recommend OpenVPN Access Server to other users. I would rate this review a six out of ten.

Our primary use case for OpenVPN is remote connectivity for clients in the mining exploration industry, specifically for winter road and ice road access.

The most valuable features of OpenVPN are its ease of use, client familiarity, end-user familiarity, operating system integration, and price points. The scalability is a bonus since it allows running on any hardware. It's part of our client stack for all of our clients' VPNs and is a de facto standard for an endpoint VPN solution.

OpenVPN could improve in centralized management and enhance the GUI configuration steps. Although it's straightforward, if I don't know what I am doing, ease of use and configuration might be challenging. I would rate ease of configuration around a five or six out of ten.

I have had experience with OpenVPN for several years.

The stability of OpenVPN is very good. On a scale of one to ten, I would rate it an eight.

I would give OpenVPN a six out of ten for scalability, as it's usually a single user or single device.

I have not dealt with support or customer service, however, the documentation is good, and I would rate it a seven out of ten.

Neutral

We have not switched from another solution as OpenVPN is part of the default stack with most of our routers.

The initial setup for OpenVPN is straightforward.

It's a one-person job for implementation, and all of our technicians can deploy it.

There is not much to mention in terms of return on investment, other than providing standard VPN connectivity.

My experience with pricing is excellent as the pricing is free.

We are slowly replacing it with WireGuard solutions.

OpenVPN could improve the GUI and configuration steps. Overall, it's a straightforward deployment, however, it would be challenging for someone without technical knowledge. I would rate the solution an eight out of ten.

My main use case for OpenVPN Access Server is access to private subnets.

What I appreciate the most about OpenVPN Access Server is that it's very easy to set up.

OpenVPN Access Server has helped in meeting my organization's security requirements. I get to keep everything in the cloud private. People on the outside cannot see it, and this I use to connect.

There are ways OpenVPN Access Server could be improved. There are many small things, such as resetting MFA. There are tasks that require logging onto the server to run commands, which is not intuitive through the UI. If they had a one-click setup where you provide credentials instead of manually running commands, that would be beneficial. But it remains quite simple, which is why people appreciate it.

I assess the compatibility of OpenVPN Access Server with different client software and operating systems as quite easy. It's very good and simple to use. That's one of the reasons we use it. It's easy to set up the server side and the client side for users. It doesn't matter if it's Windows, Apple, Mac, or Linux - they're all very easy.

I have been using OpenVPN Access Server for seven to eight years.

OpenVPN Access Server scales with the growing needs of my organization. I have had some clients who expanded their usage, starting with three users, then increasing to 10, then to 20 users, each one in a different cloud with different licenses. It's not very easy to expand, and it would be beneficial if the process were simpler.

I had to use their customer service and technical support for OpenVPN Access Server. It was very good, and I would rate it an eight.

Positive

I have not really seen any ROI from OpenVPN Access Server. It's very hard to measure ROI as it's just a method of connection.

I had considered other solutions before choosing OpenVPN Access Server, such as AWS VPN and others, but OpenVPN Access Server is simply easier to use.

Regarding OpenVPN Access Server's advanced monitoring and reporting tools, I have not seen many features. They have a basic log, which is sufficient most of the time.

I found the setup and pricing of OpenVPN Access Server very easy since I've set it up many times. Even the first time wasn't particularly complicated.

I use the feature for hybrid deployment on OpenVPN Access Server in the cloud, not on-premises.

Overall, my experience with OpenVPN Access Server on a scale of one to 10 is a nine.