Skip to content

feat: credit-based billing with monthly usage caps - #101

Open
addidotlol wants to merge 7 commits into
mainfrom
addison/credit-billing
Open

feat: credit-based billing with monthly usage caps#101
addidotlol wants to merge 7 commits into
mainfrom
addison/credit-billing

Conversation

@addidotlol

@addidotlol addidotlol commented Aug 14, 2026

Copy link
Copy Markdown
Member

Review in cubic

# Conflicts:
#	apps/dashboard/drizzle/meta/0029_snapshot.json
#	apps/dashboard/drizzle/meta/_journal.json
- purchaseProjectCredits passed currentQuantity + credits to billing.update, double-counting credits the customer already had; now passes the purchased amount directly
- add getProjectInvoices using the Autumn customer invoices expand
- include invoices in the billing overview response
- render invoice list with date, status, amount, and hosted invoice link
- Prevent reversing usage outside the current billing period
- Calculate monthly billing cycles using calendar months
@addidotlol
addidotlol marked this pull request as ready for review September 1, 2026 08:21
@TheHeroBrine422

Copy link
Copy Markdown
Contributor

There are still two sources of truth for billing. There is the rate/cap data that is in the vm_types table and the pricing on the autumn credit system. That is data that can get desynced and seems like a pain for maintenance.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants