Krate
Try Krate
Answer

How to distribute a desktop app: ship one file

Ship it as one .krate file: the same file runs natively on macOS, Windows and Linux, and sent as a link, it opens in any modern browser, phones included, with nothing to install and no account. There is no separate build, signature or download for each operating system, and the app asks before it touches anyone's files or the network.

Reviewed against Krate 0.5.4. 3 min read

The usual route, step by step

  1. Build once per operating system. Electron and Tauri share your code, then produce a separate package for macOS, Windows and Linux. In practice that means a build machine or CI runner for each system, and macOS signing needs a Mac.
  2. Often build once per processor. Apple silicon and Intel Macs, x64 and ARM64 Windows, x86_64 and arm64 Linux each need native code built for them, or a universal build that carries both.
  3. Sign and notarize. For direct downloads, macOS expects a Developer ID signature and Apple notarization, which needs a paid Apple Developer Program membership. On Windows, an unsigned download shows "Windows protected your PC", and even a newly signed app can be flagged as unrecognized until it builds reputation.
  4. Package and host each one. A DMG or app bundle for macOS, an installer for Windows, and AppImage, deb, RPM, Flatpak or Snap for Linux. Each gets its own download link and its own update path.

After all that, a conventional desktop program usually runs with the same access to files and the network as the person who opened it, unless the platform sandboxes it, as the Mac App Store does. A signature says who made the app. It does not limit which of your files the app can read.

Sources: Electron's code signing guide, Tauri's distribution guide and Microsoft's SmartScreen reputation guide.

The Krate route

  1. Make the app. Describe it in Krate Studio and the AI builds it, or write it in Rust with the Krate SDK. Studio can also bring over a project you already have.
  2. Pack one file. The result is one .krate, from 37 KB: a manifest that names the access the app wants, a WebAssembly component that holds the app, and optionally its assets and source. There is no machine code inside, so there is nothing to build per processor.
  3. Send it like a picture. Publish it and send the link, or email it, drop it in a chat or a shared folder. Everyone gets the same bytes.
  4. They open it anywhere. From a link, it opens in any modern browser, phones included, with nothing to install and no account. On Mac, Windows and Linux, the Krate runtime runs it natively; Krate for Mac is signed and notarized by Apple, and after the first install every new app is just its own file.
  5. They decide what it may touch. An app starts with no access to files or the network and asks for what it needs. The runtime checks protected calls against what was allowed. See how to see what an app asks for.

What you stop doing

You stop producing a separate package for each operating system and processor. You stop signing and notarizing each app for each platform, hosting a download per system, and asking people to run an installer that gets their full permissions. You ship one file, or one link, and spend the time on the app.

Smaller, measured

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.

Check it yourself

Download chart.krate, one file of 11,455 bytes with SHA-256 3d290c48f74936d5cdb45ceb0ee945bd0f7b5b0b21f87f79917bced3b4ca73c3. Follow the quickstart to see what it asks for and run it on any of the three systems.

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.

Questions

Can one file run on Windows, macOS and Linux?

A normal native executable can't, because each system uses its own executable format. A .krate can: it holds a WebAssembly component that the Krate runtime runs natively on each system, and a link opens it in any browser too.

Do the people I send it to need to install anything?

Not to open a link: it runs in their browser, phones included, with no account. To run it natively, they install the Krate runtime once from the download page, and every Krate app after that is just a file.

Do I need a code signing certificate to ship a .krate?

No. There is no package per operating system to sign and notarize, because a .krate isn't one. You can still sign a .krate with your own key so people can check it came from you; see code signing and Krate.

Can I ship an app I made with AI this way?

Yes. Make it in Krate Studio with the AI you already use, or bring an existing project into Studio. See how to share an app made with AI.

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.