Skip to main content

Fully Managed Prometheus
as a Service

Deploy Prometheus as a fully managed service starting at €9/mo. Get automated backups, SSL, updates, support and monitoring included.

Prometheus is the open-source monitoring and time-series database that started at SoundCloud in 2012 and became the second graduated project at the Cloud Native Computing Foundation — metrics collection, PromQL queries, alerting, and dashboards — combining the cost discipline and portability of self-hosted infrastructure with the production-grade reliability that engineering teams used to outsource at multiple times the price.

Free 7-day trial  99.9% Uptime SLA  No credit card  Cancel anytime

Free 7-day trial  99.9% Uptime SLA
No credit card  Cancel anytime

Prometheus

Prometheus

STARTING AT

€9/month
Automated Backups
Monitoring
Automated Updates
Auto SSL

USAGE

Unlimited
Human Support
Custom Domains
Terminal Access
File Manager Access
Deploy in your region 21 locations worldwide
GermanyFinlandNetherlandsUKSwedenUnited StatesCanadaSingaporeJapanAustraliaBrazilSouth Africa+9 more →
Prometheus Preview Image

ABOUT THE SOFTWARE

What is Prometheus

Prometheus is the open-source metrics monitoring system originally built at SoundCloud in 2012 and graduated by the Cloud Native Computing Foundation in August 2018. It pulls metrics from instrumented services, stores them in a local time-series database, and lets you query them in PromQL — the de facto monitoring standard for Kubernetes and microservice workloads.

Prometheus is licensed under Apache 2.0 with no single-vendor control. The 3.x series — the first major version in seven years — added UTF-8 metric and label names, native OpenTelemetry OTLP ingestion at /api/v1/otlp/v1/metrics, Remote Write 2.0 with roughly 60% smaller wire payloads, and a rewritten React user interface with PromLens-style query tree views.

The 2025 CNCF Annual Survey put Prometheus at 77% adoption among cloud-native organisations — the most-used non-orchestration CNCF project. Production deployments include SoundCloud (the origin), GitLab (bundled since version 8.16), Cloudflare, Uber, Shopify, Robinhood, and CoreOS / Red Hat. Storage on disk averages 1 to 2 bytes per sample after compression. Head memory follows a Robust Perception rule of thumb of roughly 3 KB per active time series. A 1-million-series instance therefore needs about 3 GB head RAM before query and page-cache overhead.

FEATURES

What Prometheus does

Prometheus collects metrics by scraping HTTP endpoints, stores them in a local time-series database, and lets you query them with PromQL — a functional query language built specifically for time-series math. It also handles alerting via Alertmanager, service discovery, recording rules, federation, and remote write to long-term storage backends.

Pull-based metrics scraping

HTTP scraping at intervals you control. Every instrumented service exposes a /metrics endpoint; Prometheus pulls on a schedule and stores the result locally. Default scrape interval is 15 seconds in the shipped prometheus.yml.

Local time-series database

A purpose-built TSDB on local disk. Roughly 1–2 bytes per sample compressed. 15-day retention by default; we tune to 30 days. Atomic writes via a write-ahead log for crash recovery.

Native service discovery

Built-in service discovery for Kubernetes, EC2, Azure, GCE, Consul, DNS, and twenty-plus other sources. Pod churn, autoscaling, and rolling deploys stop being a static-config problem.

Remote Write 2.0

Stream samples to a long-term storage backend (Thanos, Cortex, Mimir, VictoriaMetrics) while keeping local scraping authoritative. Remote Write 2.0 in 3.x reduced wire size by roughly 60% versus 1.0.

PromQL query language

A functional language built for time-series math. Aggregate by labels with sum by (service). Compute rates with rate(http_requests_total[5m]). Calculate percentiles from histograms with histogram_quantile().

Alertmanager integration

Alert rules evaluated inside Prometheus and sent to Alertmanager, which handles deduplication, grouping, silencing, and routing to PagerDuty, Opsgenie, Slack, email, or any webhook receiver.

Recording rules

Pre-compute expensive PromQL expressions on a schedule. Heavy dashboards stop hammering the raw series. Long retention queries become cheap. Burn-rate alerts stay accurate without query timeouts.

Native OpenTelemetry ingestion

Since 3.0, Prometheus accepts OTLP metrics directly at /api/v1/otlp/v1/metrics. Translation modes preserve dotted OTel names or convert them to underscores depending on downstream compatibility needs.

WHAT'S ALWAYS INCLUDED

Every app. Fully managed.
Nothing extra to pay for.

Every app you deploy includes the full managed service — security, backups, updates, and support from day one.

Automatic updates and patches

Apps run the latest stable version. Security patches applied silently, with rollback if needed.

Daily off-site backups

Multiple daily backups in redundant off-site locations. One-click restore if anything goes wrong.

