LIVEReading: Run Your Own Datadog Alternative Free with SigNozTotal time: 8 minSteps: 5Worked first time: 72% LIVEReading: Run Your Own Datadog Alternative Free with SigNozTotal time: 8 minSteps: 5Worked first time: 72%
CBW
Run Your Own Datadog Alternative Free with SigNoz
Mediumgithub.com/SigNoz/signoz2026-06-26

Run Your Own Datadog Alternative Free with SigNoz

SigNoz gives you logs, metrics, and traces in one dashboard — no Datadog bill. This guide gets it running locally with Docker in under 15 minutes.

// Build stats

  • Total time8 min
  • Number of steps5
  • DifficultyMedium
  • Worked first time72%
// Before you start

What you need

  • Docker Desktop installed and running (docker.com/products/docker-desktop)
  • Docker Compose included (comes with Docker Desktop)
  • At least 4 GB RAM free for Docker
  • A terminal / command prompt (Mac Terminal, Windows PowerShell, or Linux shell)
  • Internet connection to pull images (~1.5 GB download)
01
Step 1 of 5

Clone the SigNoz repository

2 min

This downloads the official SigNoz project files to your computer. The folder contains the Docker Compose file that wires together all the services SigNoz needs — the UI, the database (ClickHouse), the collector, and more. You are not writing any code; you are just grabbing the files.

Terminal · mac
$ git clone -b main https://github.com/SigNoz/signoz.git && cd signoz
What you should see
Cloning into 'signoz'... done. Your terminal prompt should now show you are inside the signoz folder.
This might happen

git: command not found

Install Git from git-scm.com, then re-run the command.

02
Step 2 of 5

Start SigNoz with Docker Compose

8 min

This single command reads the Compose file and pulls all the Docker images SigNoz needs, then starts every service automatically. The first run is slow because it downloads roughly 1–1.5 GB of images. Subsequent starts are fast. The -d flag runs everything in the background so your terminal stays free.

Terminal · mac
$ cd deploy && docker compose -f docker/clickhouse-setup/docker-compose.yaml up -d
What you should see
You will see lines like 'Pulling signoz...', 'Pulling clickhouse...', then 'Container signoz-frontend Started'. When it finishes, run: docker compose -f docker/clickhouse-setup/docker-compose.yaml ps — all services should show status 'Up' or 'running'.
This might happen

Error: port 3301 or 8080 already in use

Another app is using that port. Stop it, or edit the port numbers in docker/clickhouse-setup/docker-compose.yaml before running the command again.

03
Step 3 of 5

Open the SigNoz dashboard

1 min

Once all containers are running, the web UI is available in your browser. The first time you visit, SigNoz will ask you to create an admin account. Fill in your name, email, and a password — this is just a local account stored on your machine.

Terminal · mac
$ open http://localhost:3301
What you should see
A SigNoz signup/login page loads in your browser. After creating your account you land on the main dashboard showing Services, Traces, Logs, and Metrics tabs.
This might happen

Page does not load or shows 'connection refused'

The containers may still be starting. Wait 60 seconds and refresh. Run 'docker compose -f docker/clickhouse-setup/docker-compose.yaml ps' to confirm all services show 'Up'.

04
Step 4 of 5

Verify sample data is flowing

2 min

SigNoz ships with a sample HotROD application that generates real traces so you can explore the UI immediately without connecting your own app. Check that it is running and sending data.

Terminal · mac
$ docker compose -f docker/clickhouse-setup/docker-compose.yaml ps hotrod
What you should see
A row showing 'hotrod' with status 'Up'. In the SigNoz browser UI, click 'Services' — you should see a service called 'frontend' or 'hotrod' with live metrics within 1–2 minutes.
This might happen

hotrod service is not listed or shows 'Exit'

It may have been removed in newer releases. The main SigNoz UI still works; you just won't see demo data until you connect a real app.

05
Step 5 of 5

Stop SigNoz when you are done

1 min

SigNoz runs in the background and uses CPU and RAM. When you are not using it, shut it down cleanly with this command. Your data is saved in Docker volumes, so it will still be there next time you start it up.

Terminal · mac
$ docker compose -f docker/clickhouse-setup/docker-compose.yaml down
What you should see
Lines like 'Container signoz-frontend Stopped' for each service. Docker Desktop will show no running containers for this project.
// Status

cooked. baked. worked.

A fully working SigNoz observability dashboard running on your own machine at localhost:3301, showing logs, metrics, and traces tabs, with sample HotROD service data visible so you can explore the UI before connecting any real application.

// the honest bit

The honest part

SigNoz is a serious infrastructure tool, not a weekend toy. The Docker install is genuinely easy, but connecting your own application requires adding OpenTelemetry SDK code to that app — that part does involve editing code in your project. The self-hosted version also needs ongoing maintenance (disk space for ClickHouse, Docker updates). For a no-maintenance option, SigNoz offers a free-tier cloud version at signoz.io. Minimum 4 GB RAM is a real requirement; it will struggle on machines with less. Windows users may need WSL2 enabled for Docker to work properly.