App Kits
An App Kit (short: Kit) is a Bindle-declared application surface — the kinds that host entrypoints or interactive runtime behavior. Kits compose runtime ports into something you pack in a Bindle; providers implement those ports behind WIT interfaces.
App Kit kinds
| Label | Kind | Role |
|---|---|---|
| API Kit | api | HTTP API entrypoint |
| Web Kit | web | Web / HTML entrypoint |
| Service Kit | service | Long-running HTTP service |
| UI Kit | ui | UI render surface |
| Realtime Kit | websocket | Realtime rooms / sockets |
| Job Kit | job | Batch / async work |
| Component Kit | wasm-component | Wasm component dependency as surface |
Helpers: app kit kinds and labels in the Bindles SDK.
Infra Kits (not App Kits)
Infrastructure/port resources that are not entrypoint hosts:
kv · bucket · queue · topic · secret · data · schedule · external · container · flag · auth · crypto · notify · guardrail · golden · experiment · rollout
See infra kit kinds in the Bindles SDK.
HTTP App Kits
Subset of App Kits that local Yard hosts serve as fetch handlers:
api · web · service · ui — HTTP_app kit kinds / isHttpAppKitKind.
Session Replay
Every App Kit is Session-Replay capable by default: privacy-first capture, dual fixtures locally, progressive gating in production. Infra Kits are not auto-annotated.
Opt out per Kit:
import { sessionReplay } from "hobo/bindles";
b.api(handler).with(sessionReplay({ enabled: false }));Kill switch: HOBO_REPLAY=0. Full surface: Session Replay.
Naming split
| Term | Layer | Meaning |
|---|---|---|
| App Kit | Bindle authoring | Entrypoint-bearing resource kinds |
| Infra Kit | Bindle authoring | Port / infrastructure resources |
| WIT port | Runtime capability interface | Host/provider link for a Kit |
Related
Bindles · Resource catalog · Session Replay · WASM & WIT · Core concepts