# Emoncms.org billing **URL:** \ **Category:** Emoncms.org\ **Created:** [16 April 2018 17:06 UTC](https://community.openenergymonitor.org/t/emoncms-org-billing/7187 "2018-04-16T17:06:53Z")\ **Posts on this page:** 1\ **Showing post:** 38
**Author:** ![TrystanLea](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/trystanlea/32/31_2.png) [@TrystanLea](https://community.openenergymonitor.org/u/TrystanLea)\ **Post date:** [27 April 2018 21:43 UTC](https://community.openenergymonitor.org/t/emoncms-org-billing/7187/38 "2018-04-27T21:43:48Z")
The introduction of billing on [emoncms.org](http://emoncms.org) brings with it some interesting questions about monitoring system design (or IOT in a wider sense) which I think it would be good to discuss openly. We don’t want to push people to use and pay for [emoncms.org](http://emoncms.org) where it’s not suitable, we only want people to use it if it is valuable. There are I think advantages and disadvantages to both remote and local data storage and visualisation and it’s likely a matter of choosing the right tool for the application, or a combination of both. Luckily there are many options with emoncms: emonpi/emonbase, diy local, self hosted remote, [emoncms.org](http://emoncms.org). I started a dedicated thread on this topic here: [Forum post: Emoncms local vs remote](https://community.openenergymonitor.org/t/emoncms-local-vs-remote/7268/2), thought I better link it in here so that it doesn’t get lost. --- _[View the full topic](https://community.openenergymonitor.org/t/emoncms-org-billing/7187)._