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.

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.

1. Agree the support boundary

   Define the packages, release lines, environments, operational and security contacts, and initial response targets covered by your agreement.

2. Prepare useful context

   Map where Pydantic sits in critical paths and decide how to capture a reproducible example, relevant configuration, and recent changes.

3. 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.

No. This page describes support for the Pydantic validation library. Logfire is a separate product with its own commercial plans and support.

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.

Yes. Supported versions, severity levels, initial response targets, and other commitments are defined in your commercial agreement. Contact us to discuss your requirements.

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.