lite-bootstrap wires production observability (OpenTelemetry, Prometheus, Sentry, and structlog) into FastAPI, Litestar, FastStream, and FastMCP services in a few lines.

With lite-bootstrap, you receive an application with lightweight built-in support for:

• sentry
• prometheus
• opentelemetry
• pyroscope, with OpenTelemetry trace-profile linking
• structlog
• cors
• swagger, including an offline version
• health-checks

Those instruments can be bootstrapped for:

• Litestar
• FastStream
• FastAPI
• FastMCP
• services and scripts without frameworks

Lifecycle constraints

A few constraints that aren't obvious from the API:

• One bootstrapper per application instance. Constructing two FastAPIBootstrappers around the same fastapi.FastAPI (or two FastMcpBootstrappers around the same FastMCP) is not supported. The second bootstrapper warns at construction, and its bootstrap() raises ConfigurationError.
• One OpenTelemetryInstrument per process. bootstrap() calls opentelemetry.trace.set_tracer_provider(...), which the OTel SDK enforces as set-once: later calls log a warning and have no effect. teardown() flushes spans and closes exporters but can't reset the process-global pointer.
• teardown() is idempotent. BaseBootstrapper.teardown() short-circuits if not bootstrapped; per-instrument teardown methods are safe to call multiple times.
• Partial teardown failures are aggregated. If an instrument's teardown raises, the bootstrapper continues with the rest of the instruments and raises TeardownError at the end with all collected failures.

---

Usage examples:

• with Litestar: litestar-sqlalchemy-template
• with FastAPI: fastapi-sqlalchemy-template

Acknowledgements

lite-bootstrap is inspired by microbootstrap, a single package that wires up the common observability stack (sentry, prometheus, opentelemetry, logging, cors, swagger, health-checks) for FastAPI / Litestar / FastStream services and for plain scripts.

The following ideas were borrowed:

• the overall surface: a Bootstrapper per framework that composes a set of instruments,
• the lifecycle model: each instrument has bootstrap() / teardown() / is_ready() and is skipped when its optional dependency is not installed,
• the catalog of supported instruments and supported frameworks.

The following intentionally differ:

• Configuration. lite-bootstrap uses frozen dataclass configs with no pydantic / pydantic-settings runtime dependency, which is what makes it "lite". microbootstrap configures everything through pydantic-settings models.
• Extras. lite-bootstrap has one mandatory runtime dependency, the pure-Python typing-extensions. Every instrument (sentry, otl, logging, pyroscope) and every framework (fastapi, litestar, faststream, fastmcp) is its own extra, plus an opt-in orjson speedup for logging, per-pair combos (fastapi-sentry, litestar-otl, faststream-metrics, …) and *-all rollups. microbootstrap bundles the full observability stack (opentelemetry, sentry-sdk, structlog, pyroscope-io, rich, pydantic-settings, …) as base dependencies and only splits framework packages into extras.
• Free-threading. lite-bootstrap runs on free-threaded CPython 3.14t. Every extra whose dependencies are pure Python installs there. The rest are blocked upstream: orjson and pyroscope have no free-threaded wheels, and otl needs grpcio, so use otl-http instead.
• Scope. lite-bootstrap only wires instruments. It does not include a Granian server runner or a console writer.

Links

• Documentation
• PyPI
• License

Part of modern-python

Browse the full list of templates and libraries in modern-python; the org profile has the categorized index.