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

Why not just completely open source ESP Rainmaker? (MEGH-2878) #96

Open
NemesisXB opened this issue Oct 5, 2021 · 13 comments
Open

Why not just completely open source ESP Rainmaker? (MEGH-2878) #96

NemesisXB opened this issue Oct 5, 2021 · 13 comments

Comments

@NemesisXB
Copy link

Why don't you just completely open source ESP Rainmaker, including the server side code? Espressif is after all a silicon vendor. The pricing is just too much for small to medium projects. Also, I have open issues from almost 18 months ago that require server side updates, which has not been done as only espressif can make those changes. If it was actually open source it might have been done by someone else. You can put a clause in the license or create a new license that states that it may only be used with espressif chips.

@github-actions github-actions bot changed the title Why not just completely open source ESP Rainmaker? Why not just completely open source ESP Rainmaker? (MEGH-2878) Oct 5, 2021
@halfn0rmal
Copy link

I second this. You would be providing a huge incentive to design any new iot products around the esp32.

@Xarkle1
Copy link

Xarkle1 commented Jun 22, 2022

I agree - open sourcing Rainmaker would be great. We are developing IOT using ESP32/S2/S3/C3 and that would be super helpful and great for Espressif.

@felixcollins
Copy link

At the very least there should be some public information about expected costs of using it. One gets the impression it will be cheap or free for small commercial use. Now I'm worried that I'm wasting my time investigating it!

@halfn0rmal
Copy link

I have enquired about pricing and it is prohibitive for a small company, minimum 5000usd per year for usage plus 5000usd upfront for the first year. If your are a new venture and you are not sure whether to use rain maker then I would say you are better to invest that 10,000usd and just use the aws examples with amplify, iot core etc and build your own infrastructure that you can own going forward. For a larger company adding cloud to an existing product then this may make sense for you.
To save someone the time of enquiring the costs are below:

  1. License (Espressif pays AWS bill) - our recommended model
    In this model, if the amount of communication from the device is known, then Espressif can provide an option of one-time per device license fee and then Espressif pays the AWS bill directly. Please note that there is not much customisability for the cloud backend in this case and you get standard RainMaker deployment. If your device sends data to cloud 5 times a day, indicative license pricing is USD 0.40 per device.

  2. Subscription (You pay your AWS bill)
    In this model, you pay AWS bill directly and pay subscription fee to Espressif towards using ESP RainMaker. Annual recurring subscription fee is 0.10 USD per year per device (minimum of USD 5000 per year). You can also customise the RainMaker backend to add your own code (e.g. in this case to process the data).

Please note that there is one-time fee of USD 5000 that is applicable for both the models. RainMaker will be deployed in your own AWS account and you’ll get to choose which region of AWS to choose.

@felixcollins
Copy link

Okay! Thanks @halfn0rmal. I guess that kills that idea then. I posted on the forum asking about licensing and limitations of operating on the free platform.

@NemesisXB
Copy link
Author

Another thing to note is that the pricing changed quite a bit since I enquired about it. My quote was that when deploying on your own AWS account, the upfront cost was $10k but no yearly subscription. I just can't see this working. Bigger companies that can afford this probably has the resources to implement their own, and for smaller companies that don't have the resources, these prices are exorbitant. It also completely takes startups and entrepreneurs out of the picture.

@halfn0rmal
Copy link

I would have thought it would be in espressifs interest to make it no upfront costs to onboard new customers to their hardware platform. It would be a good motivation to use their hardware.

For me I think it isn't worth it. There is a bit of work in rolling your own but long term it would pay off.

@felixcollins
Copy link

I agree with all of that. We actually have some of the cloud infrastructure already set up for ota, telemetry etc using free tier of firebase. The easy and secure provisioning is a major draw. At the moment we use the wifi local access point and a web page. A bit old school and complex for a lot of our customers.

@ameyinamdar
Copy link

@felixcollins you can use the Unified provisioning component (supports both SoftAP and BLE transports) with open-source phone apps. Please check out https://github.com/espressif/esp-idf/tree/master/examples/provisioning

@chaudhariatul
Copy link

Is there a table which shows list of boards that support SoftAP, BLE or both?

@shahpiyushv
Copy link
Collaborator

@chaudhariatul , basically all chips that support BLE can support both SoftAP as well as BLE provisioning viz. esp32, esp32c3, esp32s3, esp32c2. However, only one of these can be kept enabled at a time (using menuconfig options)

esp32s2 does not have BLE and so it can support only SoftAP provisioning.

@Bsm-B
Copy link

Bsm-B commented Nov 22, 2023

this topic is very interesting, but i think is best solution try to change endpoint to a private MQTT broker ,OTA via private server and Give up some features Of course if he doesn't disagree with License of opensource rainmaker.

I think is the best way , i dont know if someone try to do this? share with us

@dzungpv
Copy link

dzungpv commented Feb 24, 2024

I think Espressif, if could not complete open the code, they can partly open the code (Community version), like there are some limitation set of advance feature and then charge for advance feature with fully version (Professional version) like many project. So developer can fix the bug and improve the platform.

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

8 participants