Production incident triage
Work directly with Pydantic engineers to reproduce an issue, isolate the validation boundary, and identify a mitigation or fix.
Enterprise support for Pydantic
Pydantic often sits between untrusted data and the rest of a production system. When that boundary is critical, a public issue tracker is not the escalation path you want during an incident or a major upgrade.
Enterprise plans include direct access to Pydantic engineers, 24/7 priority support, setup assistance, and an SLA matched to your operating model. Your agreement can also define how we coordinate when a vulnerability affects a covered release line.
Discuss enterprise support Defined up front Know exactly how to escalate
Coverage, contacts, severity levels, and response times are agreed before production is under pressure.
- Covered software
- Pydantic, Pydantic Core, and agreed integrations
- Release lines
- The versions your production systems depend on
- Escalation path
- Named contacts and the agreed channel for urgent issues
- Initial response
- Severity levels and initial response times defined in your agreement
Use the public documentation, issue tracker, and community channels for ordinary questions. Enterprise support covers production incidents, major upgrades, architecture or performance reviews, and coordinated vulnerability response.
Upgrade and compatibility planning
Review changes to Python, Pydantic, pydantic-core, and important integrations before they reach a critical application.
Architecture and performance
Get maintainer guidance on schemas, validators, serialization, and high-throughput validation paths.
Coordinated vulnerability response
For confirmed issues affecting a covered release line, coordinate privately on impact, mitigations, patched releases, and disclosure.
-
Agree the support boundary
Define the packages, release lines, environments, operational and security contacts, and initial response targets covered by your agreement.
-
Prepare useful context
Map where Pydantic sits in critical paths and decide how to capture a reproducible example, relevant configuration, and recent changes.
-
Escalate directly
Bring production-impacting issues or suspected vulnerabilities to Pydantic engineers through the agreed private channel. We work with your team to isolate the behavior and determine the next action.
Pydantic’s license, documentation, releases, issue tracker, and community support remain open to everyone. Enterprise support adds a direct escalation path and contractual commitments for teams that depend on Pydantic in production.
Is this the same as Logfire support?
No. This page describes support for the Pydantic validation library. Logfire is a separate product with its own commercial plans and support.
What can Pydantic engineers help investigate?
We work with your engineers to reproduce the issue, isolate Pydantic behavior, explain the relevant implementation details, and determine the next action. Your team retains ownership of the surrounding application and infrastructure.
Can we agree specific versions and initial response targets?
Yes. Supported versions, severity levels, initial response targets, and other commitments are defined in your commercial agreement. Contact us to discuss your requirements.
How are security vulnerabilities handled?
Anyone can report a suspected vulnerability privately through Pydantic’s security reporting process. For confirmed issues affecting covered release lines, enterprise support adds named security contacts and coordinated work on impact assessment, mitigations, patched releases, and disclosure. Advisories and CVEs are published where appropriate; notification and response commitments are defined in your agreement.
- Review the Pydantic version policy.
- Plan an upgrade with the migration guide.
- Use the community help channels for questions that do not require a commercial support relationship.