Introduction to ESP RainMaker
ESP RainMaker is an end to end IoT solution, with the cloud backend forming its core. The backend is built using AWS serverless architecture, which offers unparalleled flexibility and scalability in terms of computing, data storage and transmission capacity. Serverless does not mean that there is no server. It hides the management of the hardware and software infrastructure and provides usable services for the application. This makes ESP RainMaker very easy to maintain and manage.
If you're new to ESP RainMaker, we highly recommend starting with this page, followed by reading the contents in Components of ESP RainMaker, Concepts and Features. Once you're familiar with these, you can visit our Evaluation Hub to try ESP RainMaker using the public instance of RainMaker for developers and hobbyists, or follow our deployment guide to set up your own private RainMaker for commercial clients.
What is public RainMaker and private RainMaker?
Public RainMaker
The public instance of the RainMaker cloud is free to use for a small number of nodes. This cloud and the accompanying open source firmware and phone apps is ideal for proof of concept projects and technical evaluation.
Private RainMaker
Once evaluation is done on the public RainMaker, customers can opt for a private RainMaker deployment for commercial usage. The same firmware built and tested with public RainMaker can be seamlessly integrated with the private deployment. This makes it very easy to quickly create working products without even having to reach out to our sales team or follow the deployment process. The deployment cycle of ESP RainMaker is illustrated in the diagram below:
To learn about the technical difference between public RainMaker and private RainMaker, click here
What is the difference between RainMaker in China and RainMaker Global?
ESP RainMaker is available in both China and the global region regardless if you are using public RainMaker for evaluation or deploying RainMaker privately for commercial usage, with each deployment designed to meet the specific regulatory, infrastructural, and user requirements of its respective region. This regional distinction will be clearly indicated throughout the documentation hub.