Prometheus
Metrics monitoring and time-series database for instrumented services and infrastructure.
3 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Run official server binaries or the documented Prometheus container with persistent storage and a configured scrape file.
Runs in
Documented customer environment
Customer-operated metrics server and local time-series storage, with optional Alertmanager and exporters
- AWS: Customer cloud account
- AWS
Servers / containers
Operated by
Your team
Customer manages scrape targets, storage retention, alerting, access controls, exporters, backups and upgrades.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Self-managed Prometheus in an EKS monitoring stack ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Run official server binaries or the documented Prometheus container with persistent storage and a configured scrape file. |
|---|---|
| Infrastructure | Servers / containers Customer-operated metrics server and local time-series storage, with optional Alertmanager and exporters. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support. |
| Licensing model | Open Source / Open Core Apache License 2.0 for upstream Prometheus components. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms. |
| License | Apache License 2.0 for upstream Prometheus components. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
6 of 12 fields researched (50%) · 4 documented · 2 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Not confirmedEvidence and scope for Single sign-on
The reviewed server authentication page documents TLS and Basic authentication. It does not establish a native enterprise SSO/provisioning integration; an external identity-aware proxy would need a separately reviewed design.
Native server authentication page only; no claim that SSO is impossible · Source ↗ · Reviewed 2026-11-14
Sources checked — unresolved · Editor reviewed.
- Security controls
DocumentedEvidence and scope for Security controls
The server supports TLS and HTTP Basic authentication through a web configuration file. Client certificates and network restrictions require explicit settings; this is not proof of enterprise SSO or compliance certification.
Prometheus server transport and web authentication configuration · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The official installation guide provides binaries and a server container. Use persistent metrics storage and a configured scrape file; adding container command-line parameters replaces the default argument list.
Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Deployment artifact ↗ (select a released Prometheus image tag) · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
The storage guide estimates disk from retention seconds × ingested samples/second × roughly 1–2 bytes/sample, and reserves 15–20% disk headroom for compaction. It does not establish a universal CPU/RAM or HA minimum. Active-series cardinality, scrape rate, queries, WAL and remote storage require a workload-specific plan.
Official local-TSDB capacity model; whole-system compute and HA sizing remain unconfirmed · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The reviewed upstream application uses Apache License 2.0. Review the licence and bundled-component notices for your use and distribution. Hosting, databases, delivery services, commercial support and any separately licensed additions have their own costs and terms; no hosted-plan price is treated as a self-hosted quote.
Prometheus v3.16.0 server; software terms only, excluding infrastructure and operations · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
The publisher-designated GitHub release checked was v3.16.0, published 2026-11-05. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package.
Upstream prometheus/prometheus release record; commercial editions and deployment packages may differ · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
Show all fields (6 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
The sample Docker configuration is not a complete production monitoring deployment. Exporters, remote-write destinations and alert integrations may be outside the account; capacity and retention remain operational choices.
Community & maintenance
Prometheus is a CNCF Graduated project with public steering governance, established instrumentation/integration participation and a maintained upstream release stream.
Category fit
- Observability
- Metrics collection, time-series storage and PromQL analysis/alert evaluation. Log storage and distributed tracing require other components.
Compare within Observability
- AVEVA PI System (BYOL)Commercial industrial data collection, historian and visualization system with an AWS architecture.
- AWS
- Cloud Carbon FootprintOpen-source cloud-usage, energy and carbon-estimation application.
- Google Cloud
- Coroot Community EditionSelf-hosted application observability with service maps, logs, metrics, traces and continuous profiling.
- AWS
- Azure
- Google Cloud
- Oracle Cloud
- Datadog BYOC LogsDatadog log processing, indexing and storage in the customer's cloud, with search through Datadog Log Explorer.
- AWS
- Azure
- Google Cloud
- Elastic Cloud EnterpriseCommercial self-managed orchestration platform for Elastic Stack deployments across customer cloud hosts.
- AWS
- Azure
- Google Cloud
- Elastic Cloud on KubernetesElastic's Kubernetes operator for deploying and operating Elasticsearch, Kibana and related Elastic Stack resources in customer clusters.
- AWS
- Azure
- Google Cloud
- Grafana OSS Self-HostedSelf-hosted dashboards, visualization and alerting for operational data.
- AWS
- Langfuse Self-HostedSelf-hosted LLM observability, evaluations and prompt-management platform.
- AWS
- Azure
- Google Cloud
- Railway
- Render
Showing 8 of 20 other listings in Observability. These products address related workflows; read their category-fit notes before comparing scope. See all of Observability →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Official installation and runtime ↗prometheus.io
- Upstream project and capabilities ↗github.com
- Current upstream license ↗prometheus.io
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Self-managed Prometheus in an EKS monitoring stack ↗ · AWS
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
AWS documents kube-prometheus-stack pods in a customer EKS cluster, including the Prometheus Server StatefulSet and Grafana application. This evidence covers those self-managed components, not Amazon Managed Grafana or Amazon Managed Service for Prometheus. Review persistence, retention, authentication and cluster operating costs.
- Self-managed Prometheus in an EKS monitoring stack ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- Community governance ↗prometheus.io
- Graduation and ecosystem context ↗prometheus.io
- Current maintenance releases ↗github.com