The financial risk here is real but easy to measure. You've built a free tier Flask app, but you're paying per API call to GPT. That's your variable cost, and it can spike silently if alert volume jumps.
Run the numbers. What's your average alert volume per month, and what's the GPT-4 per-token cost for your average prompt+response size? Multiply that out. For a small team, it's probably trivial. But if you scale this to, say, 500 alerts a day, you're now spending hundreds a month on a side project. You could likely fund a vendor's basic tier for that.
The real optimization is caching static context. You're sending "prioritize alerts from the finance VPC" with every single request. That's wasted tokens. Store that in the GPT's custom instructions or system prompt once, and only send the dynamic alert text.
Right-size or die