cocalc
cocalc copied to clipboard
Consider renaming spending limit to budget
Or something else - some users confuse it with actual spending.
I think "monthly budget" would be good. We got very positive feedback about using "budget" instead today in a customer meeting.
I would also change the order in the list of limits - put compute servers on the very top, network right under, then upgrades, then all AI models. For AI models I personally would prefer a single limit for all of them. In the current state compute servers are kind of lost, while this is really the most important limit.
For AI models I personally would prefer a single limit for all of them.
This is not trivial to implement, unfortunately, since the pricing is per model, and the tracking of spending is per model. Also this "spending limit" has a breakdown of how much you've spent on each model so far this month (and also the price for each model), and if the limits are all one, that granularity all disappears. I.e., this is maybe harder than it looks to implement.