Vannus / Catalog / Pydantic Logfire

Pydantic Logfire

This entry runs no foundation model. Every finding below is quoted to the vendor’s own document, or marked not disclosed where the vendor publishes nothing.

Application monitoring overlay for Pydantic — tracks successful and failed validations in production, revealing where external inputs fail to meet the system's internal contracts

DevOps, AI
Model provenance

No foundation model. Pydantic Logfire does not run one, so there is no model provenance to record. An OpenTelemetry-based observability platform that records traces, metrics and logs from applications - including instrumenting LLM and agent calls - but performs no inference and serves no model of its own. Established from the product’s own public documentation and what it does. If that is out of date, tell us at right of reply.

Who controls it

Not yet assessed. We publish a sovereignty position only where the vendor documents one — we do not infer it from a domain or a company name.

Who else handles your data

Pydantic Logfire publishes a list of the other companies it uses as sub-processors. It lists 15 entries. Each is shown below with the location the vendor lists it under, in the vendor’s own words.

Amazon Web Services · United States & European UnionClay, Inc. · United StatesCloudflare, Inc. · United StatesCustomer.io, Inc. · European UnionDay AI, Inc. · United StatesGoogle Cloud Platform · United States & European UnionGoogle LLC · United StatesMetronome Holdings Inc. · United StatesGoogle Cloud Platform (Vertex AI) · European UnionOpenAI · United StatesPagerDuty, Inc. · European UnionPostHog Inc. · European UnionPylon, Inc. · United StatesSlack Technologies, LLC · United StatesStripe, Inc. · United States

Taken together those entries name at least European Union, United States. That is what our place list could match in the vendor’s own words above, so treat it as a floor rather than the whole of it — the entries themselves are the record.

These are other companies, not Pydantic Logfire. Where a sub-processor is listed as operating is a fact about that company. It is not a statement about where Pydantic Logfire keeps your data, which Vannus publishes separately and only from a document in which the vendor says so.

Read from pydantic.dev on 2026-09-16, from the page the vendor titles “Logfire Cloud Subprocessors | Pydantic”. Every entry above is a verbatim span of that page.

This is the vendor’s own disclosure, reproduced. Vannus has not audited what any of these companies do with your data, and a list can change without notice. Treat it as a starting point for your own review, not a legal determination, and take advice on anything that matters.

How this entry is set

Vannus records, from the vendor's own published documents, the legal entity a customer contracts with, the country that entity sits in, and the governing law of its terms — and whether the vendor runs its own model or resells someone else's. Each finding is quoted to its source and dated, or marked not disclosed where the vendor publishes nothing. No paid placement on a record, in the catalog or in search — affiliate status is walled off from the record, enforced by a test in the build. See the methodology →

Related tools we record
Visit Pydantic Logfire ↗ Check your whole stack →
Vannus (PRAXIS AI LLC) · entry as of the latest catalog build · all 376 tools · MCP for assistants
Work here and think we got something wrong? Corrections and right of reply → — free, no account, and we publish your response next to our entry.