Where is the source code?


I’m trying to evaluate Zerynth but can’t for the life of me find all of the actual source code.

Where is the link to the source code for the OS, the bytecode compiler, the VM, board specific support, etc.?  I looked at https://github.com/zerynth?tab=repositories but it just seems to be a bunch of metapackages without links to anything.

The only download on the website seems to be for some kind of IDE environment which is not really my style, I much prefer to build from the command line using “make” and upload to the target using JTAG/SPI programmers :slight_smile:

Is there any way to atleast view all of the source code to see if there is anything worth reusing without downloading a huge IDE?


I second the request, the website claims the sources are GPL3 but, as the OP says, they are nowhere to be found.

At least the ChibiOS derivative work should be hosted somewhere, right?


Hello everyone, 

sorry for the delay.

In order to guarantee a reliable, maintainable and scalable architecture of the Zerynth suite, the Zerynth Virtual Machine license will soon switch to a closed source policy with distribution of binaries packages only and custom VM compilation as an online service. The old VM sources are available here, in the new Zerynth Github repo.

The Zerynth Github repo is also going to be reorganized soon. The sources of Zerynth Studio and of the included toolchain will be officially published with a MIT license; at the moment they are available under the installation folder of Zerynth. 

The Zerynth team is working hard in expanding the number of supported boards (spoiler: non-ARM architectures coming this month). In the next days we will launch a survey asking  the community which boards you’d love to program with Zerynth.

In the meantime, if you would like to receive special modules, or to have Zerynth ported on a specific board, as well as to collaborate with us please write at info@zerynth.com


Giacomo, CTO Zerynth


“In order to guarantee a reliable, maintainable and scalable architecture of the Zerynth suite” doesn’t really explain the rationale, though, does it? I’d like to know why Zerynth believes that open-sourcing the VM would reduce reliability, maintainability and scalability. Large projects like the full Python interpreter have done very well at these issues.

Hello @"Steve Holden" 

thank you for your question, we are happy to dialogue with our community on this topic. With that statement we did not mean that open source projects are not reliable, maintainable and scalable. There are hundreds of amazing and fully stable open-source projects out there.

As many other aspects on this planet, the (not light-hearted) decision to close the Zerynth Virtual Machine source needs to be contextualized.

The context of the Zerynth Project is the one of a startup that, after a 22k$ crowdfunding on Kickstarter, was bootstrapped without external support or investments. The goal was clear: proving the value of the Zerynth project by constantly delivering value to our users, enabling the development of commercially-viable IoT projects with added functionalities and lower time-to-market, with a pro-level toolkit. For sustaining such goal, a business model is needed, no other way to survive in this World :smile: 

A successful open source project can be sustained by an entity like a foundation managed to gather enough direct or indirect revenues to fund the core developers, not the easiest path for a startup today, congrats to the ones that succeed on that.
Other opensource projects get indirect revenues by selling hardware coupled to the software platform: not applicable for us, we are a hardware-agnostic software project, no compromises :smile: 
Consultancy? Good as short term business opportunity, but Zerynth has been conceived as a disruptive enabling technology with bigger ambitions. Zerynth is the "Android of the embedded world", and wants to enable more and more developers creating the desired IoT solution with their own skills, rather than having them listening to an "expert" providing suggestions on how to do things.

With a clear vision in mind, a useful thing to do has been to understand the environment where the Zerynth project lives:

- Zerynth's main target are professional (or makers aiming to move further from amateurs) and industrial developers: a stable core code and a team responsible for it, appear to be more important than code openness. At the same time, the freedom for anyone to develop libraries and drivers (all opensource) guarantees the necessary flexibility to develop new products in less time and with an abundance of Python programmers able to do it.

- The closed Virtual Machine also enables an innovative business model that fits with the embedded market mindset. From the point of view of the project manager, a Zerynth VM is just another element of the bill of materials for the specific project. A Zerynth VM has no recurring license fees and a one-time price known before the user begins the project, exactly like any other hardware piece.

Last consideration, many well known products in the embedded field are not open source. Many others became open source after being closed for quite some time. One of them is Arm® Mbed™ (link to https://developer.mbed.org/blog/entry/mbed-SDK-is-now-Open-Source/). If a company like Arm® took more than a couple of years of library binaries and closed source to stabilize their code on all the supported platform, probably this reveals a lot about the complexity of projects with such scope and with the ambition of being used in reliable and real-world products. We'd be more than happy to consider such scenario in the future. For the moment, we work night and day to provide the best IoT development tools in the hands of our users. Thank you very much for being one of them :smile: 

Gabriele & Team