Pydantic Logfire

I’d like to address a lot of the questions about self hosting: we do not currently have any way to self host, but we do plan on figuring that out eventually. Offering self hosting introduces challenges around updates, support, etc that we don’t want to slow us down while we refine the product to its initial state. We are cognizant of data restrictions and other factors that would require self hosting. That said, we don’t at this time plan on completely open sourcing the entire product. It would be more of a licensing setup. Of course this is all subject to change in the future based on feedback and product direction.

The most important thing is that you share with us WHY you want to self host. Is it compliance? What does that compliance mean (min/max data retention, right to be forgotten, data at rest needs to be geographically located or you have to own it, etc)? This will help us build the “right” kind of features in this area so that it works for you and your company.

> WHY you want to self host.

In my case, I am hesitate to add another cloud service in the Sub-Processor list to meet GDPR.

Actually, if it is an Otel wrapper, I don't think you don't need to offer self-hosting the server at all. Making easy to integrate with other Otel ecosystems would be enough.

> It would be more of a licensing setup.

At least this is much better than FOSS first than switching to a non-FOSS license like what happened to hashicorp and redis.

GDPR on our side too, we need to reduce subcontractors as much as possible to handle all the requirements you listed. Also, we have to renegotiate with our own customers every time we want to had a new subcontractor, so we avoid doing so at all costs.

I like the prefect.io approach to have the control plane on the external provider, with the data and workers being run on the customer infrastructure. It seems fair for both sides: - as the subcontractor, you keep trace of the real usage, without having to handle end user data which is a pain to manage, so you don't have to offer outrageous license pricing to compensate for being stolen (looking at you Grafana) . - as the company, you comply with gdpr, while alleviate the operating costs, and also supporting the companies providing the tooling you need.