Skip to content
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.

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

feat(billing): Usage based billing #2632

Open
1 task done
betimshahini opened this issue Aug 22, 2023 · 1 comment
Open
1 task done

feat(billing): Usage based billing #2632

betimshahini opened this issue Aug 22, 2023 · 1 comment
Assignees
Labels
to-be-defined Indicates issue that needs design

Comments

@betimshahini
Copy link
Contributor

betimshahini commented Aug 22, 2023

Why

To support future use cases and services that inherently can scale proportionally to users' needs (eg. object storage), we need to support usage based billing.

What

  1. Need patterns for reporting of service usage by some consumption unit (eg. # of reads, GBs written, etc) for inclusion in a service page. In addition, need patterns for reporting the cost associated to that usage.
  2. Need patterns to purchase a pack of consumption units (eg. 1 million read operations) and for those to be applied to both the service usage level as well as the billing scenarios in item above.

How

  • Conceptual UX design or even a UX pattern for showing/managing usage based billing. We can use object storage as the illustrative example for this.
@betimshahini betimshahini added enhancement Indicates new feature requests to-be-defined Indicates issue that needs design labels Aug 22, 2023
@betimshahini betimshahini removed the enhancement Indicates new feature requests label Aug 22, 2023
@picassobanana
Copy link

picassobanana commented Nov 14, 2023

Service Plan & Billing Page

Figma link

Preview
Screenshot 2023-11-14 at 16 59 20

Service Page (Storage)

Figma Link

Preview
Screenshot 2023-11-14 at 17 03 21

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
to-be-defined Indicates issue that needs design
Projects
None yet
Development

No branches or pull requests

2 participants