Infisical raises $40M at $600M: the new problem is giving your agents keys without handing them the passwords
Direct answer
On October 27, 2026, Infisical announced a $40 million Series B at a $600 million valuation, led by investor Elad Gil, with participation from Gradient and Y Combinator. The San Francisco company builds infrastructure for managing secrets, certificates, encryption keys and privileged access. Its bet for the agent era is Agent Vault: letting an agent work inside critical systems without ever receiving the password, API key or token that unlocks those systems.
The problem Agent Vault tries to solve
- Agents need keys to work: to act, an agent must touch source code, databases, cloud infrastructure and payment APIs. All of that requires credentials.
- Credentials inside the model are a potential leak: if the key enters the model's context, it can leak in an attack, land in logs, or be sent unintentionally to the model provider or another tool.
- Infisical's answer: the company defines the access each agent needs and lets it act without handing over the real credential. The agent gets the result, not the key.
- The CEO's line: co-founder and CEO Vlad Matsiiako put it this way: you would not give an employee unrestricted access to every system in your company, and agents should get no different treatment.
The round's numbers, with their label
- $40 million and $600 million: the Series B amount and valuation announced October 27. The prior round, a $16 million Series A in June 2025, was also led by Gil.
- Company-reported scale: more than 1,300 customers and 300,000 developers, with 10 billion secrets secured per day. Customers named by the company include Airbus, Volkswagen, Hugging Face, Wise and OpenRouter. These are company figures, not audited in the announcement.
- Use of funds: product development, engineering and go-to-market hiring, and expansion of security infrastructure for agents.
- The market signal: the round landed the same week Bank of America emailed customers warning them not to share usernames and passwords with outside services, AI agents included, and that they are responsible for activity resulting from that access, as a spokesperson confirmed to TechCrunch. Banks are already seeing unauthorized agents in customer accounts, Axios reported on October 22.
What it means for your business
- Treat every agent as a new user: with its own identity, task-scoped permissions and logs of what it did. An agent holding the master password is the biggest security risk you can create by accident.
- Apply least privilege: the scheduling agent touches only the calendar; the billing agent touches only billing; none touches everything. If an agent needs a key, ask whether it can work through mediated access instead of the real key.
- Rotate and revoke: credentials used by agents should rotate and be revocable within minutes, just like the access of a departing employee.
- What to watch: whether your agent provider offers secret vaults, agent identities separate from users, and audit logs of every action. Those three pieces are already enterprise procurement requirements, not extras.
Want AI that works for your business?
Message us on WhatsApp and let's talk about automation and AI agents for your business.
WhatsApp inicIARelated articles
- OpenAI will train frontier models without live internet
- Privacy and data: what happens to your customers' information
- What to do when your AI agent makes a mistake
Frequently asked questions
What is Infisical's Agent Vault?
It is the product that lets an AI agent access systems and APIs without receiving the real password, API key or token. The company defines each agent's access, and the agent gets the result, not the credential.
How much did Infisical raise, and at what valuation?
$40 million in a Series B at a $600 million valuation, announced October 27, 2026. The round was led by Elad Gil, with Gradient and Y Combinator.
Why is giving credentials to an agent risky?
Because a credential inside the model's context can leak in an attack, land in logs or be sent to third parties. A bank can also mistake the agent for an attacker and lock the account.
What should my company ask an agent provider for?
Agent identities separate from user identities, task-scoped permissions, a secret vault or mediated access, fast rotation and revocation of credentials, and audit logs of every action.
