Show HN: Proa – A Rust web framework with fast SSR and multi-target rendering

burnrate 97 points 28 comments October 15, 2026
proa.so · View on Hacker News

Video: https://youtu.be/-CfCyvIKYyo?si=hCLuStkXxanCUJD1 Video on multi-target rendering: https://youtu.be/pJx84jdBDKU?si=HRRd6dgUWXiqeWhq Benchmarks: https://github.com/Proa-Labs/proa-benchmarks

Discussion Highlights (10 comments)

kianN

This looks really cool! I’ve been really appreciating the revival of old-school server side rendering and foundational web components, but with modern tools or approaches.

airstrike

Why does `fn render` need to borrow WebContext mutably?

egeozcan

Very cool idea, I'm going to test this! One nit: Forgive me if I'm missing something but why do you have pro components? Won't people vibe-code clones anyway? I'd rather have a donate button these days.

lwhsiao

Can I get a TLDR of why Proa is seemingly so much faster tha existing Rust web frameworks (Dioxus, Leptos, Topcoat)?

trnvll

Damn, projects like these really spark my curiosity about Rust. I guess it's time to try it out, fomo is getting too big haha

canadiantim

This looks amazing, really appreciate your minimal JavaScript approach. I’ll definitely try it out, could see myself potentially doing pro version in future.

contingencies

So... Multi-target = {chat, web, markdown}; Audience = {human, bot}; USPs = {speed, unified model} Since I don't believe the maintenance challenges of a non-unified model are particularly high-friction in the LLM era (even if they may be error-prone, since that is usually solved with CI/CD or TDD), the nominal utility of this angle of architectural enhancement is considered dubious. With regard to speed, there is no hardware shortage at present for any of these simple rendering tasks. Overall, a nice efficient codebase but suffering a bit from NIH syndrome solving no particularly acute problem. Unless a community forms rapidly, this will probably die. I'd like to see the benchmark compared to, eg. static files served with binserve.

farmeroy

This might be a silly question, but why 2 views for html and markdown? isn't there a broad base of cases where one can just be inferred from the other? Also, I think it's exciting to see so many rust web frameworks popping up but I'm in total decision paralysis. If I want to build something with rust now there are at least 3 complete frameworks: loco, topcoat and now proa... plus actix, rocket, axum, and ...more?

yieldcrv

I would be mostly curious about CI/CD and build and deployment times on underpowered compute instances I could drop the react ecosystem given considerable improvement over it at the deployment part Especially since years of experience with frameworks doesnt matter anymore and won’t matter with recruitment soon

jakswa

I was recently scanning for newer, more-batteries-included options and this looks well-scoped at first bluff. Thanks for spreading it, might end up in my next experiment!

Semantic search powered by Rivestack pgvector
9,619 stories · 90,738 chunks indexed