Source: c62 build-partner — two-track expansion (Qkit + dashboard), 2026-08-10
The demo ends and the room forks: solution providers (Cisco, F5, Vanta) heard "this is what you could build"; operating companies heard "this is the product." This is the page the demo lands on — four concepts for communicating one stream, two ways to build on it, plus the partner arrangement behind each track. Grounded in the real contract (qevents · 57 wire types · 9 families) with live vs projected honestly badged throughout. Names are working names.
The fork
The pricing-page shape, because it's the shape everyone in the room already knows how to read: thesis sentence, two cards, one differences table, the arrangement under each. Nothing clever — the clarity is the design.
One stream, two ways to build on it. qcontrol observes AI agents at runtime and emits one canonical event stream. You can build your offering on the stream — or run the dashboard we already built on it.
The unified AI-agent event stream as a product: versioned contract, typed schema, your offering on top.
Visibility and control over your org’s AI usage, as-is — built on the same stream.
| Qkit | the qcontrol dashboard | |
|---|---|---|
| you are | a solution provider | an operating company |
| the product is | the event stream + contract | the dashboard |
| the UI is | yours | ours |
| you integrate via | a collector on the socket | deploying qcontrol + the dashboard |
| success looks like | your offering ships an AI-agent capability | your org’s AI usage is visible & governed |
| the arrangement | Founding Integrator — co-develop the contract | Founding Partner — pilot → convert |
| shared | the stream itself · sharp-edges access · attribution ledger · direct line · numbered founding status | |
The stream is the product
Architecture-first: the nine event families drawn as one spine, forking to its consumers — your product on one branch, our dashboard on the other. The demo pivot ("everything you just saw came from this stream") made visual. Projected families are dashed amber and say so; co-developing them is the Track-1 arrangement, so the honesty is also the ask.
148,912 events
The demo epilogue
Designed as the literal next click after the dashboard demo: first it replays what the room just saw, tile by tile, naming the event family that powered each beat — proof by recap. Only then the fork, now carrying the momentum of the demo instead of restarting the pitch from zero.
Every one of those pages is a projection of one event stream. We built a dashboard on it. The question that forks the room: what would you build?
The honest contract
For the engineer Cisco or Vanta brings to the meeting: no thesis, no cards — the contract itself. What exists is downloadable today; what doesn't is labeled projected and framed as the co-development agenda. Trust through specificity: this page wins the technical evaluation that follows every good demo.
| Event family | Wire types | Status | Notes for collector authors |
|---|---|---|---|
| Agent activity | agent.message · tool_call · tool_decision · tool_result | live | tool decisions carry approved/denied + source (config | user | policy) |
| Model interaction | llm.request · response · usage · rate_limit | live | tokens + cost per call; provider_matched/_unmatched tells you what coverage you actually got |
| Tool supply chain | mcp.request · response · error · oauth | live | transport, protocol version, advertised server name per session |
| Data access | file.open/read/write/close · exec.spawn/exit | live | metadata only — paths and byte counts, never contents |
| Network egress | connection.* · http.* · sse.* · websocket.* | live | 5-tuple, resolved domain, TLS details, full headers; MITM coverage signals |
| Fleet inventory | installation.discovered · details · snapshot | live | declared MCP servers, skills, default model — at rest, before anything runs |
| Runtime inventory | process.started · stopped · snapshot | live | agent attribution with match strategy + confidence |
| Findings & detections | finding.raised · dlp.hit | projected | detectors exist downstream today; promoting them to the stream is co-development item #1 |
| Session lifecycle | agent.session_start · session_stop | projected | session id rides on payload context today; explicit boundaries are item #2 |
The composed page
The concepts aren't rivals — they're altitudes of one page. A composes the demo-day landing (epilogue energy, fork clarity, picture for the boss); the contract stays one click deep for the engineer. B is the standalone version for visitors who didn't get the demo. Both end at the same two doors.