App traffic
gateway requestsOpenAI-compatible chat, tool calls, and provider routing through the Gateway.
Observe real runs, route model traffic, run eval workflows, enforce cost and safety policies.
| Trace ID | Signal | Source | State |
|---|---|---|---|
| tr_8f9a2b | Tool loop stopped | Guardrail | Blocked |
| tr_1c4d5e | Budget policy exceeded | Usage | Blocked |
| tr_3b6a9c | Provider fallback used | Gateway | Settled |
| tr_7e2f1d | PII detected in prompt | Guardrail | Review |
Observability
Send OTLP telemetry or route model calls through the Gateway. Spans, tool calls, tokens, cost, errors, and attachments stay tied to one trace.
import { NodeSDK } from '@opentelemetry/sdk-node';
import { OTLPTraceExporter } from '@opentelemetry/exporter-trace-otlp-http';
const sdk = new NodeSDK({
traceExporter: new OTLPTraceExporter({
url: 'https://api.provon.dev/v1/traces',
headers: { Authorization: `Bearer ${process.env.PROVON_API_KEY}` }
}),
});
sdk.start(); | Trace ID | State | Signals |
|---|---|---|
| tr_892a4f | Settled | gatewaycost |
| tr_892a50 | Blocked | guardrail |
| tr_892a51 | Reviewed | eval |
| tr_892a52 | Flagged | tool-loop |
Automation
Trigger on traces, schedules, or Gateway events. Run rule or LLM evaluators, then route results to findings, notifications, and external tables.
Read the docs →How it works
You either route model calls through the Gateway or send OpenTelemetry directly. Provon ties every signal to a project, evaluates it with the same policies, and gives your team an auditable trace instead of scattered logs.
OpenAI-compatible chat, tool calls, and provider routing through the Gateway.
OTLP traces, logs, metrics, GenAI attributes, token usage, and errors.
Schedules, manual reruns, incident reviews, and policy updates from the Workspace.
Project API keys attach every request to an organization, project, environment, and billing period.
Gateway calls and raw OTLP signals become one trace timeline with spans, logs, metrics, costs, and attachments.
Budgets, routing rules, guardrails, retention windows, and evaluator workflows run against the same evidence.
Provon stores the trace, creates findings, triggers workflows, and keeps data for the plan window.
Trace search, findings, datasets, gateway settings, cost review, and workflow history.
Slack, Lark, Notion, Airtable, issue trackers, and dataset exports.
Usage alerts, data retention, audit-ready evidence, RBAC, SSO, and admin controls.
Edge API, hosted Workspace, managed metadata, and telemetry lake storage.
Node runtime with injected SQLite/libSQL, DuckDB/MotherDuck, and blob storage adapters.