24/7 uptime monitoring

Continuous monitoring with instant alerting. We respond before you notice.

SSL, firewall, DDoS protection

Auto-renewing SSL, hardened firewall rules, DDoS mitigation on every deployment.

Performance and scaling

We monitor resource usage continuously. When your app needs more headroom, we flag it and upgrade with your explicit approval.

Dedicated engineering support

Real engineers on chat. DNS, SMTP & migration help. All included in €9.

WHY MANAGED

Why teams pick managed Prometheus

In November 2025, Palo Alto Networks announced its $3.35 billion acquisition of Chronosphere — the Prometheus-native vendor that enterprises picked specifically to escape concentration with the proprietary observability incumbents. The deal closed January 2026. Buyers who chose Chronosphere on independence grounds are renegotiating in 2026 — and looking again at running Prometheus themselves, managed.

Running Prometheus in production means more than starting the binary. It means picking a retention window that won't lose you data when a customer asks for last quarter's uptime. Sizing memory for cardinality spikes that scale-down won't catch. Setting up a second replica because Prometheus has no native HA. Configuring Alertmanager clustering. Renewing TLS at the reverse proxy because Prometheus has no built-in identity layer. Watching the WAL. Cleaning the WAL when a compaction job dies because the disk hit retention.size first.

The gotcha that surprises most operators is restart time. A Prometheus instance with around four thousand WAL segments takes roughly three hours to replay on startup, at about three seconds per segment, and needs two to three times steady-state RAM during replay. One operator wrote up a December 2025 incident where the pod entered a restart loop because the Kubernetes startup probe timed out at fifteen minutes. The fix is operational, not architectural: alert on prometheus_tsdb_wal_corruptions_total and on the WAL segment count, raise the startup probe to match the actual replay shape, and over-provision replay RAM. We run that runbook so customers don't have to.

REVIEWS

Hear from customers ​like you​​​​​​​

Successful businesses and professionals around the world rely on DANIAN every day

USE CASES

Three teams who run Prometheus on DANIAN

These are representative team types we set up most often. Each starts with the same flat €9 plan.

12-PERSON SAAS ENGINEERING TEAM

Running 80 microservices on Kubernetes with 300k active series

The team scrapes about 200 targets across 80 microservices, holds 30 days of metrics locally, and federates older data to a long-term Thanos store. Region chosen for latency to the primary EKS cluster (Germany). Cardinality controlled by labeldrop on pod, pod_template_hash, and controller_revision_hash. Alerts route through Alertmanager to PagerDuty. Grafana datasource points at Prometheus directly so dashboards stay fast under burn-rate queries.

5-PERSON PLATFORM TEAM AT A PAYMENTS COMPANY

40 hosts with 90-day local retention and 12-month federated retention

Auth-failure rates and transaction-latency histograms route through a separate Alertmanager receiver to Opsgenie. Region pinned for data-locality reasons. Recording rules pre-aggregate sum by (service) (rate(http_requests_total[5m])) so dashboards never hit raw cardinality. Two Alertmanager replicas with --cluster.peer for deduplication. Remote write to a customer-owned Thanos receive endpoint handles the 12-month tail. Scrape interval at 30 seconds for cost discipline.

6-CLIENT OBSERVABILITY AGENCY

One Prometheus per client, region-pinned, tenant-labelled

Six client production stacks, each with their own Prometheus instance pinned to the client's preferred region. External labels carry tenant="<client>" for downstream routing. Authentication terminates at a reverse proxy because Prometheus has no native RBAC. Per-tenant Alertmanager configurations route to each client's incident channel (Slack, Teams, or email). A central Thanos Querier fans out across tenants for the agency's monthly usage reports.

COMPARISON

Four ways to run Prometheus

There are four common ways to run Prometheus in production: pay a proprietary observability vendor by the host, rent a production-class VPS and run it yourself, run it on your own hardware at home or in a small office, or have us manage it for €9 per month. The math turns out different than most teams expect.

 PATH1 HOST5 HOSTS 10 HOSTSYOUR TIME
Proprietary SaaS
Datadog Infrastructure Pro at $15/host/month annual
$15/mo$75/mo$150/moNone — but APM adds $31/host, custom metrics add $5/100, and logs bill separately. Scales linearly with hosts.
Self-host on a VPS
2 vCPU / 4 GB production-class VPS (~$24) + $5 object-storage backup + $15 monitoring
$44/mo$44/mo$44/mo1–4 hours / month at €60–120 per sysadmin hour = €60–280 effective. DB tuning adds at 25+ targets.
Home server
Synology DS923+ (~€650) amortised over 36 months + electricity + static-IP business internet + off-site backup
€100–200/mo€150–300/mo€200–400/mo2–4 hours / month. Plus a closet that can't be on a residential breaker, and a WAL replay that locks you out at 3am.
DANIAN Managed Prometheus€9/mo€9/mo€9/mo0 hours / month. Patching, monitoring, backups, and a human reply included.

