Skip to content
Notifications
Clear all

Am I the only one who uses it more for secure access than for VPN?

2 Posts
2 Users
0 Reactions
2 Views
(@datadog_dave)
Reputable Member
Joined: 2 months ago
Posts: 157
Topic starter   [#21270]

Hey folks,

I've been running Perimeter 81 for about 18 months now, and I've noticed my use-case has drifted pretty far from what I think is the classic "VPN replacement" pitch. Curious if anyone else is in the same boat.

For me, the killer feature isn't just tunneling all my traffic for privacy. It's the **secure, zero-trust access to specific resources**. I've got my homelab, a couple of cloud project VPCs, and our staging environment all segmented as "networks" in P81. My team and I can connect directly to *just* the app we need (like the Grafana or Prometheus server) without being on a full-blown VPN that exposes everything. The identity-aware part is huge for this.

My typical dashboard for access looks like this – I mostly live in the "Networks" and "Policies" tabs:
- **Main use:** Secure shell/rdp to specific servers (jump-host style).
- **Secondary:** Access to internal web apps (like our internal wiki or CI/CD).
- **Rarely:** The "Full VPN" mode for when I'm on super sketchy public Wi-Fi.

The VPN part feels almost secondary now. It's more about creating these secure, software-defined perimeters around individual services. It's like a more user-friendly, cloud-native version of setting up a bunch of individual SSH tunnels or a complex site-to-site VPN.

Anyone else using it primarily as a zero-trust / secure access service broker rather than a traditional VPN? Would love to hear how you've got your policies and network segments set up. Especially interested if you've integrated it with other IAM tools.


Dashboards or it didn't happen.


   
Quote
(@averyt)
Eminent Member
Joined: 3 days ago
Posts: 21
 

Oh absolutely! You've nailed the shift I've seen too. The "secure, specific access" is what makes it stick for teams. Once you start setting up those granular policies, going back to a traditional VPN feels like handing someone a master key when they just need to open the supply closet.

I've set up similar workflows for contractors. They only see the single app or database they need, and access drops as soon as their contract ends. The identity piece turns it from a network tool into an access management platform.

Honestly, the "Full VPN" mode on sketchy wifi feels like a legacy feature they keep because it's in the classic marketing, but it's not the daily driver.


Automate all the things


   
ReplyQuote