OpenVPN CloudConnexa / VPN and ZTNA as a Service

My main use case for CloudConnexa  is using the VPN solution, which is the primary VPN solution for our company. In my company, a lot of people are working remotely, so they need a VPN as the primary VPN solution. Previously, we were using a few other VPNs, but it was not consolidated, so we started looking for a cloud-based VPN solution. We found CloudConnexa  and have been using it for all our remote employees.

CloudConnexa has positively impacted my organization because it is easy to deploy. If we want to spin up a new tenant, it is not difficult; it takes about 30 minutes to spin up a new solution or a new tenant for us.

This quick deployment has led to measurable benefits because the remote employees' onboarding process is straightforward, and we do not want to spend a lot of time on deploying agents and upgrading those systems. That kind of flexibility is useful.

The best features that CloudConnexa offers are its good pricing and affordability. It has a lot of flexibility; we do not have a complex structure to set this up, it is easy, and it supports both IPsec and host-based connection. It also acts as a transit gateway because we can route the traffic between host-to-host. That flexibility, particularly the access group feature, is the best feature CloudConnexa provides that other VPN providers do not have.

The transit gateway feature of CloudConnexa allows me to connect applications running in two different AWS  accounts via the VPN solution. I have a lot of cloud accounts, and in some cases, I need to build a VPN between those accounts. CloudConnexa facilitates those connections by routing the traffic, and since we already have connections between CloudConnexa to both AWS  accounts, I do not have to spin up a new VPN.

CloudConnexa can be improved, particularly because they have many features, but they do have stability issues. I see many times where the stability is not good, and I have seen a few outages with a huge ETA for those outages. It takes a while for them to give a proper ETA, and they often come up with workarounds that I need to run for a long time to address stability. For the log stream, they have a facility to forward logs, but they do not have a good dashboard to filter those logs in their dashboard itself, which for troubleshooting often contains meaningless information.

The support is good, and they respond immediately, but the stability issues and the engineering work need to be improved.

Stability and logging are the main areas that need improvement.

I have been using CloudConnexa for more than three years.

CloudConnexa is not completely stable; it still has some stability issues.

On a scale of one to ten, I would rate CloudConnexa a seven because the main issue is stability. In my three years of experience, I have seen more than ten outages.

The deployment process of CloudConnexa is quick, which is faster, but regarding scalability, if you are looking for stability-related issues, this is definitely not a stable solution.

Customer support is fast; we get quick support.

I previously used GlobalProtect , FortiClient , and FortiGate. Each has its pros and cons. For GlobalProtect , the support is not good; if something goes wrong, it takes a lot of time to reach their support. For FortiClient , it does not have the flexibility to handle endpoint upgrades; if there is a critical update, we have to upgrade every system individually, which is a major pain point.

I have seen a return on investment because CloudConnexa saves costs for our company, and for deployment, it is quick, allowing us to save time.

My experience with pricing, setup cost, and licensing is very positive. The pricing is straightforward; it is the most affordable solution available. The setup is also simple, and we can do it immediately. The licensing process is not complicated at all; it is just two pages where we add a license and pay, which updates our license immediately.

Before choosing CloudConnexa, we evaluated Twingate  and Harmony SASE  as options.

My advice to others looking into using CloudConnexa is that if they are looking for a simple setup and an affordable solution, this is the best choice. I would rate CloudConnexa a seven out of ten overall.

Hybrid Cloud

Amazon Web Services (AWS)

What do you like best about the product?

Simple, stable connection to customer networks. Additionally, there is a ready configuration for Teltonika routers, which significantly simplifies the setup.

What do you dislike about the product?

I can't find the wizard directly. I wish I could add and edit new devices and networks more easily, because those are the only things I do in it.

What problems is the product solving and how is that benefiting you?

We want to be able to quickly access customer systems and networks for support. My employees are not network technicians and should therefore be able to set up a functioning VPN tunnel to the customer easily and promptly.

What do you like best about the product?

It's easy to deply, manage and get support.

What do you dislike about the product?

We are happy with the solution provided.

What problems is the product solving and how is that benefiting you?

It's to enable secure access to systems with SSO.

What do you like best about the product?

