Krate Studio
Krate StudioMake an app. Share the file.
Create and revise desktop software with AI, inspect its source and test what you built. Share one .krate file for Mac, Windows and Linux. Recipients install a compatible Krate runtime to open it.
What is in it
The build, watched
Compile, check, run and pack, with the engine's real output on screen.
Port what you have Beta
krate port reads a project you already have and tells you what it would take. Read-only.
AI-assisted, source included
Claude, Codex, Grok or Gemini on your computer, or Krate's own AI in your browser. Then read and change the source. Prefer your editor? The CLI does the build and packaging.
The wall
Read what any app declares without running it: krate run app.krate --dump-caps
See it render
Every build paints a real frame. Screenshot your app in CI with no display attached.
Ship three ways
The file, a link, or a card that carries the app inside a picture of it.
Four steps
Real timings on an M4.
- 1Say what it isseconds
- 2It buildsminutes
- 3It runs~2s
- 4One fileinstant
Built with it
Each one is a single file, around 110 KB, running from the same bytes on Mac, Windows and Linux.
Questions
What language do I write in?
Rust today, compiled to a WebAssembly component. The guest is ordinary Rust with one rule: it may import only krate:* interfaces, never wasi:*. Host access goes through Krate's capability checks. krate check-app checks the build, imports, execution and rendering; you still need to test the app's behavior.
Can I bring an app I already have?
That is what krate port is for. It reads your project and reports what maps cleanly, what needs a capability, and what will not work at all. It is read-only: it never builds, runs or edits your source. Start there before you decide whether the rest is worth your weekend.
What can it not do yet?
Check the current capability and limits guide against what your app needs. Some host integrations and UI features are still incomplete; a successful build is not proof that every interaction works on every platform.
How big is the runtime my users install?
Size depends on platform, architecture and release. The current release lists download sizes; these differ from installed footprint. Users install the runtime once, then receive compatible apps as files. Our measurement guide separates runtime, bundle and application-payload costs.
What happens to my dependencies?
Dependencies must support the guest target and Krate's import boundary. Direct OS calls need a supported Krate interface or a rewrite; not every library or host feature has an equivalent. krate port tells you which of your dependencies land on which side of that line.
Do I have to use the AI?
No. You can write the source yourself and use the CLI to build, pack and run it. krate create is the AI-assisted route and needs a configured provider. The quickstart explains the prerequisites.
Is my app locked to your servers?
A local app can run with the open-source Krate runtime without Krate Cloud. The bundle carries the app and its source. Apps that call APIs or use hosted services still depend on those services; the file format cannot make an online service work offline.
Build once. Ship one file.
Use Studio to create and revise an app, then share the file. The runtime is open source; hosted services are optional.