Alright, let's talk about the Glide Identity "test drive." Having just come off their 30-day trial after evaluating them against Okta, Azure AD, and JumpCloud for a mid-market sales ops team rollout, I can tell you the onboarding experience is... illuminating. It's less a gentle introduction and more a controlled stress test of their own platform's philosophy. If you're used to the "click here to connect your Google Workspace" wizardry of other players, strap in.
The first thing you'll notice is that Glide doesn't baby you. Their trial setup assumes you have a concrete, albeit small-scale, use case in mind from minute one. You're not given a sandbox to play in; you're expected to start building your actual identity fabric, just with a limited number of users and connectors. This is a double-edged sword:
- **Pro:** You're evaluating the real product, not a demo. The friction you feel is genuine. You'll know by day three if their policy engine logic matches your brain.
- **Con:** The learning curve is steep. Their terminology for things like "Access Flows" and "Policy Bindings" is just different enough from the IdP giants to cause constant, minor mental translation delays. You'll spend the first week wondering if a concept is missing or just renamed.
Expect to be building, not just configuring. Their model is highly declarative. You'll be defining rules for JIT access to cloud apps, setting up federation to a test SaaS app (I used a spare Salesforce sandbox), and orchestrating step-up authentication scenarios from the get-go. The trial gives you full platform access, which is admirable, but also means you can paint yourself into a corner if you don't understand their hierarchy.
A few specific pain points and victories from my log:
* **The "Directory Hub"** is their core, and it's where you'll live. Connecting your first source (like Active Directory) is straightforward, but the real test is the attribute mapping and sync logic. It's powerful, but the UI for handling conflicts is buried. I had a few "why is this field not updating?" moments that required support intervention.
* **Support during trial is surprisingly responsive.** I suspect they're aware the product's power comes with complexity. My questions were answered within a few hours, often with detailed screenshots. This, of course, makes you wonder if this pace is sustainable post-sale.
* **The reporting and audit logs are available in trial, but with a 7-day retention limit.** This was actually a clever way to let me test the "break-glass" access review workflows without committing. Seeing a full, immutable log of every admin action (including my own missteps) built confidence.
* **No "easy button" for MFA rollout.** Unlike some competitors that push a branded MFA app, Glide seems agnostic. You're configuring authenticator apps, SMS, or email gates via their policies. It's more work upfront, but it felt less like vendor lock-in.
By the end of the trial, I had a working prototype for SSO to three apps and a privileged access workflow for our finance system. It worked. But the question it left me with wasn't about features—they're all there. It was about long-term maintenance. The model feels built for an era where identity is constantly in flux, which is great, but it also feels like it will require a dedicated, semi-expert resource to tend to it. That's the trade-off. You're not just buying an IdP; you're buying into a framework you'll need to actively manage.
So, go in with a real, limited-scope project. Don't just kick the tires. Try to break something and see how they help you fix it. That's the only way you'll know if their flavor of control is worth the cognitive overhead.