So for build UI, it's not like generic. It's like, okay, I need to go check is this you does this user have a subscription? Are they on a team that has a subscription? Right. Okay. They're what video do they want? Oh, I know how to best get that video from the CMS. This is how the day this is how we're organizing the day because like if you think about the CMSs or like document stores, they're not they're not they don't know that we're putting videos in there. They don't know that like we might have like pointers over the mocks or Vimeo. Right. And something that our own little middle layer that can kind of glue all this together. I think is a nice thing. It's also just like one entry point. Yeah. So we can you know swap stuff in another there. Yeah.

It's nice to be able to look under API and see our stripe webbook and you know eventually video processing or whatever it is you

know, it is funny that if you aren't using an API route, this somehow gets like way more scary and more expensive from not like in dollars, but in terms of complexity states just just you now have another app you're running that you're deploying. If you're not using a

P and you're also not talking directly to the service. You're saying if you had another app. Yeah. Yeah. Yeah. Oh, yeah.

So like it's very easy to say, oh, just set up a proxy. And then six months later find yourself in a world of like you have eight different microservices. Yeah. Which which is something we want to avoid because we just don't

we just need that. So yeah, so there are some way to

go for sure.