The three apps and the plane

c1302026-11-10

What runs where after the roadmap: the sensor and the native app on the endpoint, the control plane with its web app and two databases, and the people on each side.

Source: Session 1b21a3ce (Tyler Flint, 2026-11-05): the UI leaves qcontrol; a native app plus the tray; the control plane as SaaS and self-hosted on Pulse, Postgres and ClickHouse. c130 plan.md D4, D6, D9; c134 plan.md §The shape; c136 D1; c137 D1. Drawn with qmap.

Loading the scene…

On the endpoint · deploy

◇qcontrol

the sensor: under 1% of a core, under 30 MB; watches the harnesses' traffic; SQLite behind it

▣The native app and the tray

GPUI Kit; Status, Inventory, Events, Config, Connect; local or connected; the person's one surface

The plane · connect to

▣The control plane web app

qdash's pages in app.qpoint.io's frame; the operator's surface; SaaS or self-hosted from one image

◇Go API (Pulse, new data model)

API first; Postgres for state, ClickHouse for events; grants and messages are plane objects

People

●The operator

IT or security; writes policy, reads findings, sends notices (the overseer)

●The person at the keyboard

sees what was found on this machine and why something was enforced (the citizen)

●Qpoint's mechanic

in only under a time-boxed grant (c136)

ours to build (c131, c134)exists (qcontrol)engineering's (Kamal: the plane's backend)people

The problem

The web UI bundled into the sensor cost memory and credibility: to show Cisco under 1% and under 30 MB the dashboard had to be turned off. The UI leaves the sensor; the endpoint gets an app built for one machine.

The core idea

Three verbs, three objects: you deploy qcontrol, you open the native app, you connect to the plane. Every flow in the scene is one of them, or the data they carry (events up, messages down, a grant opened by the operator).

What is still open

The names (c0); which messages flow in V1 (c137, Tyler at G2); the plane's identity model (c134 D2); the repo the native app ends up in (D4, Tyler at G2).