Rate Limit on self-hosted webapp

[aumeshm]

Is there a way to set rate limiting on self-hosted langfuse? I do not see any rate-limit headers in the response headers. Sometimes is required for compliance.

[inkeep-ai-assistant[bot]]

Based on the available documentation, there is no specific configuration option mentioned for setting rate limiting on self-hosted Langfuse instances (1)(2)(3)(4). The self-hosting documentation covers deployment options, scaling, and infrastructure requirements but doesn't include rate limiting configuration settings.

The rate limiting that occurs in self-hosted Langfuse typically comes from external LLM providers (like OpenAI, Anthropic, etc.) rather than Langfuse itself (5). When using features like LLM-as-a-Judge evaluations, rate limits are imposed by the external API providers, not by the Langfuse application.

For production-scale deployments, the documentation focuses on scaling strategies like adding more worker containers and optimizing throughput rather than implementing rate limiting (3). The recommended approach is to scale instances when CPU utilization exceeds 50% and use multiple containers for high availability (4).

If you need to implement rate limiting for your self-hosted instance, you would likely need to configure this at the reverse proxy or load balancer level in front of your Langfuse deployment, as this functionality isn't built into the Langfuse application itself based on the available documentation.

📚 Sources:

1. Self-host Langfuse
2. Troubleshooting & FAQ
3. Scaling
4. Application Containers (self-hosted) - Langfuse
5. rate limit issue when calling evalution in aws self hosted environment.

---

Have another question? Just tag @inkeep.

[Steffen911]

@aumeshm Currently, the rate limit behaviour within the Langfuse service is only active for Langfuse cloud and cannot be enabled on self-hosted deployments.
Instead, we recommend to use rate limit functionality of loadbalancers or proxies for self-hosted deployments.