本页还没有译文
本页 15 段还没译成한국어，下面显示的是英文原文。Deploy Langfuse v4 on Render
还没翻译译自英文（langfuse.com）本页 15 段都还没译
Render
Community-supported deployment
This deployment path is built on a template that is maintained outside the Langfuse organization. We do not systematically test it, support is best-effort, and fixes often depend on community contributions. See the self-hosting overview for officially supported alternatives.
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.
Authentication & SSO Automated Access Provisioning Caching Code evaluators Halo Custom Base Path Encryption Headless Initialization Data Masking Networking Organization Creators (EE) Instance Management API (EE) Health and Readiness Check Observability via OpenTelemetry Transactional Emails UI Customization (EE)