Channels — apps on your machine

A channel is a real application you host on your machine. Not just a static page — a channel can be a full front end and back end: an HTML/JS interface and an optional Python back end, plus any supporting files. A machine hosts as many apps as you like on its pages shelf, each versioned, each served at /s/<machine>/…, each computing against your machine through a key-free proxy. Every application in the gallery is a channel built exactly this way.

You build a channel the way you build any web app — write the front end and, if it needs one, the back end, then publish. Do it by hand in your editor, or scaffold it in the browser workbench; either way it's your code, versioned on your machine.

What a channel is made of

A front end

Self-contained HTML, CSS, and JS — the interface your users touch, served straight from your machine.

An optional Python back end

A Python script that runs server-side for the app — so a channel is a full-stack app, not just a document.

The key-free proxy

The app calls ./sdk/zeq/compute on its own origin; the node attaches your machine's identity server-side. No key ever ships to the browser.

Explore

Build & publish

From an idea to a live, versioned app.

• Building apps — author by hand or in the workbench
• Publishing & serving — the full-stack shape, versions, rollback, and the key-free proxy
• The channels reference — page-management endpoints

See it in use

Real apps, running as channels.

• The applications gallery — every app is a channel
• Contracts — the logic an app's back end drives