What Glyph is (and is not)

Public

One sentence. Glyph is a collaborative programmable whiteboard and a visual AI workflow builder, where you compose and run flows on a real-time multiplayer canvas.

One paragraph. A Glyph document is one of three things — a freehand whiteboard, an executable node graph, or a hybrid of both — that can be edited live by multiple people. The graph mode chains operators (typed nodes for LLMs, APIs, data transforms, triggers, control flow) into a DAG that the Rust backend compiles, schedules, and runs. Real-time presence and conflict-free editing are powered by Yjs, split across four CRDT subdocs per document. The whole thing runs as a Layer 2 cell on the DJED platform — one Rust binary, one React app, one Caddy site.

What Glyph is for

Designing AI workflows without leaving the canvas — you can sketch the architecture as a diagram and have it actually run.
Working together in real time — co-editing a graph the way you’d co-edit a Figma frame, including draw layer and threaded comments.
Shipping flows behind triggers — webhook, schedule, chat, form, connector — so a flow becomes an addressable service.
Versioning and replaying — every run is checkpointed and idempotent; you can resume from a breakpoint or re-execute a step.

What Glyph is not

Not a notebook. Cells in a notebook share global state implicitly; operators in Glyph are pure functions over their typed ports, by design.
Not a no-code app builder. Glyph builds flows, not UIs. If you need a form-driven CRUD app, build it elsewhere and call Glyph via webhook.
Not a one-and-done generator. A Glyph flow is a living thing: trigger it, schedule it, version it, observe it. Output of a single LLM prompt is a degenerate case.
Not a hosted black box. It is a DJED cell — the binary, schemas, and infrastructure all live in this repo and you can read them.

How to read these docs

Public pages (this section) cover concepts. Anything operational, anything internal, lives under Admin and requires a Zitadel admin role.