peko / vs tauri
A Tauri alternative that ships to the stores for you
Peko and Tauri are close cousins. Both wrap the web UI you already built in the system webview, so the app is small, fast, and looks native, with deep native control over the window, menus, and device APIs. If all you want is the shell, they’re comparable.
The difference is everything around the binary. Tauri hands you a build. Peko carries your app the rest of the way: cross-compile and sign from one CLI, generated store screenshots and listing metadata, remote Apple builds so you don’t need a Mac, hosting, and a guided path into every store. Your native layer is a few lines of PekoScript, not a Rust project.
| Capability | Peko | Tauri |
|---|---|---|
| Reuse your existing web UI (React, Next, Vue, Svelte, Astro) | Yes | Yes |
| System webview: small binary, looks native | Yes | Yes |
| Deep native control (window, menus, any native API) | Yes | Yes |
| Native layer languagePeko: a few lines of PekoScript · Tauri: Rust | Partial | Partial |
| One CLI cross-compiles + signs every platform | Yes | No |
| Store screenshots generated for you | Yes | No |
| Store listing metadata drafted for you | Yes | No |
| Remote Apple builds without a Mac | Yes | No |
| Integrated hosting for your backend | Yes | No |
| Guided path to the App Store, Play, and MS Store | Yes | No |
✓ built in · — do it yourself. The shell rows are a wash, which is the point: Peko is Tauri-class where it counts, then keeps going through the whole release pipeline.
When Tauri is the better fit
If you want to write your native layer in Rust, need bleeding-edge control of the webview internals, or don’t care about the store pipeline, Tauri is excellent and Peko won’t do it better. Peko is for teams who’d rather write a few lines of PekoScript and have the build, signing, assets, and store submission handled end-to-end.
Peko's CLI (peko-tools) and Studio (peko-studio) are MIT open source on GitHub.