This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Murasaki
Next.js DX for native desktop apps
The Next.js developer experience, in a real native window. File-based routing, Server Actions and API routes — rendered in the OS WebView, not bundled Chromium. The Rust shell ships prebuilt, so there's no Rust toolchain to install. Server Actions and API routes run in a bundled Node process, which makes them real — and the installer bigger than a Tauri app's. Shipsapp/.dmg andzip/.exe/.msi, with automatic updates using Ed25519-signed manifests. Linux: dev only for now. Pre-1.0.
Hi Product Hunt 👋
I build for the web. When I wanted to ship a desktop app, neither option felt like "just keep writing the app I already know how to write": Electron ships a whole Chromium, and Tauri — which is a genuinely good project — hands you a framework-agnostic shell and a Rust toolchain, not the Next.js-shaped app model I actually wanted.
So I built Murasaki. The idea is narrow on purpose: keep the Next.js developer experience, put it in a native shell.
• src/app/**/page.tsx is a route. Nested layouts, dynamic segments, loading / error / not-found boundaries — no router to configure.
• Server Actions and API routes work, and they actually run in Node, inside your app.
• Right-click opens a real OS menu — NSMenu on macOS, HMENU on Windows — not an HTML popup wearing a costume.
• The native layer is a Rust binding I wrote, but you call it from TypeScript, and there's no Rust toolchain to install — prebuilt binaries ship for all six targets. (If you need something the binding doesn't expose yet, that's a Rust change. I'm not going to pretend otherwise.)
Why bundle Node, when it makes the installer bigger? Because it's what makes Server Actions and API routes real rather than a shim — your 'use server' function runs in an actual Node process next to the window. I'd rather state the trade-off than bury it: the demo .dmg on GitHub is 44 MB and the installed .app is 121 MB, because Node is in there. If a small binary is your hard requirement, Tauri is the better answer, and I'd tell you so.
Auto-update and Windows packaging both land in this release: signed manifests, SHA-256-verified downloads, the app replaces itself and relaunches, and Windows installers cross-compile from a Mac. I spent last week finding out what actually breaks on real Windows hardware instead of assuming it worked — a Program Compatibility Assistant warning, an uninstaller that would delete files out from under a running app, and WebView2 processes leaking on every quit were all real, and all fixed.
Where it isn't there yet, plainly: Linux runs `murasaki dev` but has no packaging. Windows arm64 can build but can't auto-update. The binaries aren't code-signed. It's pre-1.0 and the API can still move.
What I'd love feedback on: does the Next.js-shaped API actually feel right, or does it break where you'd expect it to hold? And what's the first thing you'd try to build with it?
— ichi
About Murasaki on Product Hunt
“Next.js DX for native desktop apps”
Murasaki was submitted on Product Hunt and earned 0 upvotes and 4 comments, placing #99 on the daily leaderboard. The Next.js developer experience, in a real native window. File-based routing, Server Actions and API routes — rendered in the OS WebView, not bundled Chromium. The Rust shell ships prebuilt, so there's no Rust toolchain to install. Server Actions and API routes run in a bundled Node process, which makes them real — and the installer bigger than a Tauri app's. Shipsapp/.dmg andzip/.exe/.msi, with automatic updates using Ed25519-signed manifests. Linux: dev only for now. Pre-1.0.
On the analytics side, Murasaki competes within Open Source, Software Engineering, Developer Tools, GitHub and Vercel Day — topics that collectively have 668.6k followers on Product Hunt. The dashboard above tracks how Murasaki performed against the three products that launched closest to it on the same day.
Who hunted Murasaki?
Murasaki was hunted by ichi. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Murasaki including community comment highlights and product details, visit the product overview.
ichi