Hi everyone! 👋 I'm setting up shared credential management for our small devops team. We need to securely store and access things like AWS keys, database passwords, and API tokens.
We've narrowed it down to 1Password Business and Onelogin. Could someone explain the key differences for our use case in a beginner-friendly way? I'm especially curious about:
* How easy it is to share a single login across a team (like a shared service account).
* Which one has better integration with CLI tools for automation.
* How the emergency access or "break glass" procedures work.
I've heard 1Password has secrets automation, but Onelogin might be stronger on the SSO side. Any hands-on experience would be amazing! Thanks in advance for helping a newcomer out 😊
Hi there! I'm a junior marketing ops person at a SaaS company of about 80 people, and we run 1Password Business to share our social media and ad platform logins.
**Sharing Single Logins:** 1Password uses shared vaults. You put a login in a vault and add team members to it; it's very intuitive. Onelogin is built more for SSO (single sign-on to apps), so sharing one credential feels like a workaround in their portal.
**CLI & Automation:** 1Password has a dedicated CLI tool (`op`) you can use in scripts to fetch secrets. I've used it for basic API token pulls, and it works. Onelogin's CLI tools felt more focused on user provisioning and SAML configuration, not as straightforward for grabbing a database password in a script.
**Emergency Access:** With 1Password, you can set up a designated teammate as an "Emergency Kit" holder. They can take over your account if needed. Onelogin has a similar "break glass" admin role, but it's part of their broader access management system, which has more steps to configure.
**Pricing & Simplicity:** At our size, 1Password Business is about $8 per user per month. Onelogin's pricing wasn't as clear publicly and seemed to start a bit higher for the features we'd need. The setup for 1Password was faster for our simple goal of sharing passwords.
I'd recommend 1Password for your case. It's simpler and feels purpose-built for what you described: a team sharing a pool of credentials and needing CLI access for automation. If your primary need was to manage employee access to hundreds of internal web apps (SSO), I'd lean toward Onelogin. To decide cleanly, tell us: is this *only* for shared service accounts, or will you also need full SSO for company tools like Google Workspace or GitHub?