Protectimus vs. WorkOS

One thing we really like is getting OTPs and payment alerts through messaging bots. Unlike SMS, it’s free for us, secure, and users like it. It’s a way to send codes and notifications without extra costs. These messages are always right there for the user, easy to access on their phone.

We’ll keep using Protectimus. Been using it for years, no real issues, it just works. Covers what we need, different setups, mgmt, logs, all that. OTP via bots is really handy and saves us money. Support’s fine, they reply when needed. Overall, it does the job, so we’ll keep it.

I gave 10 points for their solution because the GUI got a fresh update and it’s really easy to use now. The old one had some annoying limitations, but the new layout is much more intuitive. On mobile it works good too. Managing relations between tokens, users, and resources is way smoother now.

We checked a few options before picking Protectimus. We looked at SafeNet Auth Management, Duo, and using Google Authenticator with our own backend. SafeNet felt really old-school — UI looks dated and the system’s kinda tricky to run & maintain. Duo’s solid, but it’s pricey and, more importantly, doesn’t offer full on-prem deployment. We need on-prem to handle auth for our employees on our own infra, so that was a dealbreaker. Google Authenticator is popular & free, but it’s just a client for generating OTPs — all the user mgmt, token handling, and policies would be on us.Protectimus gives all that out of the box. We can manage users & tokens centrally, set auth policies, and support multiple channels. That flexibility made it the best fit for our setup.