You can get it off Plugin Boutique again now.
This, and the limited licensing issue, is why I requested a refund from plugin boutique. I have a degree in music, graduated from a conservatory post-bac, and taught music at a university for several years. I know my theory, and I’ve always thought that Scaler was a great product for students, especially (I own scaler and scaler 2). I can no longer support this company. I’m a customer, not a criminal (if I were pirating their software I wouldn’t have ANY of these limitations). I supported your product, learned to use it, recommended it to students, and in return am disrespected, and forced to waste my time, and given software that isn’t as it was advertised ,gimped and hobbled, and laden with anti-consumer DRM. No thanks, I will use the refund to support developers who respect their customer base.
-LeRoy Wood III (LeRoy3rd)
Registered and went to download and got this nice message from drop box "Too many requests
Sorry, this link has been automatically turned off for now. Learn more about traffic limits."
Well that’s convenient. 
Can’t download, dropbox link is deactivated 
Same here - dropbox comes up with a message -
Too many requests
Sorry, this link has been automatically turned off for now.
Scaler 3, Can’t download it. Issues with the Dropbox link
Too many requests
Sorry, this link has been automatically turned off for now. Learn more about traffic limits.
agree, download link is a DropBox link that has too many downloads. lol
I want to sincerely apologize for the frustration caused to those who tried to download Scaler 3 and were met with the ‘Too many requests. Sorry, this link has been automatically turned off for now’ message. This was due to a bandwidth limit on Dropbox.
Honestly, while focusing on scaling up servers, activations, and website bandwidth, I overlooked the actual download link itself. Unprofessional? Maybe. More than anything, it was an oversight on my part.
That said, I trust everyone now has their copy of Scaler 3 and is enjoying it. We’ve moved to an AWS storage solution, which should prevent this from happening again. Thanks for your patience and support—I’ll be closing this post now.
Davide