Sagar Batchu

But when you think about an API and the journey a development team goes on, I think it's really more than that. It's build, it's test, and it's run. Those are three big phases that I see in the API lifecycle today that aren't really serviced by great products. I think there's point solutions and there's... kind of things at the end of the lifecycle and before the lifecycle.

But when you think about an API and the journey a development team goes on, I think it's really more than that. It's build, it's test, and it's run. Those are three big phases that I see in the API lifecycle today that aren't really serviced by great products. I think there's point solutions and there's... kind of things at the end of the lifecycle and before the lifecycle.

But in the code, when it comes down to actually building, testing, and running the API, most teams are reinventing this wheel every day or every time they launch. And so for Speakeasy, we've done the build side. There's still plenty more there. We've at least made, I think, a pretty big inroad into helping you build and distribute your API. Next comes test.

But in the code, when it comes down to actually building, testing, and running the API, most teams are reinventing this wheel every day or every time they launch. And so for Speakeasy, we've done the build side. There's still plenty more there. We've at least made, I think, a pretty big inroad into helping you build and distribute your API. Next comes test.

But in the code, when it comes down to actually building, testing, and running the API, most teams are reinventing this wheel every day or every time they launch. And so for Speakeasy, we've done the build side. There's still plenty more there. We've at least made, I think, a pretty big inroad into helping you build and distribute your API. Next comes test.

So it's about how do you ensure as your API grows and scales, you can maintain great consistency, reliability, and empower your dev team to move faster. And then finally, there's run. Run is really exciting because I think APIs haven't seen that revolution towards fast iteration and edge development. the way UI has.

So it's about how do you ensure as your API grows and scales, you can maintain great consistency, reliability, and empower your dev team to move faster. And then finally, there's run. Run is really exciting because I think APIs haven't seen that revolution towards fast iteration and edge development. the way UI has.

So it's about how do you ensure as your API grows and scales, you can maintain great consistency, reliability, and empower your dev team to move faster. And then finally, there's run. Run is really exciting because I think APIs haven't seen that revolution towards fast iteration and edge development. the way UI has.

Like, teams like Vercel and Netlify have brought that, like, amazing get previews on every GitHub commit kind of experience. And that's changed UX development. APIs haven't had that. And so we're exploring with our customers what it means to, like, instantaneously have APIs deployed on the edge, have a backend for frontend on every GitHub commit.

Like, teams like Vercel and Netlify have brought that, like, amazing get previews on every GitHub commit kind of experience. And that's changed UX development. APIs haven't had that. And so we're exploring with our customers what it means to, like, instantaneously have APIs deployed on the edge, have a backend for frontend on every GitHub commit.

Like, teams like Vercel and Netlify have brought that, like, amazing get previews on every GitHub commit kind of experience. And that's changed UX development. APIs haven't had that. And so we're exploring with our customers what it means to, like, instantaneously have APIs deployed on the edge, have a backend for frontend on every GitHub commit.

I think there's something really exciting there in terms of helping our customers go all the way from an API spec to a deployed API back as quickly as possible and becoming this core infrastructure loop for our customers every day. I'm excited the way the team is shaped up. We're half based in San Francisco, half in London. A couple of remote folks, but those are two centers of gravity.

I think there's something really exciting there in terms of helping our customers go all the way from an API spec to a deployed API back as quickly as possible and becoming this core infrastructure loop for our customers every day. I'm excited the way the team is shaped up. We're half based in San Francisco, half in London. A couple of remote folks, but those are two centers of gravity.

I think there's something really exciting there in terms of helping our customers go all the way from an API spec to a deployed API back as quickly as possible and becoming this core infrastructure loop for our customers every day. I'm excited the way the team is shaped up. We're half based in San Francisco, half in London. A couple of remote folks, but those are two centers of gravity.

I feel super lucky to be working with these great talent pools in both locations. Core team members still here at the company. We're growing the team. So yeah, I think Speakeasy is interesting. It's a platform of products. It's not a single product. And so there's scaling challenges, but there's also a bunch of new product that needs to be built.

I feel super lucky to be working with these great talent pools in both locations. Core team members still here at the company. We're growing the team. So yeah, I think Speakeasy is interesting. It's a platform of products. It's not a single product. And so there's scaling challenges, but there's also a bunch of new product that needs to be built.

I feel super lucky to be working with these great talent pools in both locations. Core team members still here at the company. We're growing the team. So yeah, I think Speakeasy is interesting. It's a platform of products. It's not a single product. And so there's scaling challenges, but there's also a bunch of new product that needs to be built.

And so I think I'm really excited for us because it feels like we're just coming from phase zero to phase one, but there's still phase two, three, four on the road to being a big kind of foundational infrastructure product. So yeah, I think this is going to be an exciting rest of the year, but I think there's so much more to be built. There's so many more problems in the world of APIs to be solved.

And so I think I'm really excited for us because it feels like we're just coming from phase zero to phase one, but there's still phase two, three, four on the road to being a big kind of foundational infrastructure product. So yeah, I think this is going to be an exciting rest of the year, but I think there's so much more to be built. There's so many more problems in the world of APIs to be solved.

And so I think I'm really excited for us because it feels like we're just coming from phase zero to phase one, but there's still phase two, three, four on the road to being a big kind of foundational infrastructure product. So yeah, I think this is going to be an exciting rest of the year, but I think there's so much more to be built. There's so many more problems in the world of APIs to be solved.