Render

You can deploy Langfuse v4 at production scale on Render with a prebuilt Blueprint. The Blueprint creates separate Render resources for the Langfuse web service, worker, and each data store. See the architecture overview for more details.

Deploy

Use the following button to deploy the Langfuse v4 Blueprint on Render:

Before you apply the Blueprint, review the service plans, disk sizes, and estimated cost. Render creates these resources:

• Langfuse v4 web and worker services
• A managed PostgreSQL 18 database
• A managed Render Key Value instance
• A private ClickHouse service with a persistent disk
• A public MinIO service with a persistent disk

Select service plans and disk sizes that match your expected workload. Configure backups and recovery procedures before you send production traffic.

MinIO has a public endpoint because Langfuse sends presigned media URLs to browsers and SDK clients. MinIO still requires signed requests.

For more details, see the Blueprint repository.

Features

Langfuse supports many configuration options and self-hosted features. For more details, see the configuration guide.

If you experience any issues when self-hosting Langfuse, please:

1. Check out Troubleshooting & FAQ page.
2. Use Ask AI to get instant answers to your questions.
3. Ask the maintainers on GitHub Discussions.
4. Create a bug report or feature request on GitHub.

---

---