Spike: purchase and manage self-serve upgrades and add-ons via the CLI
Investigate what we'd need to let users purchase and manage self-serve upgrades and add-ons from the trigger.dev CLI, without going to the dashboard. Prompted by a feedback request to buy and manage extra preview branches from the CLI; some users are no longer using the dashboard much.
Questions to answer
- How the current dashboard billing / add-on purchase flow works, and what of it can be reused (ideally alongside the new billing work).
- Which API endpoints are needed (list plans/add-ons, current usage and limits, purchase/change/cancel), and how they're authenticated.
- CLI auth and permissions: who in an org is allowed to purchase, and how the CLI enforces it.
- Payment confirmation UX in a terminal: hand off to a browser checkout link vs. charging the card on file with an explicit confirm step; handling of failed payments and missing payment methods.
- Which add-ons/upgrades to support first (extra preview branches seems the obvious first one), and whether plan upgrades belong in scope.
- Rough shape of the commands (e.g.
trigger.dev billing/addons), plus non-interactive/CI usage.
Output: a short write-up with a recommended approach, required backend changes, and a proposed first slice.
Links
No comments yet
Be the first to share your thoughts.