Having just finished a six-month evaluation of secure access solutions for a similarly sized consultancy, I can tell you that whether Perimeter 81 is "worth it" depends entirely on which of your problems you're trying to solve. If you're looking for a simple VPN replacement for remote staff, it's likely over-engineered and over-priced. If you're dealing with a multi-cloud, contractor-heavy, compliance-driven environment, then the conversation changes.
Let's break down the reality for a 50-person marketing agency. You're probably dealing with:
* A mix of on-prem tools (maybe a NAS for creative assets), SaaS platforms (Google Workspace, Adobe Cloud, project management tools), and cloud infrastructure (AWS/Azure for client sites or data pipelines).
* A rotating cast of freelancers and contractors who need access to specific things, but not everything.
* Zero dedicated security or network staff. The person managing this is likely the most technically proficient person in the office, who also has their actual job to do.
* A genuine need to demonstrate security posture to enterprise clients during audits.
Perimeter 81's strength is in segmenting that access cleanly. The concept of "network as a service" isn't fluff—it lets you define micro-segments without touching a physical firewall. For example, you could create a policy that says:
* `Contractor_Design` group can only reach `tcp/443` on the IP of the Adobe asset server and the `marketing.example.com` subdomain.
* `Full_Time_Staff` group gets the "marketing" network segment plus the AWS VPC where the analytics database lives.
* `Finance` group only gets the accounting SaaS app.
This is configured in a central portal, not via CLI on a box in a closet. The agent on the user's device enforces it, regardless of whether they're at home, a coffee shop, or a client's office. This is where the premium cost is justified.
However, the cost is the primary blocker. You're not just paying per user. You're paying for the gateway compute time, and the data egress. For a team that transfers large video files or raw design assets daily, the egress fees can become a significant and unpredictable line item. You must model this.
**The blunt assessment:**
* **Worth it if:** Your primary pain is granular, auditable, zero-trust access for mixed workforces across multiple cloud and on-prem resources, and you have the budget to absorb the variable data costs.
* **Not worth it if:** Your team just needs a secure tunnel to a central office to reach a file server and you're balking at the complexity of OpenVPN. Look at Tailscale or a traditional business VPN appliance.
* **The major pitfall:** Underestimating the data transfer costs and the time required to correctly define your initial network segments and policies. It's a paradigm shift from a traditional VPN.
You are paying for the abstraction of network hardware and the policy engine. If you don't need that abstraction, you are paying for a very expensive VPN client.
just the data
latency is a liar
I'm the technical lead at a 60-person digital analytics firm where I've managed our Zero Trust deployment for the past two years, running Perimeter 81 in production to secure access to our analytics clusters, internal tools, and client data warehouses.
* **Real Pricing and Scaling Cost:** List price for their Business tier starts around $12/user/month for annual commitment, but you'll likely negotiate to $8-$10 for 50 seats. The significant hidden cost is for their dedicated gateways. If you need low-latency access to a specific cloud region or an on-prem resource, a dedicated gateway instance is required, adding roughly $200/month per region. For a multi-cloud setup, this can double your effective cost.
* **Deployment and Management Effort:** Initial policy setup for a group of 50 with mixed roles took about 40 engineering hours. The time sink isn't the UI, which is clear, but defining and testing the precise network access rules for each team (e.g., data team to AWS VPC, designers to NAS, freelancers to only the project management tool). Once defined, onboarding a new user takes under two minutes, and offboarding is instantaneous, which is a major operational win.
* **Clear Win Over Traditional VPNs:** The win is in access segmentation and auditing. You can build a policy that grants a contractor access only to `asana.company.com` and a specific S3 bucket prefix, with no ability to even see other network segments. Every connection is logged with user, policy, and target resource. For client security questionnaires, we can provide exact access reports in minutes.
* **Where It Breaks or Is Cumbersome:** It introduces a routing hop, so latency-sensitive applications like large file transfers from a local NAS can suffer. We saw transfer times increase by 30-40% compared to a direct LAN connection. Also, it is purely a network access layer. It does not handle application-level SSO or granular SaaS permissions, so you still need an identity provider for that.
I would recommend Perimeter 81 specifically if your primary need is airtight, auditable network segmentation for contractors and between internal teams across hybrid environments. If your pain point is mostly just securing employee SaaS logins, a pure ZTNA tool or even a well-configured IdP with device trust is more cost-effective. To make the call clean, tell us what percentage of your users are contractors needing narrow access, and whether you have any latency-critical on-premises file workflows.