I do understand what you are asking for though. There used to be an older project called erlang-on-xen: https://github.com/cloudozer/ling .
It'd be great to see this idea revisited although you'll need to create some sort of new handling/framework.
Lots of people have written alternatives to BEAM. The only problem they run into is that BEAM is very good, and would be tough to beat. I was an admirer of Erlang on Xen: https://github.com/cloudozer/ling
I also remember clicking around Ling (Erlang on Xen, sadly no longer active [1]) where the whole VM could boot up, service the request, and shut down in less time than it takes a cloud to start spinning up an instance :)
There also used to be an implementation of the BEAM VM directly on Xen: https://github.com/cloudozer/ling / https://web.archive.org/web/20190507184436/https://erlangonx...
There have been efforts to provide the capability of running a program without an OS before, but any such effort is going to need to provide the system calls and standard libraries used by the program, and the infrastructure to support it (device drivers, management, etc.). That that point it becomes a mini-OS.
An example is Erlang on Xen. Xen is more often run with a guest OS running inside it, and then the program runs within that guest os. The http://erlangonxen.org/ folks made Ling (https://github.com/cloudozer/ling), software that enables an Erlang BEAM VM to be run directly on Xen, and thereby run a single Erlang program on Ling.
https://github.com/cloudozer/ling
An impressively done book on BEAM instruction sets:
https://github.com/cloudozer/ling/tree/master/doc
There is even a handy dandy online instruction set completion search:
One of the contributors recently wrote: maximk commented on 25 May "All recent updates to the code were customer-driven. New users mean new updates. The likely application area for this is NFV, modular software for telecoms. No definite plans"
So there is:
code: https://github.com/cloudozer/ling
Basicly instead of:
hardware|kernel|os|erlangvm|yourcode
it is now:
hardware|xen|ling|yourcode
Not sure how functional it is now. I haven't followed the project in the last year much. But I see some development on github lately.