Allow Private Components to Be Locked to a Account!

Roadmap Feature Requests
, ,
1

I’d like to request a feature that allows private custom components to be locked to a single app or account, preventing them from being shared with other apps or teams.

As a component developer, I sell custom components directly to clients because I can’t use the Adalo Marketplace. Stripe isn’t available in many South American countries, so publishing components on the Marketplace isn’t an option for us.

The current issue is that once I add a private component to a client’s app, there’s no protection against that component being shared or redistributed. Someone could purchase it once and then share it with other accounts, making it very difficult for developers to protect their work.

This feature would help developers safely sell private components while protecting their intellectual property.

Also, if anyone has found a workaround or another way to prevent private components from being shared, I’d really appreciate your advice.

Thanks!

2

@Dilon I can’t list on the marketplace because my LLC hasn’t been activated yet to use Stripe… it’s not used in South America, so I’ll have to sell them individually using USDT… but if I share them as a member, they can give them to others… how can I prevent the user I give the component to from using it on other accounts, like those purchased on the marketplace?