Tish - Native Performance, Familiar Syntax

Zectre is the primary path we document for hosted apps. Tish also compiles to other shapes you can run wherever fits your stack.

What you can ship

Output	Typical use
Native binary	`tish build` → run on Linux/macOS under a process manager or VM
Docker image	Any container host (including Zectre — see Docker on Zectre)
WebAssembly	Browser or WASI runtimes — see WebAssembly targets
JavaScript	Bundlers and Node — `tish build --target js`

There is no first-party “Deploy to Vercel / Heroku / Netlify” button for arbitrary Tish apps. You can use those products’ normal workflows when your artifact matches what they expect (for example static files from a wasm build, or a Dockerfile on a container-based tier).

Mental model

The zectre CLI is intentionally Vercel-like for Zectre. Other providers have their own UX; you bring the same Tish outputs you would run anywhere else.