Velxio 2.0 is live.<p>A free, open-source emulator for 19 embedded boards: Arduino, ESP32, Raspberry Pi, RISC-V , running real compiled code in your browser.<p>The best part: it's fully local.<p>No cloud dependency. No student accounts. No data leaving your network. Self-hostable with a single Docker container.<p>Universities and bootcamps can deploy it on their own servers and give every student access to a complete embedded development environment, for free.<p>I've been working on this for over a year, and just shipped v2.0 with ESP32 emulation (via QEMU), a custom RISC-V core, and Raspberry Pi 3 support that runs real Python
just curious - if it runs from a docker container, what is the advantage of running the browser as opposed to just ssh'ing in ?
The main advantage is accessibility and ease of use: with the browser, no setup is required on the user’s side, no toolchains need to be installed, and there’s no need to be familiar with SSH or terminal workflows<p>It also provides a more visual and interactive environment (editor, peripherals, simulation controls), which is especially useful for teaching and for beginners.<p>The Docker image is there so you can easily install it on your own machine if you want to run it locally or work on development
Is it easy to feed an elf or bin and run that (esp32c3)? I see compilation available, but I'm playing with asm and have my toolchain figured out already and would just like to emulate the firmware.
Another +1 for this one as this is what turns this tool from a toy environment with basic sketches into something that's actually useful for larger projects with a full toolchain, libraries, and so forth.
That’s exactly the direction I’m aiming for<p>A lot of simulators stop at simple sketches, but the goal with Velxio is to support more realistic workflows , multiple boards interacting, real toolchains, and more complex setups<p>Still early, but definitely moving in that direction
[dead]
[dead]
[dead]
This is fantastic. I am doing my first-ever consumer electronics product and this would save a lot of soldering time
Hey HN, I posted Velxio here a while back and got great feedback. Since then I've shipped a major update<p>What's new in v2:<p>- 19 boards across 5 CPU architectures (AVR8, Xtensa, RISC-V, ARM Cortex-M0+, ARM Cortex-A53)
- ESP32 emulation via QEMU (lcgamboa fork) — real flash images, ROM function emulation, GPIO/ADC/timers
- ESP32-C3 and CH32V003 run on a custom RISC-V core written in TypeScript, entirely in the browser
- Raspberry Pi 3B via QEMU raspi3b — boots real Pi OS, runs Python
- Realistic sensor simulation: DHT22 (40-bit protocol timing), HC-SR04 (trigger/echo), WS2812B NeoPixel (GRB decoding)
- 48+ electronic components from wokwi-elements<p>Architecture:<p>- AVR, RP2040, and RISC-V emulation runs client-side (avr8js, rp2040js, custom TS core)
- ESP32 Xtensa and Pi 3 run on backend QEMU
- Compilation via real arduino-cli
- React + Vite frontend, FastAPI backend
- Self-hostable via Docker, no account needed<p>Source: <a href="https://github.com/davidmonterocrespo24/velxio" rel="nofollow">https://github.com/davidmonterocrespo24/velxio</a> (AGPLv3)<p>Happy to discuss the emulation architecture — particularly the trade-offs between in-browser vs. backend QEMU emulation
When I try to visit velxio.dev, a CrowdSec page shows up and says I am not allowed to view it. I am a pretty normal android user on firefox mobile, so that is surprising.<p>I look forward to trying this out though, great project!
Quick update: this should be fixed now. It was an overly aggressive CrowdSec rule blocking some legitimate traffic.<p>If anyone still has issues accessing velxio.dev, let me know
Nice one! I can access it now.<p>Really awesome project, it runs well on my old android phone, the fact that I can use a tool like this on my phone is pretty wild, you have done well with the UI in that regard. The oscilloscope is a really nice feature too.
Oh, thanks for reporting this.that definitely shouldn’t happen.
It’s likely an overly aggressive CrowdSec rule blocking some legitimate traffic. I’ll look into it and adjust the configuration
Hi, adding WS2812B LED strips of arbitrary length would be awesome! Scrolling the canvas is sometimes problematic. Otherwise very interesting.
Quick update: traffic is still coming in waves, had to scale up compilation workers to keep up with demand<p>Things are more stable now, but still tuning performance under load<p>If anyone finds it useful, the source is here:
<a href="https://github.com/davidmonterocrespo24/velxio" rel="nofollow">https://github.com/davidmonterocrespo24/velxio</a><p>Always happy to get feedback or contributions.
I like this Idea but I don't want to use this.
I know what kind of prompt U using to create this one:
"Create something like Wokwi and make it local"
The container instructions has `-d` in it, but note that after booting the container it downloads another, I don't know, 300+mb more (its still downloading as I write), so if you can't connect that's why.<p>Might be better to not include `-d` in the instructions?
Good catch!!! thanks for pointing that out<p>The container pulls additional assets on first run (mainly emulation dependencies), which is why there's extra downloading even with -d.<p>You're right that it can be confusing. I'll update the instructions to make this clearer (and probably remove -d so users can see what's happening)
Can someone who has used both wokwi and this do a compare/contrast? The footer suggests that it's built on top of wokwi-elements
Velxio is definitely inspired by Wokwi, and I really like what they’ve built. Parts of Velxio also reuse open-source components , for example, the wokwi elements are used for the visual SVG rendering of boards and peripherals, but they don’t include any emulation logic.<p>I also integrated a couple of existing open-source emulators, like the Raspberry Pi Pico and Arduino ones. And I even reached out to the creator of Wokwi to share the project.<p>In terms of differences, one of the biggest ones is that Velxio supports multiple heterogeneous boards in the same circuit: for example, two Arduinos connected over SPI or serial, ESP32 with Arduino, Raspberry Pi 3 with a Pico, etc.<p>Another major difference is the focus on full emulation, including ESP32 (via QEMU) and a Raspberry Pi 3 running Linux (still in beta).<p>There are also quite a few other differences, but those are probably the most notable ones
I often write a bunch of Esphome ‘code’ , which I then use with various esp32 based devices (mostly from M5stack) via esphome/HomeAssistant.<p>Can this project help me in any way during dev stage before uploading the code to device just to see it doesn’t work ? Eg could I use this to somehow compile&run those esphome yamls via this emulator?
That’s a really interesting use case. I’m currently evaluating integrating the ESPHome compiler into the project, so it could potentially compile and run ESPHome YAMLs during the development stage<p>It’s still exploratory, but it could definitely go in that direction
Awesome. Is there any chance of getting MicroPython or CircuitPython support?
I’m currently working towards that.<p>The Raspberry Pi emulation already runs Python, and I’d like to extend that into proper MicroPython / CircuitPython support for microcontrollers as well<p>It’s a bit tricky depending on the board/emulator, but definitely a priority!
Nice work! One minor point for me: it wasn’t immediately clear that you need to press Compile before Play gets enabled (e.g. Arduino IDE let's you upload right away and compiles if needed)
First of all: Awesome work! Playing with it now.<p>One suggestion: The main splash screen image is nearly 8MB big. It takes a noticeable time to download on my connection. I'm not sure what bandwidth costs these days, but seems like that could be something to optimize.
This is a great idea. It’s always been inconvenient requiring access to the physical board just to be able to test these sort of projects.
Exactly,that’s the idea. Not having to flash the chip a thousand times just to see if everything works. The goal is to let you test the setup as fast as possible, ideally without installing anything locally
[dead]
[dead]