A few pre-requisites:
A Craft purchase/edition is tied to the
craft/config/license.key file that is in place at the time the purchase is made and wherever that file goes, the purchase/edition will follow.
craft/config/license.key file can only be tied to one "public" domain at a time.
Craft license validation doesn't run on "non-public" domains and you're able to trial the different editions of Craft for as long as you want on non-public domains.
Craft will treat
app-client.local.mycompany.com.br as a "non-public" domain, because it has one of the keywords we're looking for in its own segment in the subdomain. You can see a list of those keywords here in number 4 of the previous link.
The rest of those domains Craft treats as "public" because they don't match any of the rules in that link, so license validation will run on them.
You don't say exactly what you're issue is, but if you purchased Craft on the development domain and you're using that same
license.key file on the three other public domains, you're probably getting a warning in the Control Panel saying that license is already in use on another domain.
Since they are all for the same "site", you can either tell everyone that has access to the Control Panel to ignore the message and to not transfer the license away from the production domain, or you can change your
hom domains so Craft treats them as "non-public" and license validation won't run.
More related reading: https://craftcms.com/support/license-key-info