The comparison
| Question | Electron | Tauri | Flutter | Qt | Krate |
|---|---|---|---|---|---|
| What you ship | A package per OS | A bundle per OS | A build per OS | A build per platform | One .krate file, and a link |
| What the user installs | Your package | Your package; WebView2 on older Windows | Your package; VC++ redistributables on Windows | Your app with Qt's libraries | Nothing for a link; the Krate runtime, once, to run natively |
| Per-OS builds | Yes; some installers only build on their own OS | Yes; macOS bundles on a Mac, MSI on Windows | Yes, with each OS's toolchain | Yes, each platform's environment | No; one build |
| Signing | Sign and notarize per OS | Sign and notarize per OS | Notarize on macOS; signed MSIX on Windows | macdeployqt can sign for notarization | None per OS for the app file |
| Sandbox and permissions | Renderers sandboxed; main process not | Capabilities for the frontend; core unconstrained | App Sandbox on macOS builds | OS consent APIs; no Qt sandbox | Whole app starts with no file or network access |
| App languages | JavaScript, HTML, CSS | Web frontend, Rust core | Dart | C++, QML, Python | Rust, or described in plain words to Studio's AI |
| Phones | No | Yes | Yes | Yes | Yes, from a link in the browser |
| Current release | Latest three majors supported | Stable v2; v3 in alpha | Stable, 3.47 | Qt 6.12, September 2026 | 0.5.4, September 2026 |
Sources: Electron distribution, signing and sandbox; Tauri distribution, security and webviews; Flutter desktop, macOS builds and platforms; Qt deployment, permissions and platforms. Wails and Neutralinojs are on the Electron alternatives page.
Three questions that decide it
- Do you want to hand people one file for every screen? Then Krate. Every other option here produces a separate build for each operating system.
- Do you need phones? Flutter, Qt and Tauri build store apps. A Krate app opens on a phone from a link, with no store and nothing to install.
- Do you have a web codebase you want to keep as it is? Then Electron or Tauri. Flutter, Qt and Krate each draw their own interface, and Krate Studio's AI can rewrite yours.
A fourth question sits under all of them: who decides what the app may touch? In most frameworks the developer decides. In Krate the person running the app sees what it asks for and grants it, and the runtime enforces that.
Signing and installers, whichever you pick
A native installer is signed for each system. On macOS, software distributed with a Developer ID must be notarized by Apple (Apple). On Windows, unsigned apps show a SmartScreen warning, and new signed apps can still warn until they build reputation (Microsoft).
A .krate file is not a native installer, so there is no per-OS signing of the app, and a link needs no install at all. On macOS the Krate runtime is signed and notarized by Apple. More on the code signing page.
One file, proven on three systems
The same .krate files pass automated checks on macOS, Windows and Linux in CI: 10 apps on all three at Krate 0.5.4.
Ten ported apps, as the same committed .krate files, passed their headless replay checks on macOS (Apple silicon), Ubuntu (x86_64) and Windows (x86_64) GitHub runners with runtime 0.5.4 on 29 September 2026. Records: macOS, Ubuntu, Windows. Native runtimes are published for Apple silicon and Intel Macs, x64 and ARM64 Windows, and x86_64 and arm64 Linux.
Measured against an Electron editor
Krate's Notes app is one 36.6 KiB file. Holding 50,000 lines, it used 178.5 MiB of memory against 2,299.4 MiB for MarkText, an Electron editor: 13x less. A warm open took 237.1 ms against 611.5 ms: 2.6x faster. MarkText takes 284.6 MiB installed; the Krate runtime is installed once and shared by every app.
Measured on 25 August 2026 on an Apple M4: Krate's Notes app against MarkText 0.17.1 on the same 50,000-line notes workload, an equivalent workload. Read the method.
Questions
What is the best cross-platform desktop app framework?
For one file on every screen, Krate: it runs natively on every desktop and opens from a link in any browser. For an existing web codebase, Electron or Tauri; for store apps on phones, Flutter, Qt or Tauri.
Which framework needs no build per operating system?
Krate: you build one .krate file and the runtime on each system opens it. The others produce a build for each operating system.
Which frameworks avoid a browser engine?
Flutter and Qt draw their own interface, and so does Krate's runtime. Electron bundles Chromium, and Tauri uses the system WebView.
Is Krate open source?
Yes. The runtime, the .krate format and the CLI are MIT OR Apache-2.0, and Krate Studio is under the Business Source License 1.1. The source is on GitHub.