Corey

I forgot about that.

Yeah, it doesn't have to be AWS or Azure and cost a lot to be a large project.

I mean, you could spin it up small very reasonably.

Before we get back to kind of the money talk earlier, there are a few things I would recommend you really want to watch out for in doing this.

Number one is I think you want to set some kind of a token limit within your app.

You want your tasks that an end user is able to do.

You don't want it to run away and pull out 2 million tokens and cost you $42 per user.

You want to make sure that what you've got is streamlined, it has enough to do the job well.

So you want to get an idea of what the token count of your thing is.

That's a thing we can get into a little deeper.

If it's something that interests you, let us know and we can talk about, you know, maybe doing a future episode on tokens, how they work and token counts and token count tools, the various things to help you with that part of this.

You also want to monitor its output regularly.

Go use it.

You know, presumably if you spin it up, you'll have access to some kind of a database that's probably saving most of what's running through it, where you can go through and look for anomalies, problems, make sure it's not recommending people go somewhere that, you know, is dangerous or inappropriate, maybe.

You know, you want to really watch out for that kind of stuff because, you know, I would assume directly you're going to be liable for this app if you put it out into the world.

So treat it as such.

Third, and not necessarily most importantly, but one you really want to watch, is cost controls.

Like you can, with most of these tools, set maximum amounts of money for how much they can ding your card for, how much is running through, and have stopgaps in there to notify you and let you know that, you know, hey, this is getting out of hand.

Because if you don't,

It can just bill your credit card according to how many people are using it.