official minimum CPU and memory specs for the Langfuse web and worker pods on Kubernetes

[divyanshbasys]

Describe your question

What are the official minimum CPU and memory specs for the Langfuse web and worker pods on Kubernetes (e.g. Fargate), especially for v3.161+?

We saw CrashLoopBackOff with 0.25 vCPU / 0.5Gi on v3.161.0; v3.137.0 ran fine on the same limits.
Does your scaling guide apply to v3.161+, and is there an explicit “minimum” for dev/staging?

Langfuse Cloud or Self-Hosted?

Self-Hosted

If Self-Hosted

No response

If Langfuse Cloud

No response

SDK and integration versions

No response

Pre-Submission Checklist

• I have checked for existing issues/discussions and consulted Langfuse AI.

[inkeep-ai-assistant[bot]]

The official minimum infrastructure requirements for Langfuse v3 are:

• Langfuse Web Container: 2 CPU, 4 GiB Memory (1)
• Langfuse Worker Container: 2 CPU, 4 GiB Memory (1)

Your configuration of 0.25 vCPU / 0.5Gi is significantly below these minimums, which explains the CrashLoopBackOff behavior. The scaling guide does apply to v3.161+. (1)

For production environments, the Helm chart documentation recommends these resource settings in your values.yaml:

langfuse:
  resources:
    limits:
      cpu: "2"
      memory: "4Gi"
    requests:
      cpu: "2"
      memory: "4Gi"

(2)

There isn't an explicitly documented "minimum for dev/staging" that's lower than the production requirements. The 2 CPU / 4 GiB Memory specification represents the baseline for stable operation. If v3.137.0 worked on smaller resources, it may have been running at the edge of stability, and subsequent versions may have slightly higher baseline requirements due to new features or dependencies.

📚 Sources:

1. Scaling
2. Kubernetes (Helm) (self-hosted) - Langfuse

---

Have another question? Just tag @inkeep.

[divyanshbasys]

If i am just running it for local development , then what should be specs ? as right now i am not building it for production level