The perspective of PENVM is the application. It is meant to tie processes of an application (just one) together to produce results. So it is different from wir

The perspective of PENVM is the application. It is meant to tie processes of an application (just one) together to produce results. So it is different from wireguard mesh which is for setting up VPNs. It is different from docker compose because it is works within the application. One area that does seem similar is that resources are booted on behalf of the application. However, there is no need for docker or containers. It looks like netmaker is about actual networking, a-la VPNs and the like. So, it is different from PENVM. From a Python example, suppose an application has a function "calculate". With PENVM, an alternative function named "calculate" could be provided (in its place, taking the same arguments) which runs across a network of machines (as specified in a .penvm configuration file). This would be transparent to the application itself. I think the pvx tool (https://github.com/penvm/penvm-pvx https://github.com/penvm/penvm-pvx) actually demonstrates how PENVM can be used. The Jupyter demos show this as well (https://github.com/penvm/penvm-jupyter-demos https://github.com/penvm/penvm-jupyter-demos) with videos (https://penvm.dev/docs/examples/jupyter/jupyter-demos-videos/ https://penvm.dev/docs/examples/jupyter/jupyter-demos-videos...). Let me know if those examples clarify things.