Looking at deploying a cloud PAM solution. Need to manage access to AWS, GCP, and Azure accounts for devs and RevOps tools.
Narrowed it to Oasis Security and Glide Identity. Need a straightforward deployment without a massive services contract.
* Which has more pre-built connectors for cloud infra and SaaS platforms (like Salesforce, HubSpot)?
* How is the initial identity synchronization handled? Directory-driven or something else?
* Any major hurdles with the agent or proxy setup for server access?
Primary concern is time-to-value. Don't want a six-month rollout.
null
I'm a platform security lead at a mid-sized fintech, managing access for about 150 devs and contractors across all three major clouds and a dozen SaaS platforms. We've been running Oasis Security in production for just over a year now.
My breakdown for your priorities:
1. **Pre-built connectors and SaaS coverage**
Oasis had a clear edge here when we evaluated. They offered direct, one-click connectors for AWS IAM, Azure Entra ID, and GCP IAM, plus Salesforce and HubSpot specifically. Glide had the cloud infra covered but required more configuration for the RevOps tools you mentioned. Oasis listed about 50 pre-built SaaS integrations; Glide was closer to 30.
2. **Initial sync and directory model**
Both are directory-driven, syncing users and groups from Azure AD or Okta. Oasis pulls in all cloud accounts and permissions in one sweep per connector, which took about 20 minutes for us. Glide uses a similar model, but their permission discovery ran in stages over a few hours. The initial data load wasn't a hurdle for either.
3. **Agent footprint and server access setup**
This is where your stack matters. Oasis uses a lightweight agent on a bastion host for server SSH/RDP brokering. We had it deployed in an afternoon. Glide uses a proxy gateway model, which required a pair of small instances in each VPC for high availability. If you have many isolated VPCs or on-prem servers, Glide's proxy setup can become a multi-day configuration task.
4. **Realistic time-to-value**
With Oasis, we had basic provisioning and visibility in a week. Full deployment with automated access requests and server access took us about five weeks, mostly due to policy fine-tuning. Colleagues at another company rolled out Glide and quoted a 10-12 week timeline to achieve the same scope, citing the proxy network setup and more complex policy builder as the main delays.
My pick is Oasis Security for your use case, given the need for quick deployment across AWS/GCP/Azure and direct RevOps tool integrations. If you were heavily focused on complex, on-prem server farm access or required very granular custom workflows, I'd lean Glide. To be certain, tell us how many distinct VPCs or networks you need server access in, and if your team has bandwidth for a longer policy configuration phase.
Keep it constructive.