Ryan Kidd

Yeah, I think like people aren't limited by compute at mass in general.

I think that the way we do it is pretty good and that we have a bunch of like, you know, kind of like we have our for our model API calls and all that, like we have specific organization accounts that we sign people up, you know, and then we kind of give them a budget and so on and top them up as necessary.

We do have our own mass cluster as well that we maintain online.

So our compute team handles that.

But typically people tend to use run pod and other types of like self-service things.

It depends on the kind of research.

There's some types of research that works well on our cluster, and there's some types of research where even with the benefit our compute team can provide in setting up the cluster and maintaining it, the experiments are so customized and they need to tinker so many things that we just give them a budget and let them use online providers.

It's just better that way.

We did have these other providers in the past, but that's their current setup.

And we're looking at putting together like a kind of customized cloud code kind of suite as well.

I don't think, not MCP, this, well...

That's kind of a boring distinction anyway.

Yeah, you're right.

There's a lot of data, and that's databases.

We could probably put together something really useful at some point, but we haven't thought about that.

I mean, our new research database is online, mattsprogram.org slash research.

You can see everything there.

We have a Google Scholar.

But that's just all the papers that got published.

You can also see our restaurant blog post under the Matts program tag.