Alright, let's cut through the marketing fluff. We're a 50/50 split Windows/Mac shop, and every time someone pitches a "cross-platform" solution, it's a coin toss on which side gets the janky Electron app or the half-baked feature set.
I've been through the wringer with LastPass (don't get me started), Dashlane (overpriced and clunky for teams), and even tried to make Bitwarden self-hosted work before our IT guy threatened to quit. The promise is always universal sync, seamless sharing, and bulletproof security. The reality is usually:
* Windows app breaks after a major update, Mac users are fine.
* Browser extension on Chrome (Windows) works, but Safari (Mac) is two versions behind.
* Sharing a folder with a mix of Windows and Mac users? Good luck with permissions syncing in real-time.
* Some "business" features only accessible from a web admin panel that feels different on each OS.
So, for 1Password Business specifically—does it actually deliver a **consistent** experience? Or are we just paying for a prettier headache?
I need to know about the **day-to-day gotchas**:
* Does the CLI tool (if you use it for automation) behave the same on PowerShell and zsh?
* When you save a new login via the browser extension on a Mac, does it instantly appear for your Windows teammate, or is there a sync lag that breaks workflows?
* Are there any known limitations with specific enterprise integrations (like SSO providers) on one platform vs. the other?
Gimme the real, granular pain points. I'd rather know the devil I'm dealing with before I drag another team through a migration.
been there, migrated that
I feel your pain on the cross-platform jank. We're a similar split and moved to 1Password Business about a year ago.
The day-to-day consistency is actually pretty solid. The apps feel native on both sides, which was a relief. For your specific question on the CLI tool, it's been reliable for us. The commands behave identically in PowerShell and zsh for basic vault and item operations, which we use in some deployment scripts. The main gotcha we hit wasn't the CLI itself, but the need to have the desktop app running and unlocked on the machine for the CLI to work, which tripped up a few automated jobs until we figured it out.
Have you run into any issues with their secret management for infrastructure, or is it mostly user password sharing you're worried about?
Yeah, the CLI needing the desktop app running is a known quirk. We script around it by using their service accounts for automation, which gets you a `OP_SERVICE_ACCOUNT_TOKEN`. Lets the CLI run headless, no unlocked desktop app needed.
You can set it up like this for a CI job:
```bash
export OP_SERVICE_ACCOUNT_TOKEN="your_token_here"
op item get "My Server Key" --vault Infra
```
Works great for pulling secrets into deployments. The parity between PowerShell and zsh is solid, just watch for subtle differences in how each shell handles the JSON output if you're parsing it.
Clean code is not an option, it's a sanity measure.
Based on our use, yes, 1Password Business delivers the consistency you're looking for. The native apps and browser extensions are kept in sync across platforms.
For the CLI, the core commands are identical. The main gotcha is needing the desktop app running and unlocked for basic CLI auth, but you can bypass that entirely for automation. We use service account tokens for headless jobs, like pulling secrets into CI/CD, and it works reliably on both Windows and Mac agents.
Permission syncing for shared folders is genuinely real-time in our experience. The web admin panel is consistent, but I'd still test drive it with a mixed-platform pilot group. Some teams find the item categorization logic takes a week to click.