What I like best about OpenVPN CloudConnexa is how simple it makes secure private networking. I don't need to manage my own VPN servers, certificates, or complex network setup. most things just out of the box. The cloud-managed approach is very convenient. I can connect users, servers, and cloud resources without worrying about infrastructure maintenance. I also like the strong security model. Authentication, encryption, and access control feel solid, which gives confidence when handling sensitive systems. From a backend and infra point of view, it's great for connecting services across different clouds. Whether something is on AWS, GCP, or on-prem cloud, Connexa can connect them securely. Another thing I appreciate is the centralized dashboard. Managing users, connections, and access rules in one place is much easier than handling multiple VPN configs. It feels like a modern VPN solution, not an old, heavy network tool.

What do you dislike about the product?

One downside is that advanced networking concepts still require learning. While the basics are easy, deeper configuration can be confusing for new users. The UI could be more intuitive in some areas. Certain settings are not immediately clear without reading documentation. Pricing can be a concern for large teams, especially when many users or endpoints are involved. Another limitation is less flexibility compared to fully self-hosted VPNs. You trade some control for convenience. Debugging connectivity issues sometimes requires patience, especially when multiple networks and policies are involved.

What problems is the product solving and how is that benefiting you?

OpenVPN CloudConnexa solves the problem of securely connecting people, services, and systems across different locations without building complex VPN infrastructure. Traditionally, setting up a secure private network means managing servers, firewall rules, certificates, and constant maintenance. CloudConnenexa removes most of this complexity. The biggest benefit for me is speed of setup. I can connect a new environment or user in minutes instead of days. It also improves security posture. Access is controlled centrally, and connections are encrypted by default, reducing risk. From a backend and ops perspective, it makes service-to-service communication safer. Internal APIs and databases can be accessed without exposing them to the public internet. Another major benefit is support for remote teams. Developers, admins, and support staff can access internal systems securely from anywhere. It reduces operations overhead. There is no need to patch VPN servers, rotate certificates manually, or monitor infrastructure health constantly. CloudConnect also helps with scaling. As teams or service groups grow, the network expands without major new work. It improves reliability. Cloud-managed networking is more stable than many homegrown VPN setups. Another benefit is better visibility and control. You can see who is connected and what they can access and revoke access quickly if needed. It also supports zero-trust-style access. Users only get access to what they need, not the entire network. Another benefit is less dependency on network experts. Even teams without deep network knowledge can manage access and connections without breaking things. It also makes onboarding new team members easier. New developers or admins can be given access quickly without sharing VPN configs or complex setup steps. CloudConnexa helps with clean environment separation. Production, staging, and internal tools can stay isolated while still being reachable in a controlled way. It reduces security risks from exposed services. Internal services don't need public IPs anymore, which lowers the attack surface. Another useful point is faster incident response. if something looks suspicious. Internal services don't need public IPs anymore, which lowers the attack surface. Another useful point is faster incident response. If something looks suspicious, access can be disabled immediately from one place. It also supports temporary access use cases. Contractors or short-term users can be granted access for a limited time and removed easily later. CloudConnexa also helps with fewer configuration mistakes. Since most networking rules are managed centrally, there is less chance of someone misconfiguring a VPN file or opening access by mistake. It makes day-to-day access management simpler. When roles change or someone switches teams, permissions can be updated quickly without touching multiple systems. Another helpful thing is better consistency across locations. Whether a team member is working from home, the office, or another country, access behavior stays the same, which avoids confusion and access issues.

What do you like best about the product?

I like using OpenVPN CloudConnexa for a secure connection to my AWS. I appreciate that only allowed employees can access my AWS, which is important for maintaining security. I find the ease of configuration a major plus, as well as the support speed. Additionally, I value the limited IP range capability that makes our AWS more secured. The initial setup was easy.

What do you dislike about the product?

Our security corporate policy would like OpenVPN CloudConnexa to publish IP range to do whitelisting.

What problems is the product solving and how is that benefiting you?

I use OpenVPN CloudConnexa to secure connection to my AWS, ensuring only allowed employees can access it. I like the ease of configuration and fast support. Limiting the IP range enhances my AWS security.