Krate app maker

Ask for an app. Get one file. Send it.

Make a small app from a request, or connect your coding agent. Krate gives you one file that opens on Mac, Windows, and Linux and shows its access before it runs.

Make an app I received one
One app file Three operating systems Clear access
MAKE_APP.EXE
What do you need?
Make a checklist app that saves locally.
YOUR_APP
checklist.krateREADY TO SHARE
ACCESS_MANAGER
✓Show a windowALLOW
✓Save checklist itemsALLOW
KRATE DESKTOP 1.0

Start menu

Choose what you want to do.

You do not need to understand runtimes or app packaging first. Pick your path and Krate will show you the next step.

OPEN_APP□ ×

I received a Krate app

Install Krate once, double-click the file, review what it needs, and open it.

Show me how →
CREATE_APP□ ×

I want to make an app

Create a small app from a supported request, or build one yourself with the Krate SDK.

Make an app →
CONNECT_AGENT□ ×

We build AI products

Connect your coding agent so it can hand users a local app instead of loose code.

See the integration →
KRATE SETUP WIZARD

Set up once

Get the krate tool.

You need it on any computer where you want to open or make Krate apps. Paste this line into a terminal and press Enter.

TERMINAL.EXE
curl -fsSL https://raw.githubusercontent.com/incyashraj/krate/main/scripts/install.sh | sh
Making an app? krate create also needs the Rust build tools. It checks what is missing before it starts. Run krate doctor any time to see what is ready.
01

For anyone

Someone sent you a .krate file.

OPEN_APP.WIZ
1

Double-click the file

Krate shows what the app wants before any app code runs. You might see a window and access to its own data folder.

2

Review the list

If the request makes sense, allow it. If it asks for something it should not need, say no.

3

Use the app

Close it and open it later. Its approved data stays saved, and the same app file works on Mac, Windows, and Linux.

Try saying no. Withhold access the app requires and it does not start. The app cannot ignore your choice.
02

For makers

Describe a small app. Get one file.

CREATE_APP.WIZ

New to Krate? This walks you through it from the very beginning. You type each line into a terminal (on a Mac it is called Terminal; on Windows it is called PowerShell). Do the steps in order.

1

Get the krate tool

You only do this once per computer. Paste this line into a terminal and press Enter. It downloads Krate and sets it up for you.

TERMINAL.EXE
curl -fsSL https://raw.githubusercontent.com/incyashraj/krate/main/scripts/install.sh | sh

Check it worked. This should print a version number:

TERMINAL.EXE
krate --version
2

Let it set up the app-building tools

Making an app also needs the Rust build tools. You do not have to know what those are. The first time you make an app, Krate checks for them, tells you what is missing, and offers to install it for you. Say yes when it asks.

Want to check first? This shows you what is ready and what is not:

TERMINAL.EXE
krate doctor
3

Say what you want

Describe your app in plain words. The built-in creator currently makes a checklist or a word-frequency tool. Pick a file name that ends in .krate.

TERMINAL.EXE
krate create "Make a checklist app that saves my items" \
  --output checklist.krate

The first run may take a minute while the tools install and the app builds. That is normal.

4

Krate builds and checks it

Krate writes the app, checks it, packages it, and tests that its permission wall behaves correctly. When it finishes you have one file: checklist.krate.

BUILD STATUS
Created checklist.krate
requested access:
  - show a window
  - save checklist items
5

Open it, and send it

Double-click checklist.krate to use it yourself. To share it, email it, message it, or put it in a shared folder. The next person opens the same file and reviews its access first.

Prefer to use your own AI to write the app? That works too, and it removes the two-template limit. See Let your coding agent deliver a real app just below.
Want to build something else by hand? Write it with the Krate SDK and package it using krate pack. Follow the Create and Share an App guide.
03

For AI teams

Let your coding agent deliver a real app.

Your agent already writes code. Krate gives it a route from a request to one local app file with declared access.

AGENT_CONNECT.WIZ

This uses your own AI coding tool to write the app, so you are not limited to the two built-in templates. You describe anything; your AI writes it; Krate builds and checks it.

1

Have an AI coding tool ready

You need a command-line AI coding tool that is already signed in on your computer, such as Claude Code (the claude command). If you can run it in a terminal, you are ready.

2

Point krate create at it

Add --agent claude. Krate hands Claude Code your request and a folder, and it writes the app. Here it makes a grocery list:

TERMINAL.EXE
krate create "A grocery list app called My Groceries" \
  --agent claude \
  --output groceries.krate

Using a different AI tool? Use --author-cmd "<your command>" instead of --agent.

3

Krate checks the result

Krate builds what your AI wrote, refuses anything that reaches outside the Krate rules, packages it, and tests its permission wall. If your AI writes something unsafe, Krate stops it here. It never reaches the user.

4

Hand the user one file

The user receives a .krate file, sees what it requests, and decides what it may access before it opens.

Building AI products? Your agent can also drive Krate directly over a standard connection with krate mcp, so it can inspect and run apps inside the sandbox on its own.

Access control

Know what an app wants before it opens.

A Krate app declares what it needs. You see that list before it runs, and the runtime limits it to the access you approve.

Krate reduces the access you must trust an app with. It does not promise that every app is free of bugs.

KRATE ACCESS MANAGER
Checklist wants to openapp.krate.checklist
✓Show a windowALLOWED
✓Read and write ./checklistALLOWED
×The rest of your filesBLOCKED
×The internetBLOCKED