Some customers can't use your cloud. Now what?

Pydantic Logfire introduced a self-hosted option over a year ago to accommodate customers who cannot use cloud environments due to regulatory or architectural constraints. This decision required adapting the software to run on customer-managed Kubernetes clusters using Helm, a familiar tool for Kubernetes teams. The transition highlighted challenges, such as increased customer support due to configuration mismatches during upgrades and resource allocation issues leading to performance problems. To address these, Logfire implemented an audit tool to synchronize platform configurations with Helm charts and introduced sizing presets to optimize resource allocation. Additionally, the need for explicit boundaries and APIs for instance management became apparent, as customers now manage their own deployments. The experience underscored the importance of treating deployment configurations as integral components of the product to reduce support overhead.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.