Pydantic Logfire: Know more. Build faster.
From the team behind Pydantic Validation, Pydantic Logfire is an observability platform built on the same belief as our open-source library: that the most powerful tools can be easy to use.
What sets Logfire apart:
- Simple and Powerful: Logfire's dashboard is simple relative to the power it provides, ensuring your entire engineering team will actually use it.
- Python-centric Insights: From rich display of Python objects, to event-loop telemetry, to profiling Python code and database queries, Logfire gives you unparalleled visibility into your Python application's behavior.
- SQL: Query your data using standard SQL: all the control and (for many) nothing new to learn. Using SQL also means you can query your data with existing BI tools and database querying libraries.
- OpenTelemetry: Logfire is an opinionated wrapper around OpenTelemetry, allowing you to leverage existing tooling, infrastructure, and instrumentation for many common Python packages, and enabling support for virtually any language. We offer full support for all OpenTelemetry signals (traces, metrics and logs).
- Pydantic Integration: Understand the data flowing through your Pydantic Validation models and get built-in analytics on validations.
See the documentation for more information.
Evaluating observability tools? See what Logfire does for LLM apps and agents, evals in production, and how it compares to alternatives.
Feel free to report issues and ask any questions about Logfire in this repository!
This repo contains the Python SDK for logfire and documentation; the server application for recording and displaying data is closed source.
Using Logfire
This is a very brief overview of how to use Logfire, the documentation has much more detail.
Install
pip install logfire
Authenticate
logfire auth
Manual tracing
Here's a simple manual tracing (aka logging) example:
from datetime import date
import logfire
logfire.configure()
logfire.info('Hello, {name}!', name='world')
with logfire.span('Asking the user their {question}', question='age'):
user_input = input('How old are you [YYYY-mm-dd]? ')
dob = date.fromisoformat(user_input)
logfire.debug('{dob=} {age=!r}', dob=dob, age=date.today() - dob)
Integration
Or you can also avoid manual instrumentation and instead integrate with lots of popular packages, here's an example of integrating with FastAPI:
from fastapi import FastAPI
from pydantic import BaseModel
import logfire
app = FastAPI()
logfire.configure()
logfire.instrument_fastapi(app)
# next, instrument your database connector, http library etc. and add the logging handler
class User(BaseModel):
name: str
country_code: str
@app.post('/')
async def add_user(user: User):
# we would store the user here
return {'message': f'{user.name} added'}
Logfire gives you a view into how your code is running like this:
Contributing
We'd love anyone interested to contribute to the Logfire SDK and documentation, see the contributing guide.
Reporting a Security Vulnerability
See our security policy.
Logfire Open-Source and Closed-Source Boundaries
The Logfire SDKs (we also have them for TypeScript and Rust) are open source, and you can use them to export data to any OTel-compatible backend.
The Logfire platform (the UI and backend) is closed source. You can self-host it by purchasing an enterprise license.
5 maintainers
Release files for logfire 5.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| logfire-5.1.0.tar.gz | 1.4 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| logfire-5.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.8 MB
Release files / logfire-5.1.0.tar.gz
| Download URL | logfire-5.1.0.tar.gz |
|---|---|
| Size | 1.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
edf6c7d33c00214e11c2cdc567eb53051be36289747091e8bb910527e5970bea
|
|
BLAKE2b-256 checksum How to use checksums |
f9da0c73a4447dffe01e1737580556f5f061ffda8f85e46fbf35ac36f5b64d27
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / logfire-5.1.0-py3-none-any.whl
| Download URL | logfire-5.1.0-py3-none-any.whl |
|---|---|
| Size | 474.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c1d54eabf39f4c8f5e18e71f35da13375c8adb144c263f3076e650ba85929108
|
|
BLAKE2b-256 checksum How to use checksums |
cd02b32c3d5c298e4a9010694d261fb82c2c672747c0bf2b47bffda484aef349
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency log
