the phone-home register
Strata
What Strata sends out of your computer by default, when, to whom, and the switch that stops it, version by version, with how we know.
The answer
We found no call out of Strata's own in its code at commit 8fc40dde, read with its network clients enumerated: it fetches only what a request or your configuration names (an image URL in a request, the MCP servers you configure, the files its setup script downloads when you run it), and the one lookup it makes on its own, of its host name, happens only when you bind the server beyond the loopback address and goes to your resolver; we did not run it.
Builds and versions
not installed: source read at commit 8fc40ddeOn by default?none found · code read at 8fc40ddeMeasured here?no · read in codeDate checked (UTC)2026-10-10
- Version
- 8fc40dde · the source at commit 8fc40dde (its setup names engine v0.1.25; the tag v0.1.25 now names a rewritten commit)
- Where the evidence came from
- not run: the source applies to every platform it builds
- On by default?
- none found · code read at 8fc40dde: no call on its own; it fetches only what a request or your configuration names
- Measured here?
- no · read in code
- Date checked (UTC)
- 2026-10-10
- Why we say so
- every network client call enumerated at 8fc40dde (Python requests, httpx, urllib, aiohttp, socket, grpc, websockets, huggingface_hub downloads; JS fetch, XMLHttpRequest, net, https, dgram, WebSocket, axios); each hit read: the setup script's downloads, image URLs named in a request, MCP servers you configure, and the bundled chat client talking to the local server. The repository's history was later rewritten: the tag v0.1.25 now names commit d4e04766.
Each call out
No call found · 8fc40dde
- Version · build
- 8fc40dde · the source at commit 8fc40dde (its setup names engine v0.1.25; the tag v0.1.25 now names a rewritten commit) · not run: the source applies to every platform it builds · not installed: source read at commit 8fc40dde
- Sends by default
- none found · code read at 8fc40dde: no call on its own; it fetches only what a request or your configuration names
- Also know
- When started bound to an address beyond loopback, the server looks up its own host name to print the addresses other devices can use; that lookup goes to your resolver, not to a vendor. — github.com · server.py, read 2026-10-10
Its setup script downloads the files it needs when you run it. — github.com · setup.py, read 2026-10-10 - Grade and method
- read · every network client call enumerated at 8fc40dde (Python requests, httpx, urllib, aiohttp, socket, grpc, websockets, huggingface_hub downloads; JS fetch, XMLHttpRequest, net, https, dgram, WebSocket, axios); each hit read: the setup script's downloads, image URLs named in a request, MCP servers you configure, and the bundled chat client talking to the local server. The repository's history was later rewritten: the tag v0.1.25 now names commit d4e04766. · read 2026-10-10
- Receipts
- the server's default host · an image URL named in a request is fetched · the own-name lookup, only when bound beyond loopback
The switch
No switch found.
Listens beyond the machine, and other cloud features
Listens beyond the machine by default
- loopback only · its server's default host is the loopback address (serve/server.py at 8fc40dde) (8fc40dde the source at commit 8fc40dde (its setup names engine v0.1.25; the tag v0.1.25 now names a rewritten commit))
Other cloud features
None found.
What it leaves on disk
Nothing we know of.
Brings in, and installed for you by
None on the register.
Vendor documents it? · public discussion
Vendor documents it?
No call to document.
Public discussion
History
No dated changes yet.
Not yet checked
Nothing named.