SigNoz

Deploy SigNoz on a VPS in One Click

MonitoringDevOps, CI/CD & containers

Open-source observability platform for tracing requests, monitoring performance, and collecting logs across your services.

  • Ready in ~10 min
  • Free installation
  • We handle the setup
At a glance
Version
Latest (0.146)
Operating system
Ubuntu Server 24.04 LTS
Minimum RAM
4 GB
License
MIT
Addressing
IPv4, IPv6
GitHub
32,000
Deployment~10 min
Open source & self-hosted
VPS plans

Choose a VPS plan for SigNoz

Blazing-fast NVMe drives and powerful processors. Take a ready-made plan or build the configuration yourself.
Minex
Perfect for personal projects and small websites.
€3.20/mo
Save €0.80 per month

  • 1 vCPU core
  • 1 GB DDR5 RAM
  • 20 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • 1 TB traffic
Basex
A great balance of power and affordable price.
€4.80/mo
Save €1.20 per month

  • 2 vCPU cores
  • 2 GB DDR5 RAM
  • 40 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • 2 TB traffic
Most popular
Corex
For growing applications and businesses.
€7.20/mo
Save €1.80 per month

  • 4 vCPU cores
  • 4 GB DDR5 RAM
  • 50 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Midex
Resources for high-load projects.
€9.60/mo
Save €2.40 per month

  • 4 vCPU cores
  • 6 GB DDR5 RAM
  • 60 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Proex
Maximum power and scalability.
€12.00/mo
Save €3.00 per month

  • 6 vCPU cores
  • 8 GB DDR5 RAM
  • 70 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Scalex
Resources for scaling.
€16.00/mo
Save €4.00 per month

  • 6 vCPU cores
  • 10 GB DDR5 RAM
  • 150 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Maxex
A large reserve of power.
€44.00/mo
Save €11.00 per month

  • 8 vCPU cores
  • 16 GB DDR5 RAM
  • 200 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Apex
The top configuration.
€79.99/mo
Save €20.00 per month

  • 16 vCPU cores
  • 32 GB DDR5 RAM
  • 400 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic

What you can do with SigNoz

SigNoz is an open-source observability platform built on OpenTelemetry that unifies application performance monitoring, distributed tracing, log management, and metrics dashboards in a single interface. It's built for backend engineers, SRE teams, and DevOps engineers who need to trace a request across dozens of microservices instead of guessing which one caused a slowdown.

What sets SigNoz apart is that it speaks the same OpenTelemetry standard your instrumentation already uses, so traces, metrics, and logs land in one ClickHouse-backed store instead of three separate tools. Running SigNoz self hosted keeps that telemetry — request payloads, user identifiers, internal service names — on infrastructure you control, and a VPS for SigNoz means ingestion volume is bounded by your server rather than billed per gigabyte the way the managed cloud version charges.

The applications screen of the control panel with one-click install

SigNoz features

A server surrounded by app icons — applications running on a VPS

SigNoz ships as a multi-container stack — ClickHouse, an OTel Collector, and a query service — so a SigNoz VPS Docker deployment runs the same components behind SigNoz Cloud, not a stripped-down build. Here's what's included:

01

Distributed tracing

Follow a single request across every microservice it touches, down to individual spans and database calls.

02

Out-of-the-box RED metrics

Rate, error, and duration charts appear automatically for instrumented services without building dashboards by hand.

03

Log management

Collect and search structured logs in the same ClickHouse store as traces, using SQL-style queries.

04

Custom dashboards and alerts

Build panels from any combination of metrics, logs, and traces, and route alerts through Alertmanager.

05

Exception tracking

Capture unhandled errors with stack traces linked to the request that triggered them.

06

Service maps

Visualize how services call each other and where latency accumulates across the dependency graph.

07

LLM observability

Trace prompts, tokens, and latency for applications built on LLM APIs.

08

PromQL support

Query metrics with the same syntax used in Prometheus-based setups.

Requirements

Which server to run it on

Minimum requirements for SigNoz and the configuration worth starting with.
Minimum
  • CPU2 vCPU
  • Minimum RAM4 GB
  • Disk40 GB
Recommended
VPS Corex
  • CPU4 vCPU
  • Minimum RAM4 GB
  • Disk50 GB

Installation is free — you only pay for the server

Getting started

How to deploy SigNoz

Three steps and the app is running on your server.
Step 1
Choose a server

Pick a plan with at least 4 GB RAM — ClickHouse and the rest of the SigNoz installation stay resource-hungry even at idle.

Step 2
Pick the app

Choose SigNoz in the catalog to install SigNoz on VPS as a pre-configured Docker Compose stack, no manual container setup required.

Step 3
Get your credentials

Open the server address and complete the on-screen form to create the first admin account — SigNoz has no default password.

Why us

Why Host SigNoz on Leneex

Speed, protection and support you can rely on — on every plan, with no hidden limits.
Deployment speed
SigNoz's multi-container stack (ClickHouse, OTel Collector, query service) normally needs a careful startup sequence; one-click provisioning gets it running in minutes instead of debugging container order by hand.
Free installation
SigNoz Cloud starts metering usage the moment you cross the included credit; setting up the self-hosted stack at no installation cost means you skip that meter from day one.
DDoS protection
A SigNoz dashboard reachable on the open internet is a target worth attacking, since it holds request-level detail on your production services; DDoS protection keeps that surface stable under attack traffic.
Control and support
Root access lets you tune ClickHouse memory limits and retention windows directly instead of accepting whatever a managed plan allows, and engineers are reachable if a container in the stack won't come up.
99.9% uptime with SLA compensation
If SigNoz is your main window into production incidents, the monitoring tool going down alongside the thing it watches is the worst failure mode; the uptime SLA guards against exactly that.
Flexible payment
Hosting for SigNoz on a fixed-price VPS instead of usage-based cloud billing means a traffic spike that generates more traces doesn't also generate a bigger invoice — pay by card, crypto, or invoice for business accounts.
What to choose

SigNoz: Self-Hosted vs Cloud — Which to Choose

We compare cost, control over your data and limits, so the choice is an informed one.
SigNoz Cloud
Self-hosted on LeneexRecommended
Resources and limitsShared multi-tenant infrastructure, ingestion metered per GBDedicated CPU, RAM, and disk used only by your telemetry
Control and accessNo server access; retention and pipeline options limited to plan settingsRoot access; tune ClickHouse retention and sharding directly
Feature limitsEnterprise features like SAML SSO available on higher-tier plans without extra setupFull Community Edition feature set (SAML SSO/RBAC require Enterprise Edition either way)
ScalingScales automatically, but usage-based billing scales with itScale by resizing the VPS plan — CPU/RAM/disk upgrade on click
CostFrom $49/month base, then $0.30/GB for logs and traces, $0.10/million metric samples above the included creditFixed monthly VPS price regardless of trace/log volume
Who it fitsTeams that want zero ops overhead and whose telemetry volume stays within the included creditTeams with steady or high telemetry volume who want predictable costs and full data control

For teams already generating meaningful trace and log volume, SigNoz VPS hosting turns the cloud's per-gigabyte model into a flat monthly cost that doesn't grow with traffic spikes. Self-hosting also keeps request-level trace data — which can include payloads and internal service names — inside your own infrastructure. Teams that want to skip infrastructure management entirely, or whose telemetry volume comfortably fits the included cloud credit, are usually better served by the managed option.

Frequently Asked Questions about SigNoz on VPS

What people ask most about SigNoz and our servers.

  • ClickHouse data lives on the server's disk, so upgrading to a larger plan without touching the volume keeps trace and log history intact; moving to a different server means copying the ClickHouse data volume across.

  • If the new plan's disk can't hold the current trace and log history, older data may become unavailable until you clean it up or add storage — setting a retention window in SigNoz ahead of time keeps volume predictable.

  • The SigNoz one click install brings up the Docker Compose stack itself, but issuing an SSL certificate for the domain hosting the dashboard usually needs a reverse proxy step on top.

  • SigNoz's Community Edition doesn't license-cap the number of invited users — the practical limit is how many concurrent dashboard queries the server's CPU and ClickHouse can handle; a team of 5-10 engineers typically fits the minimum plan.

  • Once you deploy SigNoz in one click, updating the container images and running any ClickHouse schema migration stays your responsibility — Leneex keeps the VPS itself running, but you pull new versions through docker compose yourself.

What's already running

The one-click deployment brings up SigNoz as a multi-container Docker Compose stack: ClickHouse for trace, log, and metric storage, an OpenTelemetry Collector for ingestion, a query service, PostgreSQL for the metastore (accounts, dashboards, alert rules), and the frontend UI — all started and networked together automatically. Expect roughly 1.5-2 GB of RAM in use at idle before any telemetry even arrives, since ClickHouse and its supporting services stay resident in memory.

First login

Open the SigNoz dashboard at the address shown in your Leneex panel and you'll land on a setup screen asking you to create the admin account yourself — there's no default username or password, so whoever fills in this form first becomes the organization's first admin.

Sending telemetry

SigNoz's one click automation gets the backend running, but it doesn't instrument your applications for you: point your services' OpenTelemetry SDK or Collector at your server's OTLP endpoint (gRPC or HTTP) to start receiving traces, metrics, and logs. Once the first spans arrive, service maps and RED-metric dashboards populate automatically without extra configuration on your part.

Deploy SigNoz in about 10 minutes

Choose a server — we do the rest: install, configure and send you the credentials.