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

Customer Billing (MEGH-5461) #308

Closed
3 tasks done
jetpax opened this issue Apr 25, 2024 · 1 comment
Closed
3 tasks done

Customer Billing (MEGH-5461) #308

jetpax opened this issue Apr 25, 2024 · 1 comment

Comments

@jetpax
Copy link

jetpax commented Apr 25, 2024

Answers checklist.

  • I have read the Rainmaker documentation and the issue is not addressed there.
  • I have updated my IDF branch (release/vX.Y) to the latest version and checked that the issue is present there. This is not applicable if you are using Rainmaker with Arduino.
  • I have searched the Rainmaker forum and issue tracker for a similar issue and not found a similar issue.

General issue report

Lets say I use the Rainmaker service for a product and pay the AWS & ESP charges, and the product has 10,000 individual users.

What is the recommended mechanism for passing this through to my users?

ie how does customer billing work?

@github-actions github-actions bot changed the title Customer Billing Customer Billing (MEGH-5461) Apr 25, 2024
@shahpiyushv
Copy link
Collaborator

ESP RainMaker private deployments do not explicitly have any end customer billing as it could be very much use case specific. Some customers may want to have a flat monthly billing, some may chose billing linked to device count, others may link to the messaging count. You can pull out such info from your private RainMaker deployment and charge the end users accordingly.

Since this is linked to business aspect, please also reach out to our sales team at [email protected] or the RainMaker admin at [email protected]

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

No branches or pull requests

2 participants