The math is set up to be honest, not flattering. Datadog at one host looks competitive — until you add APM at $31 per host per month, custom metrics at $5 per hundred, and logs at $0.10 per gigabyte. A 50-engineer team running Datadog at full breadth crossed $220,000 per year in OneUptime's March 2026 cost breakdown.

The VPS path looks cheap if you don't price your time. A freelance sysadmin at €60–120 per hour priced for 1 to 2 hours a month puts the path between €100 and €280 per month effective — that is before the cardinality alert at 2am. The home-server path looks free until you price the static-IP business internet, the off-site backup target (a backup on the same machine isn't a backup), and the four-hour WAL replay when the box reboots. The €9 number on our row is flat because every cost component that scales with usage is bundled — the patching, the backups, the WAL monitoring, and the human at the other end of chat.

BY INDUSTRY

Prometheus for specific industries

Five industries account for most production Prometheus deployments on DANIAN. Each puts distinct demands on retention, scrape cadence, label hygiene, and alerting — and pulls a different configuration choice from the same binary. The industry list below varies per app; what Prometheus needs in payments is not what it needs in real-time gaming.

SaaS engineering teams operate against four-golden-signals discipline: latency, traffic, errors, and saturation, measured per service and aggregated at the customer-facing endpoint. A typical mid-market SaaS customer asks for 12 months of metric history to defend uptime claims, but 12 months at full cardinality is prohibitively expensive on a single Prometheus.

We tune retention.time to 30 days locally and remote_write older data to a Thanos receive endpoint customers own. Recording rules pre-aggregate the four-golden-signals queries so long-window rollups don't time out. Burn-rate alerts based on histogram_quantile over rate of *_bucket fire roughly 14 times faster than threshold alerts and miss far fewer real events.

Typical workload: 300k to 1M active series; 20–50 alerts per week; quarterly customer SLO reports pulled from recording-rule data.
Payments teams operate inside cardholder-data-environment isolation rules that drive observability decisions long before they drive metric labels. Twelve-month log retention floors are typical for the industry, with the most recent three months immediately queryable.

We pin Prometheus to a region that matches the customer's data-locality posture and tune retention.time to 90 days locally, with a remote_write to a customer-owned long-term store for the 12-month tail. Authentication failures and transaction-latency outliers route through a separate Alertmanager receiver — typically to a security on-call rather than the standard infra channel. Recording rules pre-aggregate latency histograms at 30-second resolution so dashboard load doesn't move overall ingestion rates around.

Typical workload: 1 to 5 million active series; security-skewed alert volume; quarterly audit pulls of historical alert and recording-rule data.
Health-tech operators run Prometheus for operational metrics only — patient identifiers, MRNs, and clinical data live in dedicated logging pipelines, never in time-series labels. The separation is the right one: Prometheus is the SLO and availability layer; the audit layer is somebody else's job, with different retention and different access controls.

We help customers configure metric_relabel_configs that strip any label name matching patient_id, mrn, encounter, or visit before storage. The /metrics scrape surface is locked down with TLS plus per-target authentication. Region pinning aligns to the customer's chosen data-locality posture.

Typical workload: 200k to 500k active series at deliberately tight cardinality; multi-year retention via remote_write to a customer-owned long-term store; alerts limited to genuine operational events, never patient-level activity.
E-commerce teams design their Prometheus around peak: Black Friday, Cyber Monday, or whichever Tuesday in November traffic hits 8 times the weekly baseline. Scrape interval drops from 30 seconds to 15 seconds during peak windows. Per-scrape sample_limit (we default to 50000) fails fast when a runaway exporter explodes the cardinality.

Cardinality head-room is pre-provisioned at 2 to 3 times the baseline so a viral product page doesn't OOM the head block. Recording rules at 30-second resolution feed capacity dashboards; synthetic checkout-funnel checks feed p95 SLOs at the 200-millisecond mark.

Typical workload: peak-day ingestion 5 to 10 times baseline; 500k to 2M active series; recording-rule cardinality dominates dashboard cost.
Game-server teams measure tick rate, matchmaker queue depth, and player-to-server RTT at percentile resolution most monitoring systems can't deliver. p99 latency under 50 milliseconds is the typical internal SLO for matchmaking and state replication.

We enable native histograms (stable in Prometheus 3.8+) so latency percentile queries don't lock you into a static bucket design at scrape time. Scrape interval drops to 10 seconds for matchmaking-critical services. Per-region Prometheus correlates tick-duration histograms with player RTT histograms; alerts fire on histogram_quantile(0.99, rate(game_tick_duration_bucket[1m])) > 0.05.

