Example repo: https://github.com/valdanylchuk/breezydemo
The underlying ESP-IDF component: https://github.com/valdanylchuk/breezybox
It is something like Raspberry Pi, but without the overhead of a full server-grade OS.
It captures a lot of the old school DOS era coding experience. I created a custom fast text mode driver, plan to add VGA-like graphics next. ANSI text demos run smooth, as you can see in the demo video featured in the Readme.
App installs also work smoothly. The first time it installed 6 apps from my git repo with one command, felt like, "OMG, I got homebrew to run on a toaster!" And best of all, it can install from any repo, no approvals or waiting, you just publish a compatible ELF file in your release.
Coverage:
Hackaday: https://hackaday.com/2026/02/06/breezybox-a-busybox-like-she...
Hackster.io: https://www.hackster.io/news/valentyn-danylchuk-s-breezybox-...
Reddit: https://www.reddit.com/r/esp32/comments/1qq503c/i_made_an_in...
Hello everyone!
I'm a solo developer who's been doing UI/UX work since 2007. Over the years, I watched design tools evolve from lightweight products into bloated feature-heavy platforms. I kept finding myself using a small amount of the features while the rest just mostly got in the way.
So a few years ago I set out to build a design tool just like I wanted. So I built Vecti with what I actually need: pixel-perfect grid snapping, a performant canvas renderer, shared asset libraries, and export/presentation features. No collaborative whiteboarding. No plugin ecosystem. No enterprise features. Just the design loop.
Four years later, I can proudly show it off. Built and hosted in the EU with European privacy regulations. Free tier available (no credit card, one editor forever).
On privacy: I use some basic analytics (page views, referrers) but zero tracking inside the app itself. No session recordings, no behavior analytics, no third-party scripts beyond the essentials.
If you're a solo designer or small team who wants a tool that stays out of your way, I'd genuinely appreciate your feedback: https://vecti.com
Happy to answer questions about the tech stack, architecture decisions, why certain features didn't make the cut, or what's next.