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.

It was exceptionally easy to install and configure. It works well.

It allowed me to get through geofencing to work abroad.

The configuration is easy on both the server and client side.

Currently, the solution works as it is for our requirements. We are still evaluating full scope of options and fine-tuning e.g. split VPN to allow LAN access whilst on VPN.

New customer.

Works without issues from challenging locatios.

None. New requirement.

The setup cost was reasonable.

I considered using Norton and Nord VPN.

I would rate it a ten out of ten.

I use OpenVPN Access Server to restrict access to internal AWS-hosted resources.

I have been using OpenVPN Access Server for several months as a lightweight, cost-effective VPN solution deployed on an EC2 instance. My primary requirement was to secure access to internal AWS resources without adding unnecessary complexity or overhead. OpenVPN Access Server met that need well.

The setup process is straightforward, with good support for common operating systems. The admin interface is clean, making configuration and user management easy even for teams without deep networking expertise.

The lack of an official Linux client is a clear gap. The community-maintained alternative is functional but not as stable or polished as the official Windows and macOS clients.

I have used this solution for 3 years.

There were no stability issues.

There were no scalability issues.

Having an officially supported Linux client would significantly improve usability and reliability across all platforms.

Our infrastructure in AWS needed to be accessed only by authorized users. OpenVPN gave us the option to have our employees access the server securely from all over the world.

Some of our IT infrastructures, such as file servers and dev/testing servers, were on-premises. Maintaining and scaling these became troublesome. So, we decided to move to the AWS cloud. Once in the cloud, we needed our employees to have access from all around the world. We looked up the VPN options in AWS and OpenVPN seemed to fit our need. We have been running it for several months and it is working great for us.

To be honest, everything came pre-setup out of the box and we did not have to change much of the configuration. We do love the MFA option that forces all the users to comply.

We used Palo Alto before, but the cost was out of our budget.

We recommend checking the compliance you need for the project and picking the product that meets those requirements within the best price. For us, it was OpenVPN.

We considered Palo Alto and Cisco as alternate solutions.

We were surprised how straightforward it was to integrate with AWS. We had a little hiccup with installing the certificate, but we read the documentation and everything was sorted out. We would recommend creating tutorial videos of setup and common troubleshooting. People prefer to watch video guides rather than read documentation.

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.

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.

We connect to the OpenVPN using a VPN for any computer not directly connected to our local server. This is necessary because multiple offices need to use the software developed on the local server.

We use OpenVPN Access Server on every device that needs to connect to the server. It's the best way to achieve better latency and connect remotely.

It is easy to use. We connect to the server and launch our software in between.

It should automate our processes. Our developers continuously improve the software, but we'll continue using PowerBuilder unless we undertake a significant project to migrate to a different platform, possibly Java. Additionally, we need RPA software. I've also looked into Twilio, which provides automated SMS alerts. We're assessing how useful that service could be for our needs.

It's stable.

We need RPA software and automatic testing software to make any improvements.

We want to scale internationally. To do this, we'll create a blank copy of our software, replicate our database architecture schema, and then prepare it for the new location. Additionally, we plan to implement automation tools, such as RPA and automated testing, to catch up on the technological aspects we've been lagging. Since our current software is built on PowerBuilder, starting from scratch is challenging. Therefore, we'll continue using it while integrating new resources to improve our system.

It is suitable for small to medium businesses. We have three locations: one laboratory and two offices. We have approximately 120 to 130 employees across these locations.

The initial setup was very easy, and one system administrator did it.

It's efficient. Connecting to the local server without it would be much more difficult. Every employee who works from another office has to use it, so it's essential.

It is not that expensive. It makes it more efficient for some people's jobs.

Overall, I rate the solution a nine out of ten.

We use the solution to access FTP pages and file sharing.

The solution is reliable, easy to use, and open source. It's free at no cost.

I have been using OpenVPN Access Server as a user.

The product is stable. There are no interruptions, and it works smoothly.

The solution’s scalability is fine. It encompasses security advances and investments in the industry.

The solution is free. It is worth the money.

The tool works fine and doesn't bother me all day.

I recommend the solution.

Overall, I rate the solution a ten out of ten.

We use the solution to communicate with our servers located in the office.

OpenVPN Access Server is a simple and easy-to-use solution that I can use myself without anybody's help.

The solution should provide a faster connection, and its security could be improved. The solution’s stability could be improved.

I have been using OpenVPN Access Server for two to three years.

I rate the solution a seven or eight out of ten for stability.

Around 50 users use the solution regularly in our organization.

I rate the solution’s scalability an eight or nine out of ten.

The solution's initial setup is easy.

On a scale from one to ten, where one is complex and ten is easy, I rate the solution's initial setup a seven or eight out of ten.

The solution’s deployment did not take much time.

The solution was deployed on the cloud in our organization. More than 100 people are needed for the solution's deployment and maintenance.

Overall, I rate the solution an eight out of ten.

OpenVPN Access Server provides remote secure access. 

OpenVPN Access Server needs to have fewer updates. 

OpenVPN Access Server is stable. 

The tool is scalable. 

The tool's deployment is straightforward. It took ten minutes to complete. 

OpenVPN Access Server is a cheap corporate solution. 

I rate the product a nine out of ten.