David Carney

to use the gateway instead, the gateway knows who you are.

So then all the API accesses have identity associated with them.

All the API keys can be withdrawn.

So that you end up with a single point of observability, control, and access for your entire team.

So those engineers get onboarded faster because they can just tell their peers, just point your coding agent at the proxy, everything just works if you're on tail scale.

That's the security team saying, great, we can get rid of all the security, all the API keys that are all over the place.

We can just tell people, just go to HTTP.

For us, it's HTTP colon slash AI.

And then every API call has your identity associated with it.

So you can just log everything.

And so we use Aperture internally right now and

I think we've got, I don't know how many tens of thousands of API calls across a big part of the company at this point.

We've just got every interaction with all of our coding agents going through Aperture right now internally.

So we have full visibility into how people are using AI.

all the requests, all the responses, the full logs.

We're mining it for tool calls.

And our security team gets to review it if they need to.

And we're working with third-party providers to start doing analysis of the logs in real time and after the fact.

There's all this stuff that is unlocked for us.

But initially, it just started with the simple idea of, we just want to solve the API key problem.