Observability Platform

See what matters.

A managed platform for metrics and logs – built for teams that need operational clarity.

Zero Exposure VPC endpoint connectivity
Data Residency T Cloud Public in Germany
No Lock-in Native OTLP ingestion
Zero Maintenance Operated by Metrikom

02 / Efficiency by design

More signal. Less overhead.

Process more telemetry with fewer resources and more predictable costs.

  1. 01

    Efficient architecture

  2. 02

    Fast processing

  3. 03

    Predictable capacity

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

Observability should not become an operations problem.

Metrics and logs are essential. The stack behind them can consume the same platform teams that should be advancing applications and business services.

01

Operate it yourself

Deployment, security, scaling, upgrades, retention, and troubleshooting become a permanent responsibility for your team.

02

Accept the compromises

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 development

Built on and integrated with T Cloud Public.

Metrikom is currently building the platform in the German T Cloud Public – close to workloads, privately reachable, and clearly separated from your own cloud environment.

German T Cloud Public
  1. 01

    Your workloads

    Inside your own T Cloud Public VPC

  2. 02

    OpenTelemetry

    SDKs and Collectors send over OTLP

  3. 03

    Private endpoint

    VPC Endpoint Service without a public ingest path

  4. 04

    Metrikom

    Separately operated platform in Germany

  5. 05

    Insights

    Dashboards, search, and alerts

Workloads stay in your environment. Telemetry is transferred privately into the separately Metrikom-operated environment.

05 / Two signals. One platform.

From the first data point to an operational decision.

01

Metrikom Metrics

Metrics for infrastructure and applications

Collect, store, query, visualize, and alert — as a managed service with native OTLP ingestion.

  • Native OTLP ingestion
  • OpenTelemetry SDK and Collector integration
  • Managed scaling and storage
  • Dashboards and alerting
  • Less operational work for your team
02

Metrikom Logs

Logs for debugging and analysis

Ingest, store, search, visualize, and alert on application and infrastructure logs.

  • Native OTLP ingestion
  • OpenTelemetry Collector integration
  • Centralized search and analysis
  • Managed retention and platform operations
  • Correlation with operational context, where supported

Two products, one platform. Metrics and Logs work well together — but using both is not required.

06 / Managed means clear responsibility

Your team builds the product. We operate the platform behind it.

You operate

  • 01 Applications and infrastructure
  • 02 OpenTelemetry instrumentation
  • 03 Business services and SLOs
  • 04 How you use the insights

Metrikom operates

  • 01 Ingestion, storage, and retention
  • 02 Querying, dashboards, and alerting
  • 03 Scaling and ongoing maintenance
  • 04 Security updates and platform upgrades

07 / Security & trust

Trust starts with verifiable facts.

Trust comes from verifiable properties of the architecture — not from superlatives.

01

Private VPC connectivity

Your telemetry never leaves the T Cloud Public network. Data is transmitted securely via private VPC endpoints, without any public ingest endpoint.

02

Operated in Germany

Fully operated within the German T Cloud Public, aligning with your requirements for data sovereignty and local compliance.

03

Zero Trust security

Our architecture is built on a Zero Trust model, utilizing mTLS and a dedicated PKI to strictly secure all internal and external communication.

04

Clear separation

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

A focused, independent partner

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.

Independent

A standalone company — not a product or business unit of Deutsche Telekom, T-Systems, T Cloud Public, or Open Telekom Cloud.

T Cloud Public first

Focused on T Cloud Public, with the option to support other European cloud providers in the future.

Standards-oriented

OpenTelemetry is at the center of telemetry ingestion.

FAQ

Frequently asked questions

Is Metrikom part of Deutsche Telekom?

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.

Does my data leave my environment?

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.

Is the platform available yet?

The platform is in preparation. Book a consultation to talk with us early.

What about compliance and certifications?

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.

Do I need to use Metrics and Logs together?

No. Metrics and Logs are two products within one platform and work well together — but using both is not required.

What does Metrikom operate, and what do we?

You run your applications and instrument them with OpenTelemetry. Metrikom operates the observability platform: ingestion, storage, querying, dashboards, alerting, scaling, and upgrades.

Consultation

Let's talk about your observability

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

  • Your current T Cloud Public setup
  • Existing metrics and logs tooling
  • Operational pain with self-managed stacks
  • Missing integrations in your current solution
  • Private connectivity and onboarding requirements

We'll get back to you to arrange a time. No newsletter, no sales spam.

No email client? Write to us directly at kontakt@metrikom.de