1Password targets machine and agent security

This push turns 1Password from a tool employees use at login into an access layer that can sit inside production software and AI workflows. In the old model, the main buyer was an employee or IT admin paying for password storage. In the new model, engineering and security teams can buy 1Password to deliver secrets to service accounts, CI/CD jobs, and AI agents at runtime, while consumers can use it to let assistants sign in and act without handing over permanent credentials.1 2 3 4 5

• On the enterprise side, 1Password already had the bridge product for this move. Secrets Automation, Connect, Service Accounts, and Credential Broker let software fetch API keys, tokens, and other secrets when it runs, which puts 1Password into developer security and machine identity budgets that were historically served by tools like HashiCorp Vault.2 3 5
• On the agent side, the product is not just password autofill for a human. 1Password for Agents and Unified Access are designed so an assistant or coding agent can get approved credentials for a task, use them with time limits and audit trails, and avoid exposing raw secrets in prompts, logs, or local files.1 4 5
• This also widens the internal buyer map. Earlier expansion came from turning team vaults into an organization wide seat sale, with B2B mix rising from 33% of revenue in 2019 to 60% by 2024. Machine access adds engineering as a budget owner, while personal and enterprise agent security adds security teams that care about governance, approval, and traceability.2 3 6

The next step is a broader identity platform where the same system governs employees, devices, workloads, and AI agents. If 1Password can keep moving from storing secrets to brokering access at the moment work happens, it shifts from a replaceable password manager into infrastructure that sits directly in the path of how companies deploy automation.1 4 5