ArchHub / public lens

One canvas. Every tool you already use.

ArchHub is a graph you can read. Hosts, AI drafts, memory and permissions sit on one canvas as nodes and wires, so you can see what happened and why.

The three pillars

Canvas. Composer. Brain.

The whole product is three ideas, and not one of them is a chat box.

01The surface

Canvas

Every action is a node; every node is replayable. Drag a parameter and the chain downstream re-runs. Nothing happens that you can't see, trace, or undo.

02The hand

Composer

Talk to the project. The AI proposes edits to the graph; you approve the line before it's drawn. Set out, don't ask out: review is the default, not an afterthought.

03The memory

Brain

Persistent memory and reusable skills that grow with your firm. Save any thread as a skill: a graph-held assembly you own, with the work it was learned from and the evidence that earned it. No marketplace lock-in.

Self-healing connectors

Your CAD tells us when it breaks. We listen.

No restarts. No "please relaunch Revit." The connector watches the host, reconnects on its own, and tells you what it did.

  • -manual restartsLAST 7 DAYS
  • -recovered sessionsLAST 7 DAYS
  • -median recoveryALL HOSTS

Connection healthy

BEFORE
handshake-
rpc port-
session-
→
AFTER
handshake-
rpc port-
session-

Idle. The connection is nominal. Break it and watch what happens.

illustrationYou didn't notice. That's the point.

The canvas

A graph you can audit, not a transcript you have to trust.

  • 01
    Replayable by constructionRe-run any node from any upstream state. The same inputs always draw the same line.
  • 02
    Parametric, not one-shotEvery chat turn becomes a parameter. Nudge a slider; the chain re-runs from that node down.
  • 03
    Auditable wiresEvery connection is typed and logged. Hover any wire to see exactly what passed through it.