Canvas

A visual engineering canvas, wired to a real Runtime

The canvas is where components become graphs, workflows and connected systems. It is a place Devory shows you a system — not a room every page traps you inside.

How the canvas works

Visual composition

Available in pilot

Software is composed on a canvas of rounded-square tiles. Each tile is a real engineering capability with a type, configuration, inputs and outputs — inspectable at a glance rather than a picture that only looks like software.

Connections describe relationships

Available in pilot

A connection between two tiles is the real path data or control takes between them. Connections are drawn locally, between tiles that actually relate — not as page-length decoration.

Local execution

Available in pilot

A deterministic local Runtime plans, schedules and executes tile graphs as real operating-system processes across multiple languages, journals every run, and recovers from ordinary failures.

Cloud-connected canvases

In active development

The same graph model is designed to move between a local canvas and Devory Cloud's workspaces. Binding local and cloud canvases into one consistent experience is active, ongoing work.

What the canvas does not do today

  • Execution is limited to trusted, known components — no untrusted code sandbox exists yet
  • Browser-based execution is policy-defined but not wired to an executor
  • An automated crash-resume worker does not yet exist — a stalled run is retriable, not auto-resumed

See how components become a canvas

The canvas is built from components — read how those are defined, tested and reused.