Krate
Try Krate
Answer

Krate vs Electron: one small native file with no browser inside

Krate ships your app as one small .krate file that runs natively on Mac, Windows and Linux and opens from a link in any browser, phones included; Electron puts Chromium and Node.js inside every app and ships a package for each operating system. On the same 50,000-line notes workload, measured on 25 August 2026 on an Apple M4, Krate's Notes app used 13x less memory and opened 2.6x faster than MarkText 0.17.1, an Electron editor doing the equivalent work.

Reviewed against Krate 0.5.4. 3 min read

Side by side

Electron and Krate, reviewed 6 October 2026 against Electron's official docs
QuestionElectronKrate
What you shipA packaged app for each operating system, each carrying its own Chromium and Node.js.One .krate file for every system, and a link that opens it in any browser.
App codeHTML, CSS and JavaScript in Chromium, with Node.js in the main process.A WebAssembly component that calls Krate's interfaces. Describe it in Studio and the AI writes it, or write Rust yourself.
Builds per OS and CPUOne package per target platform.One file. Krate builds the native runtimes.
SigningSign for Windows and macOS, and notarize for macOS, for each release.No per-OS signing of the app file. Optional Krate signature with your own key.
Default accessRenderers are sandboxed by default since Electron 20. The main process is not sandboxed and has Node.js.The app starts with no file or network access. The person running it grants or refuses each request.
PlatformsWindows, macOS and Linux.macOS, Windows and Linux natively, and any modern browser from a link, phones included.

Electron facts: process model, process sandboxing, code signing and distribution overview.

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.

What one file changes for shipping

With Electron, each release is a set of platform builds that you sign, notarize and host. With Krate, each release is one new file. Send the link and it opens in any modern browser, phones included, with nothing to install and no account. On a desktop, the Krate runtime opens the file natively, and because every Krate app shares that runtime, a second or third app never brings another copy of a browser.

Who decides what the app can touch

In Electron, the developer decides what the main process exposes to the sandboxed renderers, and the main process itself runs with the user's permissions. That is a sound design for code you wrote, but the person running the app has no say in it.

In Krate, the app lists what it wants in its manifest and the person running it approves or refuses, before it opens. The runtime checks protected calls against what was allowed, and hosts the app did not declare stay unreachable.

Moving an Electron app to Krate

Start with a scan. It reads your source without building or running it and shows how each part maps to Krate:

krate port ./my-electron-app

krate port is in beta. Krate Studio can do the move with AI: it rewrites the app against the Krate SDK and shows its plan first. Electron apps go from hundreds of megabytes to one small file. Begin with one representative feature and read the porting guide.

Questions

How do I move an Electron app to Krate?

Run krate port (beta) on the project, or open it in Krate Studio: the AI rewrites it against Krate's interfaces and shows its plan first. The result is one small .krate file in place of a package per OS.

Do Krate users need Chromium?

No. A Krate app runs natively, with no browser engine inside, and every Krate app shares one runtime. From a link, it opens in whatever browser the person already has.

Do I need to know Rust?

No. Describe the app in Krate Studio and the AI writes the Rust for you. Developers who like Rust can write it by hand with the Krate SDK.

Which one should I pick?

Pick Krate when you want one small file that opens anywhere, uses a fraction of the memory and asks before it touches anything. Electron suits a team with a large web codebase built on Node.js packages that wants to keep that code exactly as it is.

More answers about making and sending apps

Make your first app

Describe it and Krate makes it. Send it as a link that opens in any browser, phones included, and run the same file natively on Mac, Windows and Linux. The runtime, format and CLI are open source under MIT OR Apache-2.0 (licensing details), and the capability reference lists everything an app can use today.