MicroPython Tools Freemium Release

[lukaskremla]

TL;DR: All features of 0.6.3 will remain fully free, open source and actively maintained. You will simply see paid professional features available in the plugin, which can be unlocked with a monthly/annual subscription - absolutely nothing else changes for you.

First of all, thank you all for using this plugin, submitting issues, starting discussions, writing reviews or starring this repository. When I started this project I had no idea how much it might grow, and how many people will end up using it.

I'm glad this plugin is your tool of choice for working with MicroPython - and I'm looking forward to seeing how this tool will evolve with the community's help.

I hope that the mention of monetization of this announcement's title didn't scare you - there's nothing to worry about. All of the features that are currently available in 0.6.3 will remain fully free, open source and actively maintained. They will be managed the same way they've been managed up until now.

Developing features for this plugin, fixing bugs, ensuring it all works - it takes a lot of time and effort. As well as that, I want to start working on complex features for professional/commercial use of MicroPython. This includes features such as:

• MicroPython Port/Firmware flashing and development
• Debugging
• Mpy-cross integration
• custom-network based communication
• upload speed optimizations
• smoother IDE integration in the form of background tasks that don't block the IDE

Development of these professional features will no doubt be very demanding. For this reason I decided to move to a freemium monetization model. This allows this project to keep the best of both worlds - everyone can continue using this plugin exactly the way they're used to - fully free, open source, actively maintained and improved. While, at the same time, offering paid professional features and tools to aid commercial development involving MicroPython.

The first pro features will become available in the 0.7.0 version - its release date is set for 17.10.2025. The following features will become available (+ a sneak peak):

• Mpy-cross run configurations
• Upload compression (Saves time on very large uploads)
• Background Uploads/Downloads (Instead of running in a model progress dialog, you will see a progress reporter near the bottom right corner of the IDE)

Sneak peak of the mpy-cross run configuration

The Pro subscription can be purchased through the plugin's marketplace page already - you'll also be able to buy it through the IDE once 0.7.0 is out, you'll also be able to start a 30-day trial period through the IDE. The details of the pricing can be seen in the spoilers below:

For individual use

For organizations

NOTE: The prices are subject to change when more complex features are released.

Lastly everyone who is actively sponsoring the project right now, or who did so in the past, is eligible for lifetime free access to the premium features (the JetBrains marketplace currently doesn't offer any solution for combining lifetime licenses and subscriptions, you will be provided with a 100% off coupon code yearly instead).

Please get in touch with me through the contact email in my GitHub profile to claim your subscription. The sponsors who have a public contact email have received their first code already.

[lukaskremla]

NOTE: This doesn't mean no new free features will be added - some of the pro features will work on a half free/half paid basis.

For example the current plan with MicroPython firmware flashing is to allow flashing the latest MicroPython release onto the supported board platforms and then offer more custom port/firmware related features in pro.

Also, some new features and improvements will of course come to the free version as well.

[Witawat]

pro version have option flash firmware ?
have option protect read code ?

[lukaskremla]

THe option to flash firmware will be implemented next, as matter of fact, I'm actually working on it right now.

The free version will provide a UI to flash esp, rp2, stm and samd devices similarly to Thonny, more complex flash run configurations will then be made available through Pro.

Could you please clarify what you mean by "protect read code"?

[Witawat]

I mean how to protect the code from being copied or read for editing or copying.

i found it can make. mpy boot.py or main.py ?

[lukaskremla]

Neither boot.py nor main.py can be compiled, because MicroPython expects them with the .py extension, it would ignore them if they were main.mpy or boot.mpy. These files should be minimal anyway, and most of your logic should be in other files, which can be compiled to .mpy.

Yes, compiling to .mpy bytecode will make your code harder to deobfuscate/reverse engineer, as they will no longer be in a plain-text human readable format. Of course, note that no protection is 100%, but compiling to .mpy bytecode with emitter of "Bytecode" is a cheap way with minimal tradeoffs to make your code more secure, faster and also take up less space on flash.

[Witawat]

Could you please explain how to use it?

Can you choose anything? Or are there any principles for choosing?

[lukaskremla]

You can find more info in the docs.

Basically, unless you know the implications of Native/Viper and have a reason to use either, select Emitter of type Bytecode.

Any MicroPython code can be compiled with emitter of type Bytecode, it is also widely compatible as it isn't compiled for a sepcific architecture.

If you'd be using an emitter that requires an Architecture be set, you can just click the auto-detect option while your board is connected to the plugin. This auto-detect option also sets the Bytecode version automatically for you.