Budget controls and alerts system implementation #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

bonus414 opened this issue Apr 10, 2025 · 0 comments

Labels

bonus414 commented Apr 10, 2025 •

edited

Loading

Budget controls would allow customers to:

Set daily/hourly token usage limits
Configure different thresholds for prod vs dev environments
Set company-wide spending limits for end users

For alerts:

Light LLM has webhook capabilities for budget tracking per key
Alerts can't happen directly in Drupal, but:
- Dashboard can show usage (e.g. "95% of budget used")
- amazee.ai could send email alerts
- Need to determine how to handle links/CTAs since amazee.ai doesn't know Drupal site URLs
Would need to build feature to handle webhook data from Light LLM to amazee.ai

Current limitation: Budget features are focused on trial usage limits, need to expand for customer usage control.

We could have

Have Light LLM send webhooks to amazee.ai
amazee.ai would then handle the webhook data

bonus414 added the billing-system label

bonus414 moved this to Icebox in amazee + Afrolabs

bonus414 added this to amazee + Afrolabs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment