• Docs
  • Changelog
Sign in
Get started
    • Home
    • Your first deploy
    • Free instances
    • Platform features by plan
    • Use with coding agents
    • FAQ
    • Templates
      • Migrate from…
        • Heroku
        • Railway
    • Compute plans
    • SandboxesBeta
      • Service types
        • Which to use?
        • Static sites
        • Web services
        • Private services
        • Background workers
        • Cron jobs
        • Workflows
        • Multi-service architectures
      • Data storage
        • Render Postgres
        • Render Key Value (Redis®-compatible)
        • Persistent disks
    • How deploys work
    • Supported languages
    • Git providers (GitHub, etc.)
    • Build pipeline
    • Deploy hooks
    • Monorepo support
    • Troubleshooting deploys
      • Previewing changes
        • Single-service previews
        • Preview environments (multi-service)
      • Docker deploys
        • Overview
        • Deploy a registered image
        • Using secrets
      • Runtime
        • Native runtimes
        • Environment variables & secrets
        • Default environment variables
    • Intro to sandboxes
    • Limits
      • How to…
        • Create & configure sandboxes
        • Execute commands
        • Manage files
        • Manage snapshots
      • Use with…
        • Claude Managed Agents
        • Cursor Cloud Agents
        • OpenAI Agents API
      • SDK/CLI reference
        • TypeScript SDK
        • Python SDK
        • CLI commands
    • Intro to workflows
    • Tutorial
    • Limits & pricing
      • How to…
        • Define tasks
        • Define flowsNew
        • Trigger runs
        • Develop locally
      • SDK reference
        • TypeScript SDK
        • Python SDK
      • Example workflows
        • TypeScript examples
        • Python examples
    • Overview
    • Create & connect
    • Database credentials
    • Extensions
    • Version upgrades
    • Logical replication
    • Legacy instance types
      • Database recovery
        • Recovery & backups
        • High availability
      • Database performance
        • Read replicas
        • Connection pooling
        • Admin apps
        • Repacking tables
        • Troubleshooting performance
    • Regions
    • Inbound IP rules
    • Edge caching
    • WebSockets
    • TLS certificates
      • Custom domains
        • Overview
        • Cloudflare
        • Namecheap
        • Other DNS providers
      • Internal traffic
        • Private network
        • Private links
      • Outbound traffic
        • Default IP ranges
        • Dedicated IP addresses
        • Outbound bandwidth
        • Handling network changes
      • Static site config
        • Custom response headers
        • Redirects & rewrites
    • The Render Dashboard
    • SSH / Shell access
    • Projects & environments
      • Service actions
        • Scaling
        • Rollbacks
        • Maintenance mode
        • One-off jobs
      • Infrastructure as code
        • Blueprints overview
        • render.yaml reference
        • Terraform provider
    • In-dashboard metrics
    • Health checks
    • Uptime best practices
      • Logging
        • In-dashboard logs
        • Log streams (syslog/HTTPS)
      • OpenTelemetry (OTel) metrics
        • Provider setup
        • Metrics reference
      • Notifications
        • Webhooks
        • Email / Slack
    • MCP Server
      • Render CLI
        • Overview
        • Command reference
      • REST API
        • Overview
        • API reference
      • Third-party connections
        • OIDC support
        • Datadog
    • Workspaces, members, & roles
    • Login settings
    • Audit logs
      • Organizations
        • Overview
        • SAML SSO
    • DDoS protection
    • Platform maintenance
      • Compliance
        • Overview
        • HIPAA (US health data)
        • HIPAA best practices
        • Shared responsibility model
        • Pentest policy
    • Heroku vs Render
    • Vercel vs Render

Deploy ClickHouse

ClickHouse is a column-oriented OLAP database system that allows generating analytical reports in real-time using SQL queries. ClickHouse strives to maximize hardware efficiency and is capable of processing typical analytical queries two to three orders of magnitude faster than traditional row-oriented systems. It also supports multi-master asynchronous replication where all nodes are equal, which prevents single points of failure. You can run your own ClickHouse instance as a private service on Render backed by high performance SSDs with automatic daily snapshots.

We'll be deploying ClickHouse using the latest official Docker image and the Render ClickHouse repository to install ClickHouse with a single click.


One-Click Deploy

Click Deploy to Render below and follow the prompts to deploy ClickHouse on Render.

Deploy to Render

Manual Deploy

  1. Create a new Private Service on Render and enter https://github.com/render-examples/clickhouse in the repository search box. You can also fork the repository on GitHub or click Use this template.

  2. Set the Language field to Docker.

  3. Be sure to choose the 1c-2g compute plan or higher. ClickHouse might exhaust memory limits on smaller compute plans.

  4. The master branch uses the latest stable version of ClickHouse. You can choose a different branch if you'd like to use a specific ClickHouse version.

  5. Under Advanced, add a disk with the following values:

    Mount Path/data/db
    Size10 GB Feel free to change this to suit your needs.

You're all set! Save your private service, and your ClickHouse instance should be up in a few minutes.

Connecting to ClickHouse

You should be able to connect to your ClickHouse instance using host:port values displayed in the dashboard like clickhouse-xyz:8123 (port 9009 is internal and used for replication). Consult ClickHouse documentation on interfaces for more details.

InterfaceDescription
clickhouse:8123HTTP interface
clickhouse:9000Native interface for driver libraries and clickhouse-client application
clickhouse:9004MySQL wire protocol

You can also use the shell in your dashboard to connect to your database.

ClickHouse Shell on Render

Backups

Relying on a disk snapshot to restore a database is not recommended. Restoring a disk snapshot will likely result in corrupted or lost database data.

Using a database’s recommended backup tool (for example: clickhouse-copier) is the recommended way to backup and restore a database without corrupted or lost data.

Deploy ClickHouse
  • One-Click Deploy
  • Manual Deploy
  • Connecting to ClickHouse
  • Backups
All Systems Operational
© Render Inc. All rights reserved.