EOS ($EOS) dapps can be costly for the teams deploying them. In order to onboard users to an EOS dapp, developers generally have to make sure they've secured sufficient amounts of three separate costly resources: RAM, which amounts to state storage on the blockchain; CPU, which measures average consumption of computing resources in microseconds; and network bandwidth, or NET, which measures average consumption in bytes. This proves problematic for users as well, who may find that costs are shifted onto them.