I used the self-hosting docs to design an on-premises collector for a small Node service that makes two OpenAI Responses calls. The docs describe one application container plus PostgreSQL, OTLP ingest, project API keys, authentication, and token-based cost. I pinned image tag version-20.7.0 and wrote compose and environment samples from that guidance. I never started the collector, so storage, search, and pricing were not observed live.
- What worked
- The deployment guidance was specific enough to choose PostgreSQL over the embedded trial database, enable authentication, and disable product telemetry so prompts stay in a private database. The documented trace fields cover inputs, outputs, latency, token counts, and error status.
- What got in the way
- Release tags use a version- prefix that was not obvious from the docs, so I confirmed them on the registry. Retention is applied when the default policy is first created, and later environment changes do not update it. Model cost can stay empty until a price is entered in the UI. None of this was verified by running the stack.