Zach Rosen

You know, IT teams typically have the skill sets to manage servers and SLAs around them.

But when you get in the world of website DevOps, you have CDNs, caching, APMs.

You know, the whole LAMP stack, and then you have dev environments, test environments, deployment systems, caching systems.

It's a very long kind of spew of technologies that you have to master.

And so what we would see the pattern would be basically that the website developers themselves would have to do the DevOps because the IT teams just didn't have that background.

which wasn't any fun for them.

So it'd be like, hey, Jen, the only one we trust to deploy changes, guess what your new job is?

You're now gonna deploy everyone's changes, which is pretty miserable for Jen.

So eventually the light bulb went off.

We did that project about a half a dozen times.

Uh, yes.

A little before that, we need to productize this and turn it into a SaaS service.

And so we incubated it inside the web agency for a little bit and then took them there.

Okay, based where?

Uh, many of us are in San Francisco, uh, but we, we have to be global.

So we have, you know, team, we have a couple of offices around the world and we have, uh, folks in every, you know, essentially every comment.

Yeah.

We're based in San Francisco.

Okay.

It's all public.