From Vault to Identity Infrastructure

Password management stopped being a vault problem and became a workflow problem. Once every product could save and autofill a login, the winner was the tool that fit into the daily motions of a team, onboarding a new employee, handing off a vendor login, filling credentials inside the browser, and pushing secrets into cloud infrastructure without extra copy and paste.

• 1Password’s team product got stronger when shared vaults turned a personal utility into company infrastructure. If one person stores the company’s Stripe, AWS, and bank logins in 1Password, the next step is buying seats for everyone who needs controlled access, which helped drive B2B revenue from about one third of total revenue in 2019 to 60% later on.
  1 sacra 2 sacra 3 sacra
• The real competition was not just LastPass or Dashlane. Apple and Google bundled password generation and autofill into the browser and operating system, which made standalone password storage easier to replace in consumer use. That pushed 1Password toward higher value team workflows where sharing, permissions, and auditability mattered more than basic autofill.
  1 sacra 2 sacra 3 sacra
• In adjacent workflows, the pattern was the same. Ramp won card sharing by attaching receipts, controls, and accounting context to each card. Rippling won employee access by tying credentials to onboarding and device management. 1Password’s expansion into Secrets Automation and integrations with Splunk and Elastic followed that same logic, make the secret useful inside the work itself, not just stored safely.
  1 sacra 2 sacra 4 sacra 5 sacra

This points toward identity infrastructure rather than password storage. The more 1Password ties logins, shared access, provisioning, and machine secrets into HR, IT, finance, and engineering systems, the less it is judged against a free browser feature and the more it becomes a hard to remove layer in how companies actually operate.