Up to
20×lower memory usage
Elasticsearch reference
Metrikom
Observability Platform
A managed platform for metrics and logs – built for teams that need operational clarity.
02 / Efficiency by design
Process more telemetry with fewer resources and more predictable costs.
Figures come from internal tests against a configured Elasticsearch reference environment. Results depend on workload, retention, and configuration and are not universal performance guarantees.
03 / The operational dilemma
Metrics and logs are essential. The stack behind them can consume the same platform teams that should be advancing applications and business services.
Deployment, security, scaling, upgrades, retention, and troubleshooting become a permanent responsibility for your team.
Available tools remain in place even when integrations, workflows, and user experience do not meet your requirements.
A clear division
You operate your applications and business services. Metrikom operates the observability platform.
04 / Location is part of the architecture
Under active developmentMetrikom is currently building the platform in the German T Cloud Public – close to workloads, privately reachable, and clearly separated from your own cloud environment.
Inside your own T Cloud Public VPC
SDKs and Collectors send over OTLP
VPC Endpoint Service without a public ingest path
Separately operated platform in Germany
Dashboards, search, and alerts
Workloads stay in your environment. Telemetry is transferred privately into the separately Metrikom-operated environment.
05 / Two signals. One platform.
Metrikom Metrics
Collect, store, query, visualize, and alert — as a managed service with native OTLP ingestion.
Metrikom Logs
Ingest, store, search, visualize, and alert on application and infrastructure logs.
Two products, one platform. Metrics and Logs work well together — but using both is not required.
06 / Managed means clear responsibility
You operate
Metrikom operates
07 / Security & trust
Trust comes from verifiable properties of the architecture — not from superlatives.
Your telemetry never leaves the T Cloud Public network. Data is transmitted securely via private VPC endpoints, without any public ingest endpoint.
Fully operated within the German T Cloud Public, aligning with your requirements for data sovereignty and local compliance.
Our architecture is built on a Zero Trust model, utilizing mTLS and a dedicated PKI to strictly secure all internal and external communication.
Strict separation between your cloud environment and the Metrikom-operated service, ensuring you maintain full control.
Planned certifications
Metrikom intends to pursue ISO/IEC 27001:2022 certification and a BSI C5 attestation for platform operations. These are future objectives — no audits are currently underway and no assurances are made.
Certifications of the underlying T Cloud Public are T Cloud Public's, not Metrikom's.
The mission behind Metrikom
Metrikom builds and operates managed cloud services for organizations that want the benefits of sovereign European cloud infrastructure without carrying the full operational burden themselves. Observability for T Cloud Public is the first platform in that mission.
A standalone company — not a product or business unit of Deutsche Telekom, T-Systems, T Cloud Public, or Open Telekom Cloud.
Focused on T Cloud Public, with the option to support other European cloud providers in the future.
OpenTelemetry is at the center of telemetry ingestion.
FAQ
No. Metrikom is an independent company and not a product or business unit of Deutsche Telekom, T-Systems, T Cloud Public, or Open Telekom Cloud.
Your workloads stay in your own T Cloud Public environment. Telemetry is sent over a private VPC endpoint into the separately Metrikom-operated platform, which also runs in the German T Cloud Public. The transfer does not use the public internet and does not leave Germany.
The platform is in preparation. Book a consultation to talk with us early.
Metrikom intends to pursue ISO/IEC 27001:2022 certification and a BSI C5 attestation for operations. These are future objectives; no audits are currently underway and no assurances are made.
No. Metrics and Logs are two products within one platform and work well together — but using both is not required.
You run your applications and instrument them with OpenTelemetry. Metrikom operates the observability platform: ingestion, storage, querying, dashboards, alerting, scaling, and upgrades.
Consultation
Metrikom is under active development. We are looking for early conversations with teams that take T Cloud Public, private connectivity, and OpenTelemetry seriously.
What we'll discuss