Typical workload: 500k to 2M active series multiplied by per-region and per-shard label dimensions; a sub-second p99 SLO that breaks if scrape cadence slips.

FAQ

Frequently asked questions

Everything teams ask before signing up — answered straight, without sales speak.

Three groups: technical setup, migration, and how DANIAN works as a service.

01

Technical and configuration

We run the current stable version. We upgrade on a customer-by-customer cadence with maintenance windows the customer picks. Major version changes are scheduled separately and pre-tested on staging instances.

02

Migration and onboarding

We can activate your app on your own custom domain/subdomain. Examples: mydomain.com, anyword.mydomain.com.
Or, on our randomized free subdomain. Example: 963.apps.danian.cloud
If you wish to use a custom domain/subdomain, select that option when ordering your app (or notify us later). We will send you the required DNS records and if needed, our tech team will modify them for you.
21 datacenter locations across six continents. You choose the region at provisioning. Application data sits in the region you choose; pick whichever is closest to your users or matches your data-residency preference.
Yes. Request a region migration from the dashboard and we run the move in the background. The system emails you when the migration completes; total transfer time depends on data volume but typical instances finish in a few hours. There is no extra charge for a region change.
Yes. Full data export is available at any time, in a portable format you can bring to any infrastructure.
Migration is rarely a hard cutover. Most teams run both stacks side by side for a quarter, instrument new services in Prometheus first, and turn off the proprietary vendor once dashboard parity and alert parity are confirmed. Common path: month 1 stand up Prometheus, month 2 port Grafana dashboards, month 3 port alerts to Alertmanager, month 4 cancel the proprietary contract.

03

Billing, support, and platform

€9 covers everything we do for that app: hardware in the region you choose, daily off-site backups with one-click restore, automatic security patches and version upgrades, 24/7 monitoring, SSL and firewall, and engineering support on Email/LiveChat. There are no setup fees or hidden line items. For more info see our Pricing page.
If you decide to continue, we charge €9/app/month from day 8. If you don't, the trial ends and you can export your data. No card is required for the trial, and we never auto-charge you without explicit consent.
No. The €9/month is flat regardless of how many users log into your app. Add 5 users or 50; the price doesn't change.
24/7 Live chat and email support, both staffed by engineers who run the systems. We handle DNS configuration, SMTP setup, app integrations, performance tuning, troubleshooting, and migration help. Response time is typically under an hour. There is no tier system — every customer gets the same support.
Yes. Cancel from the dashboard. We don't charge a cancellation fee, we don't lock data, and we will export your data to you on request before deletion. data to you on request before deletion.
Every customer instance is backed up daily to a separate region from the primary. We test restores. You can request a restore at any backup point within the retention window — usually 7 days for daily backups.
Your application data sits in the region you choose at provisioning — 21 datacenter locations across six continents. Account-level data (billing, account email, support ticket history) is processed centrally. Application data region is picked by you, per app.
99.9% uptime SLA on every app, every tenant. Service credits are documented at danian.co/service-level-agreement. The status page is located at status.danian.co.
When your tenant approaches the resource ceiling — the base tier holds 1 vCPU/RAM, 30 GB storage — we notify you. Resource upgrades happen with your explicit consent; we will not upgrade your tenant or charge you without it.
We wait. We don't suspend the app or delete your data on the first failed charge. We email you, you fix the card on file, and we continue.
Invoices can be downloaded from the billing dashboard in PDF the day each charge succeeds. EU VAT is added where applicable and the VAT-reverse-charge regime applies for VAT-registered businesses with a valid number.
150+ open-source apps across automation, team chat, file sync, analytics, AI, password management, email marketing, dev tools, project management, smart home, CMS, and federated social. See the full catalog →
Yes. Every instance comes with a web-based terminal and a file manager in your DANIAN management dashboard. Useful for managing your data and customizations.
Resources scale with your usage. If your app needs more vCPU, RAM, or storage, we add it — and we ask first before any change to your plan. €9 is the floor; resource-heavy workloads may price higher, but you'll always know in advance.
Yes. We have both a Partner program and an Affiliate program available. Anybody can sign up.
No contract. No minimum commitment. Cancel anytime from the dashboard with one click. The 7-day free trial requires no credit card. After the trial converts to paid, you can still cancel at any month without notice or penalty.

DEPLOY IN YOUR REGION

21 datacenter locations on six continents

Pick the region closest to your users.

United States, Germany, Finland, Singapore, Australia, Brazil, Canada, Netherlands, UK, Spain, Italy, France, Sweden, Malaysia, India, Japan, Mexico, Poland, South Korea, Chile, South Africa and more coming soon

Global Reach Map

Try managed Prometheus for 7 days

No card. Cancel from the dashboard.