Summary
On a self-hosted deployment, we noticed the daemon opens connections to https://www.braintrust.dev/
on the first event after a cold start. We initially suspected this was contributing to a startup
stall we were separately investigating — it isn't; the connection completes in under a second and
is not on the slow path. So this is not a performance bug report.
We're flagging it as a question because a self-hosted deployment reaching the public SaaS domain at
all was unexpected from a network/security-review standpoint (egress to a public destination outside
the deployment's own configured endpoint). Could you clarify what that connection is for (telemetry,
version check, license check, something else), and whether it's expected/documented behavior for
self-hosted installs?
Not part of this report
Any specific hang/timing bug — we've ruled this connection out as a cause of the daemon cold-start
issue tracked separately.
Summary
On a self-hosted deployment, we noticed the daemon opens connections to
https://www.braintrust.dev/on the first event after a cold start. We initially suspected this was contributing to a startup
stall we were separately investigating — it isn't; the connection completes in under a second and
is not on the slow path. So this is not a performance bug report.
We're flagging it as a question because a self-hosted deployment reaching the public SaaS domain at
all was unexpected from a network/security-review standpoint (egress to a public destination outside
the deployment's own configured endpoint). Could you clarify what that connection is for (telemetry,
version check, license check, something else), and whether it's expected/documented behavior for
self-hosted installs?
Not part of this report
Any specific hang/timing bug — we've ruled this connection out as a cause of the daemon cold-start
issue tracked separately.