Hey Product Hunt — I built RustFrame because local-first desktop tools should not force frontend developers to own a native backend just to get SQLite, scoped file access, and installers. RustFrame is an open-source Rust runtime and CLI around the frontend stack you already know. Start with TypeScript or JavaScript, React, Vue, or Svelte; RustFrame owns the native runner, window lifecycle, embedded SQLite, permission checks, and platform packaging. Research Desk is the flagship proof: it indexes a folder the user chooses, keeps source files in place, tracks review state locally, and exports portable data. This is 0.1.0-rc.2, not a finished v1. The CLI artifacts are public, but rustframe-api has not yet reached npm, so the registry-only generated-project path is not publicly supported. Public apps may also need platform signing or notarization, and Linux is X11-only in this candidate. I am looking for feedback from people building research desks, document tools, media queues, operations consoles, or offline-first internal apps. Please try the site and release, inspect the capability model, and tell me: is the boundary between frontend-owned workflow and RustFrame-owned native runtime clear? Which quickstart or packaging step still feels risky or confusing?

RustFrame

Build local-first desktop tools with your frontend stack

Build local-first desktop tools with your frontend stack