Deploying to Render

This guide explains how to deploy SigNoz on Render using Foundry. Foundry generates a Render Blueprint (infrastructure-as-code YAML) from your configuration, which you then connect to your Render account.

Prerequisites

• A Render account.
• foundryctl: The Foundry CLI (see Step 1).
• A Git repository connected to Render (GitHub, GitLab, or Bitbucket). The generated Blueprint and configs will be committed and pushed so Render can deploy from the repo.

Step 1: Install foundryctl

Download and extract the foundryctl binary from GitHub Releases.

Linux:

curl -L "https://github.com/SigNoz/foundry/releases/latest/download/foundry_linux_$(uname -m | sed 's/x86_64/amd64/g' | sed 's/aarch64/arm64/g').tar.gz" -o foundry.tar.gz
tar -xzf foundry.tar.gz

macOS:

curl -L "https://github.com/SigNoz/foundry/releases/latest/download/foundry_darwin_$(uname -m | sed 's/x86_64/amd64/g' | sed 's/arm64/arm64/g').tar.gz" -o foundry.tar.gz
tar -xzf foundry.tar.gz

Windows (PowerShell):

$ARCH = if ($env:PROCESSOR_ARCHITECTURE -eq "ARM64") { "arm64" } else { "amd64" }
Invoke-WebRequest -Uri "https://github.com/SigNoz/foundry/releases/latest/download/foundry_windows_${ARCH}.tar.gz" -OutFile foundry.tar.gz -UseBasicParsing
tar -xzf foundry.tar.gz

After extracting, use foundryctl from the unpacked directory:

./foundry/bin/foundryctl <COMMAND> <OPTIONS>

Step 2: Create casting.yaml

Create a casting file that targets Render with flavor: blueprint and platform: render. Set metadata.name to a deployment name of your choice.

apiVersion: v1alpha1
metadata:
  name: <deployment-name>
spec:
  deployment:
    # blueprint generates Render's YAML format
    flavor: blueprint
    # render specifies Render.com
    platform: render

Verify these values:

• <deployment-name>: A unique identifier for your deployment (used in service naming)

Step 3: Generate the Blueprint (forge)

Run forge to generate the Render Blueprint and configuration files:

foundryctl forge -f casting.yaml

The generated files, including render.yaml, will be created in the pours/ directory. You can then deploy render.yaml to Render using Render's Infrastructure as Code.

Step 4: Deploy on Render

1. Commit and push the contents of pours/ (including render.yaml) to a Git repository that Render can access.
2. In the Render Dashboard, go to New Blueprint. Connect the repository and set the Blueprint file path to the generated file (e.g. pours/render.yaml).
3. Review the services and resources, then deploy the Blueprint.

For full details, see the Render Infrastructure as Code setup guide.

Render will provision and run the SigNoz services (SigNoz, ClickHouse, OTel Collector, etc.) as defined in the Blueprint. When deployment finishes, use the URL Render assigns to the SigNoz web service to access the UI.

Step 5: Verify

In the Render Dashboard, confirm that all services from the Blueprint are running. Open the SigNoz web service URL and check the health endpoint if needed:

curl -X GET https://<your-signoz-service>.onrender.com/api/v1/health

• Replace <your-signoz-service> with the actual hostname Render gives your SigNoz web service.

Next Steps

• OpenTelemetry Collection Agents
• Instrument your application
• Tutorials