Keycard puts users, developers and companies in control of AI agents with real-time, adaptive permissions and complete transparency.

Joined December 2024
Today we're publishing the first draft of the Agent Baseline Software Factory Reference Architecture! An opinionated blueprint for securing increasingly autonomous software factories, built with folks across the community. It's open for feedback and contributions! agentbaseline.org/reference-…
7
32
5
198
25,014
AI agents can only be truly autonomous if they have the authority to act and that authority is tightly controlled. At ODSC AI West 2026, @ianlivingstone, Co-Founder & CEO of @KeycardAI, will present “Autonomy Requires Authority: Building Auth for AI Agents.” Ian brings 15+ years of experience across developer tools, security infrastructure, and platform engineering, including previous roles at Snyk and Salesforce. At Keycard, his work focuses on trusted, autonomous agents and the infrastructure needed to let them access tools and services safely. In this session, he’ll explore the shift from static credentials and inherited permissions toward ephemeral access, delegated authority, runtime context, and attributable agent actions. Join Ian at ODSC AI West 2026: hubs.ly/Q04yVWNV0
1
2
5
959
Really enjoyed talking with @MollySOShea about why we’re entering the systems engineering phase of agents. The raw intelligence is here, but making agents the default in software means figuring out how to make them cheap, reliable, and safe without nuking their ability to reason and solve problems dynamically. That is why we’re building auth for agents at @KeycardAI.
Ian Livingstone (@ianlivingstone) CEO of @KeycardAI says the biggest thing standing between today’s AI agents & true autonomy actually isn't intelligence.. “We have apparently AGI, but the real thing that stops us from having autonomous agents that actually work, like a self-driving car, is identity & access.” “Our systems weren't built for agents that are non-deterministic actors.”
4
28
1,867
I've always found Satya a salient thinker, and once again he nails it here. As AI gets more capable, we need to keep pushing to democratize access, increase choice, and build the controls that let us adopt it safely at any scale. We started @KeycardAI because we believe in a future where trusted, autonomous agents are everywhere, and everyone can access them and build them themselves. The problem is that agents break the security models we've relied on for decades because they were built for humans, not millions of non-deterministic machines acting on our behalf. Democratizing that future requires authn/z built for this new world: delegated, task-scoped and revocable access, identity carried through every tool call, a tamper-resistant record of who did what and on whose behalf, and intent-based authorization that can reason about what an agent is trying to do and apply deterministic boundaries dynamically at machine scale. That's the infrastructure we're building at @KeycardAI.
Any pursuit of superintelligence has to be grounded in the core principle that if the AI we build is not helping humanity and under human control, it's not worth pursuing. We also need to accelerate and spread the benefits of AI, such that they are diffused broadly across countries, communities, and companies. This requires a frontier ecosystem in which both closed and open-source models can thrive. And for firms, it’s imperative that they retain full control over their unique and tacit knowledge. Every organization should be able to build its own continuous learning loop/hill climbing machine, without becoming dependent on any one model provider, and have the ability to embed its own knowledge into models and weights they control. So, in this context, we welcome the research, focus, and deliberate pacing needed to get alignment right as the design goal. We also welcome ideas like "embedded evaluators" and the broader efforts to develop the mechanisms to make this more than just talk. The key is that this cannot be controlled by a handful of entities, but must have broad representation across the ecosystem, countries, and fields, including academia. This is the approach we are taking: broad access and choice at every layer of the AI stack; enterprise control of learning loops and models; and the “Code of Conduct” that underlies our own first party MAI models that we’ll publish tomorrow for public consultation.
3
1
13
1,425
I'm stoked for next week's Builder After Hours: Durable Agents with @MongoDB , @temporalio, and @KeycardAI (9/15, SF). Instead of the usual lineup of separate talks, @MelGoesTech is bringing a fresh take: co-presenting one shared architecture, then diving into each component. RSVP here: luma.com/hu0e1aks
3
1
6
554
Auth for agents is the biggest remaining gap between cool toy and production grade autonomy. The permission problem is perpetuated by an age of human driven computing where static roles and broad scopes were sufficient - it doesn’t work for agents - permissions have to be task scope and contextual to the progression of the task. We’re solving this @KeycardAI
i used instinct pretty aggressively on day one. it felt magical. and then it turned scary. giving it access to my email was already scary. then it started establishing sessions across apps and websites i use, on its own. watching an ai get that much access to act as me made me appreciate granular permissions on APIs a lot more. think about it. would you give even a clone of yourself unrestricted access to tools that could cost you money & happiness? i'd feel more comfortable with a dedicated app where sessions stay on device. but even then, i'd want it to ask before logging into anything on my behalf. and honestly, whatsapp/imessage doesn't feel like the right interface for this. i want to see where it's working, what it's doing in real time, and be able to step in before it does something i wouldn't have. that's why i prefer codex for example. the form factor is built around you trying to code, lives in projects and connects to your IDE easily. i'm not completely in the dark about what it's doing. ai agents don't have to live inside the apps or interfaces we already use. familiar interfaces help with adoption. they don't solve trust or control. if something can act as me, i need more than a chat bubble telling me it's done.
7
6
5
34
8,495
"Today you need an ability to actually like revoke an agent's access to a session, all things, whatever it is... It requires a central source of truth for hey, what's this? What's the agent capable of doing? What has it done potentially? What things does it ask permission for? And so then as a result of that, if I have a central system, I can click a button or you know, send an API call or have an automated response loop, do this thing that makes sure that all that access gets revoked." - @ianlivingstone
2
2
3
11
4,807
The technology that makes software factories possible is here. The secure design pattern for coding agents is what's missing. Join us at Black Hat for a panel with @Docker @snyksec @KeycardAI to discuss
The Great Loops Debate is published on @aiDotEngineer's YouTube The underlying technology that makes software factories possible is here today. The secure design pattern for coding agent is what's missing. Join @insecureagents at BlackHat to continue the conversation 👇
1
3
9
649
Keycard retweeted
Thanks to @KeycardLabs , @StainlessAPI , @Cloudflare , Temporal, @humanlayer_dev for a great evening chatting about Agentic Identity.
2
1
5
1,634
The MCP Debate is going down this Thursday at 2:30pm @aiDotEngineer CODE @dexhorthy challenges MCP, @ianlivingstone defends Is MCP > a bad protocol > rotting the context window > really the best way to do tool calls Find out Thursday!
4
8
4
44
26,548
Join us for a LIVE discussion next Thursday after @aiDotEngineer CODE Hear from @ianlivingstone @leonardtang_ @ProulxKerem @samuelcolvin on > the current state of AI security > building trustworthy AI > securing coding agents Luma link below, RSVP now to save your spot
2
8
2
19
4,360
Keycard retweeted
Alex Konrad
@alexrkonrad21 Oct 2025
Exclusive: Keycard, a new startup looking to secure AI agents for developers, has launched out of stealth with $38M from a16z, boldstart and others. Repeat entrepreneur and CEO Ian Livingstone (@ianlivingstone) says he's addressing the "missing pillar" in building with agents.
7
16
8
96
21,518
Excited to have @ianlivingstone, Co-Founder & CEO of @KeycardLabs, at the AI Security Summit 2025! He’s kicking off the Opening Keynote & joining a panel on Agentic Identity and Security. Don’t miss his insights on building secure, agent-native systems! 🔗 bit.ly/4mx5xM7
1
1
17
2,821
The recipe for building Trustworthy AI includes a strong auth strategy. We need a new solution to be rebuilt specifically for agents that takes their non-determinism into account and can make decisions based on the current context. You'll want to keep an eye on @KeycardLabs 👀
Agents break the fundamentals of traditional IAM systems - overtime, if you build them, as you did a traditional service, they will end up with god-mode privileges -- access to everything, for every user that interacts -- like katamari damacy. Ultimately, we need IAM systems that are highly dynamic, ephemeral, and only give agents access to systems on a per-task, user-specified basis that are deeply integrated into the agentic loop and provide active, run-time guarantees. If a user can't access something, an agent shouldn't be able too either, and, the user should have the ultimate control over what those agents can do on _their behalf_. The foundations of agentic security come back to the basics: how do you control what they can access, on behalf of whom, and what actions they perform with whose authority. This is why we're rebuilding IAM from the ground-up for the agentic era at @KeycardLabs.
1
12
3,987
Agents break the fundamentals of traditional IAM systems - overtime, if you build them, as you did a traditional service, they will end up with god-mode privileges -- access to everything, for every user that interacts -- like katamari damacy. Ultimately, we need IAM systems that are highly dynamic, ephemeral, and only give agents access to systems on a per-task, user-specified basis that are deeply integrated into the agentic loop and provide active, run-time guarantees. If a user can't access something, an agent shouldn't be able too either, and, the user should have the ultimate control over what those agents can do on _their behalf_. The foundations of agentic security come back to the basics: how do you control what they can access, on behalf of whom, and what actions they perform with whose authority. This is why we're rebuilding IAM from the ground-up for the agentic era at @KeycardLabs.
we hijacked microsoft's copilot studio agents and got them to spill out their private knowledge, reveal their tools and let us use them to dump full crm records these are autonomous agents.. no human in the loop #DEFCON #BHUSA @tamirishaysh
4
5
1
31
8,865
Join me at @aiDotEngineer World's Fair next week in San Francisco! I'll be discussing how to secure agents using OAuth and what we are building at @KeycardLabs. The talk is Thursday, June 5 in the security track. See you there!
3
3
19
2,170