Side by side
| Question | Tauri | Krate |
|---|---|---|
| What you ship | An installer or bundle per platform: DMG or app bundle, a Windows installer, AppImage, deb, RPM, Flatpak or Snap. | One .krate file for macOS, Windows and Linux, and a link that opens it in any browser. |
| Interface | Your web frontend in the system WebView: WebView2, WKWebView or webkit2gtk. | Krate's own UI, drawn natively by the runtime. No WebView. |
| App logic | Rust commands, with plugins in Rust, Swift or Kotlin. | A WebAssembly component in Rust, written by you or by Studio's AI. |
| Permissions | Capability files the developer writes grant or deny commands per window. | The app requests access in its manifest; the person running it grants or refuses. |
| Signing | Required on most platforms. Direct macOS downloads also need notarization. | No per-OS signing of the app file. Optional Krate signature with your own key. |
| Platforms | Windows, macOS, Linux, Android and iOS. | macOS, Windows and Linux natively, and any modern browser from a link, phones included. |
Tauri facts: distribution, capabilities and WebView versions.
Who holds the permissions
Tauri's capabilities limit what the frontend in the WebView may call. They are chosen by the developer, and Tauri's own docs say they do not protect against malicious or insecure Rust code in the app itself. They protect users from a compromised frontend.
In Krate, the whole app is the guest. It has no direct line to the operating system; it calls Krate interfaces, and the runtime checks protected calls against what the person running it allowed.
Shipping a release
With Tauri, a release means building on each platform, usually in a CI job per system, signing for each platform, and hosting and updating each package. With Krate, a release is one new .krate file. Publish it and send the link, and it opens in any modern browser, phones included, with nothing to install and no account; on a desktop, the same file runs natively.
Moving a Tauri app to Krate
Both are Rust, so a lot comes with you. Run the scan, which reads your source without building it:
krate port ./my-tauri-app
krate port is in beta. Pure Rust logic often carries over as it is; the WebView interface moves to Krate's widgets, canvas and host interfaces, and Krate Studio's AI can do that part for you. See the porting guide.
Questions
Which one should a Rust developer pick?
Pick Krate when you want one file for every desktop and every browser, no WebView, and permissions the user approves before the app opens. Tauri suits a team that wants to keep a web frontend and ship a bundle per OS.
What does the person I send it to install?
With Tauri, your app's own installer or bundle for their system. With Krate, nothing to open a link; to run it natively, the Krate runtime once, and then every .krate opens from the file.
Is Krate built on Tauri?
No. Krate is its own runtime, built on Wasmtime. It does not use a WebView.
How does a Tauri app move to Krate?
With a port. Rust logic often carries across, and krate port (beta) and Krate Studio's AI rewrite the WebView interface against Krate's interfaces.
Which one makes smaller downloads?
Krate apps are tiny: Krate's Notes app is one 36.6 KiB file, and a link needs nothing installed. The native runtime is installed once and shared by every Krate app, so each new app is only its own file.