License — Fredoscale

Proponents of this license (often small dev tool startups or indie game engine creators) argue that it is the only sustainable model for modern open-core development.

The "Rent-Seeking" Prevention: Without the Fredoscale License, a large cloud provider can take a free, permissive license, repackage a library, and sell it for $10,000/month, paying nothing to the original author. Fredoscale License

Sustainable Maintenance: Heartbleed (OpenSSL) proved that volunteer maintenance fails. The Fredoscale License forces profitable users to become paying customers, generating a revenue stream for the maintainers. Proponents of this license (often small dev tool

Equity: It aligns with progressive taxation logic. Those who benefit most from the software (giant corporations) pay the most, while students and bootstrappers pay nothing. IN NO EVENT SHALL THE LICENSOR (FREDO6) BE

✅ One-time payment – No annual fee, unlike many modern SketchUp extensions moving to subscriptions.
✅ Works offline – Great for secure environments or poor internet.
✅ Bundle value – Pay once for ~8 major tools (RoundCorner alone is worth the price).
✅ No DRM spyware – No phone-home checks every launch.
✅ Generous trial – 30 days to fully evaluate, not feature-crippled.
✅ Perpetual – You keep the last version you paid for, even if you don’t renew (but there’s no renewal anyway).

IN NO EVENT SHALL THE LICENSOR (FREDO6) BE LIABLE FOR ANY INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

| Myth | Fact | |------|------| | "I can remove the copyright notice" | ❌ No – it must remain in all copies. | | "I can sue the author for bugs" | ❌ No – warranty disclaimer is explicit. | | "It's not an open-source license" | ✅ It is – OSI-approved via MIT equivalence. | | "I need to include the license in binary distributions" | Usually yes – the notice must be included, e.g., in a documentation file or about box. |

  • For binary distributions, include license and attribution within packaged documentation or an accessible NOTICE file.
  • Incompatible “copyleft” licenses that impose reciprocal source-disclosure obligations may be disallowed for relicensing of Fredoscale original files unless contributor approval is obtained.