Prometheus in the Cloud Fully Managed, Infinitely Scalable

You can send metrics to Bleemeo in multiple ways: Glouton agent can scrape Prometheus endpoints locally and forward metrics, you can configure remote_write from existing Prometheus instances to Bleemeo's endpoint, or send metrics via OTLP (OpenTelemetry Protocol). Glouton is the recommended approach as it adds infrastructure context and requires minimal configuration.

Yes, Bleemeo fully supports PromQL (Prometheus Query Language). You can use PromQL for custom dashboard widgets, alert conditions, and ad-hoc queries. This means you can migrate existing Prometheus dashboards and alert rules with minimal changes. Our documentation provides examples and best practices for PromQL usage in Bleemeo.

Yes, Bleemeo provides a Prometheus-compatible API endpoint that works as a Grafana data source. You can connect your existing Grafana installation to Bleemeo and use your existing dashboards. This allows teams to continue using familiar tooling while benefiting from Bleemeo's managed storage and scalability.

Bleemeo retains metrics for 13 months by default, compared to Prometheus's typical 15-day local retention. This long-term storage enables year-over-year comparisons, capacity planning, and compliance requirements. All retention is automatic - no need to configure external storage solutions like Thanos or Cortex.

Self-hosted Prometheus at scale typically costs $5,000-10,000/month including infrastructure, storage solutions, and 20-40 hours of engineering time. Bleemeo's managed service costs $500-3,000/month with zero operational overhead. Use our calculator to compare costs for your specific use case. The savings increase with scale due to our efficient multi-tenant architecture.

Bleemeo provides built-in high availability with multi-zone redundancy and automatic failover. We achieve 99.99% uptime SLA. This is included in the standard service - no need to configure multiple Prometheus instances, set up replication, or manage failover manually. Your metrics are always available when you need them.

Yes, migration is straightforward. You can run Bleemeo alongside your existing Prometheus during transition. Configure remote_write to send metrics to both systems, validate data in Bleemeo, then decommission your self-hosted setup. Alert rules can be migrated using PromQL compatibility. We provide migration guides and support for enterprise customers.

Bleemeo's architecture handles millions of time series without manual intervention. As your metrics volume grows, our infrastructure scales automatically. You don't need to resize instances, configure sharding, or set up federation. This is handled transparently - you simply send metrics and we ensure they're stored and queryable regardless of volume.

Bleemeo includes a full alerting system compatible with Prometheus alerting rules. You can define alerts using PromQL conditions, configure multiple notification channels (email, SMS, Slack, PagerDuty, webhooks), set up escalation policies, and use features like grouping and maintenance windows. This replaces the need for separate Alertmanager infrastructure.

Yes, security is a priority. All data is encrypted in transit (TLS) and at rest. Bleemeo is hosted in European data centers with SOC 2 compliance. Each customer's data is isolated. We support SSO integration and role-based access control. See our security page for detailed information about our security practices and certifications.