Forge is preparing the requested surface and verifying the live route.
Forge is preparing the requested surface and verifying the live route.
Forge observability is an app/workspace capability for user-owned accounts and self-hosted runtimes. The public website explains the model without exposing a live dashboard.
Forge observability follows the same boundary as Forge operation: the account or local runtime that runs the work owns the traces, cost evidence, policy outcomes, and replay receipts. Public pages stay informational.
Forge records request, routing, tool, policy, memory, and provider evidence in the runtime that owns the work. The website describes the model; the app shows the live workspace evidence.
Users inspect spend, latency, provider choice, and usage envelopes from their signed-in or self-hosted workspace where account data is scoped.
Forge can connect Langfuse, OpenTelemetry-compatible exports, and evaluation tools without making public marketing pages a monitoring console.
Runaway spend, policy blocks, provider failures, and quality regressions are handled by governed runtime owners with receipts and next actions.
Use the desktop, mobile, or signed-in workspace to inspect traces and alerts for the runtime you own. That surface can enforce auth, redact sensitive data, and preserve receipts.