SigNoz: Open-Core alternative to Datadog in 2026
SigNoz unifies metrics, traces and logs in a single OpenTelemetry-based platform, as a direct replacement for Datadog/New Relic with your own data.
Core is open source, but advanced features or enterprise support may be behind a paid tier — check the license.
Audit Snapshot
View notes →License — Not verifiable on GitHub
GitHub — Active
Latest release — v0.145.0 · 8 days ago
Docker Compose — Official installer, no compose
Production — Not production-tested by AltFreeStack
SigNoz vs. Datadog
Pros
- The OpenTelemetry standard avoids locking you into a proprietary SDK
Things to consider
- ClickHouse adds operational complexity
Quick Docker installation guide
This tool doesn't install via a plain docker-compose.yml — it uses the project's own official installer. Review it before running it. See the full step-by-step guide →
💡 Official SaaS or self-hosted with AltFreeStack?
- On the official cloud: a recurring monthly fee and usage limits on Datadog.
- On your own VPS: the core is free to self-host on your own server — no more monthly SaaS fee, though some advanced features stay behind a paid plan.
# SigNoz recomienda su script oficial (levanta ClickHouse, el
# query-service y el frontend juntos con la configuración correcta):
git clone -b main https://github.com/SigNoz/signoz.git
cd signoz/deploy && ./install.sh
This docker-compose corresponds to an actively maintained project — last commit today.
This docker-compose not working for you? Report it on GitHub →Technical profile
- License
- MIT
- Category
- Monitoring, Logs & Errors
- Replaces
- Datadog, New Relic
- Tech stack
- GoClickHouseOpenTelemetry
Key features
- 100% built on OpenTelemetry (open standard)
- Metrics, traces and logs in one dashboard
- Configurable alerts
Preview
Public image provided by SigNoz on its own website.
🌐 Connect your domain with free SSL
Step 1 — Set up the DNS
In your domain registrar's dashboard (Cloudflare, Namecheap, GoDaddy...), create a record:
- Type
- A
- Name/Host
- @ (root domain) or a subdomain, e.g. app
- Content/Value
- Your server's public IP
Wait 5 to 15 minutes for the record to propagate across the internet.
Step 2 — Automatic reverse proxy with Caddy
One single file, no Nginx config or manual certificates — Caddy issues and renews Let's Encrypt HTTPS on its own.
Create a file called Caddyfile:
yourdomain.com {
reverse_proxy localhost:YOUR_APP_PORT
}Start Caddy with this command (pulls the image and runs it in the background):
docker run -d -p 80:80 -p 443:443 --name caddy --restart always -v $PWD/Caddyfile:/etc/caddy/Caddyfile -v caddy_data:/data caddy