--- title: Deploy Langfuse v4 on Render description: Use this guide to deploy Langfuse v4 at production scale on Render with a prebuilt Blueprint. label: "Version: v4" sidebarTitle: "Render" --- # Render 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](/self-hosting) for officially supported alternatives. You can deploy Langfuse v4 at production scale on [Render](https://render.com/) with a prebuilt Blueprint. The Blueprint creates separate Render resources for the Langfuse web service, worker, and each data store. See the [architecture overview](/self-hosting#architecture) for more details. ## Deploy Use the following button to deploy the Langfuse v4 Blueprint on Render: [![Deploy to Render](https://render.com/images/deploy-to-render-button.svg)](https://render.com/deploy-template/api/github/start?template_repo=langfuse4-template) 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](https://github.com/render-examples/langfuse4-template). ## Features Langfuse supports many configuration options and self-hosted features. For more details, see the [configuration guide](/self-hosting/configuration). - [Authentication & SSO](/self-hosting/security/authentication-and-sso) - [Automated Access Provisioning](/self-hosting/administration/automated-access-provisioning) - [Caching](/self-hosting/configuration/caching) - [Code evaluators](/self-hosting/configuration/code-evaluators) - [Custom Base Path](/self-hosting/configuration/custom-base-path) - [Encryption](/self-hosting/configuration/encryption) - [Headless Initialization](/self-hosting/administration/headless-initialization) - [Data Masking](/self-hosting/security/data-masking) - [Networking](/self-hosting/security/networking) - [Organization Creators (EE)](/self-hosting/administration/organization-creators) - [Instance Management API (EE)](/self-hosting/administration/instance-management-api) - [Health and Readiness Check](/self-hosting/configuration/health-readiness-endpoints) - [Observability via OpenTelemetry](/self-hosting/configuration/observability) - [Transactional Emails](/self-hosting/configuration/transactional-emails) - [UI Customization (EE)](/self-hosting/administration/ui-customization) --- If you experience any issues when self-hosting Langfuse, please: 1. Check out [Troubleshooting & FAQ](/self-hosting/troubleshooting-and-faq) page. 2. Use [Ask AI](/ask-ai) to get instant answers to your questions. 3. Ask the maintainers on [GitHub Discussions](/gh-support). 4. Create a bug report or feature request on [GitHub](/issues). Enterprise-grade support is available when self-hosting Langfuse. Learn more on our [pricing page](/pricing-self-host). --- ## Agent Instructions This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/self-hosting/deployment/render.md`. ### Querying these docs If the answer is not on this page, query the documentation instead of guessing: - **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question: ```bash curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?" ``` - **Index of every page**: , with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt). ### Before writing Langfuse code - **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results. - **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application. - **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples. - **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api `) to read or write traces, prompts, datasets, and scores from the terminal. Found an error in these docs? Please open an issue at .