diff --git a/content/self-hosting/deployment/meta.json b/content/self-hosting/deployment/meta.json
index 90865198f..249e77067 100644
--- a/content/self-hosting/deployment/meta.json
+++ b/content/self-hosting/deployment/meta.json
@@ -6,6 +6,7 @@
     "aws",
     "azure",
     "gcp",
+    "render",
     "railway",
     "infrastructure"
   ]
diff --git a/content/self-hosting/deployment/render.mdx b/content/self-hosting/deployment/render.mdx
new file mode 100644
index 000000000..feee5dc4e
--- /dev/null
+++ b/content/self-hosting/deployment/render.mdx
@@ -0,0 +1,41 @@
+---
+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
+
+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?repo=https://github.com/render-examples/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).
+
+import SelfHostFeatures from "@/components-mdx/self-host-features.mdx";
+
+<SelfHostFeatures />
diff --git a/content/self-hosting/index.mdx b/content/self-hosting/index.mdx
index a9d53cb9b..763f1d54b 100644
--- a/content/self-hosting/index.mdx
+++ b/content/self-hosting/index.mdx
@@ -31,13 +31,14 @@ This is recommended for testing and low-scale deployments and lacks high-availab
 
 ### Production-scale deployments
 
-For production and high-availability deployments, we recommend one of the following options:
+For production-scale deployments, we recommend one of the following options:
 
 - [Kubernetes (Helm)](/self-hosting/deployment/kubernetes-helm)
 - [AWS (Terraform)](/self-hosting/deployment/aws)
 - [Azure (Terraform)](/self-hosting/deployment/azure)
 - [GCP (Terraform)](/self-hosting/deployment/gcp)
-- [Railway](/self-hosting/deployment/railway)
+- [Render](/self-hosting/deployment/render)
+- [Railway (v3)](/self-hosting/deployment/railway)
 
 ## Architecture