Changelog
Public release notes for the web presence and announced platform milestones.
Changelog →Documentation
Technical documentation for PUVINoise™
Canonical reference for engineering teams integrating the SDK and operators reviewing how signals reach the control plane.
Overview
PUVINoise is a multi-tenant behaviour runtime intelligence platform. Agents instrumented with the PUVINoise SDK emit OpenTelemetry traces and decision signals into a tenant-scoped control plane. Operators use Command Centre, behaviour intelligence, and Runtime Case workflows to observe, govern, and recover fleets — without building bespoke observability stacks for every agent. Documentation is refreshed with SDK and control-plane changes — check Changelog for public notes.
Documentation freshness
Stay current
OpenTelemetry & SDK
OTLP path and decision telemetry — keep linked from trust-sensitive reviews.
SDK docs →Architecture
Control plane flow for security and engineering reviewers.
Architecture →Reference: SDK environment & telemetry contract
From agent-sdk/README — required configuration and what the collector receives.
Configure the SDK from environment variables (for example a .env file). The SDK appends /v1/traces to the OTLP endpoint URL when missing. Resource attributes on every span include service.name (from PUVINOISE_AGENT_NAME), tenant.id (from PUVINOISE_TENANTID), and puvinoise.llm_provider (from CUST_LLM_PROVIDER). Agent.run spans carry agent.name, agent.run_id, tenant.id, and llm provider fields so the dashboard can filter by tenant, agent, and provider.
PUVINOISE_AGENT_NAME — agent/service name for resource attribution
PUVINOISE_TENANTID — tenant ID for multi-tenant isolation
PUVINOISE_API_KEY — agent access key (Bearer) for the OTLP endpoint
PUVINOISE_END_POINT_URL — OTLP collector base URL (e.g. http://host:4318)
CUST_LLM_PROVIDER — connected LLM provider (openai, anthropic, ollama, …)
Related resources
Continue from documentation
SDK
Install, quickstart, decision telemetry APIs, and migration notes.
SDK docs →Guides
Practical playbooks for instrumentation, verification, and operator handoff.
Read guides →Architecture & security
How ingest, tenancy, and behaviour intelligence fit together for reviewers.
View security →Need a walkthrough for your fleet?
Developer relations can review your runtime topology, tenancy model, and instrumentation plan.