Up to
20×lower memory usage
Elasticsearch reference
Metrikom
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
Keep your team focused on what you build.
Metrics and logs are essential. But running the platform behind them takes valuable engineering time away from the applications and services that move your business forward.
02 / Logs
Logs for debugging and analysis
Centralize, search, and alert on your application and infrastructure logs — from ingestion to retention.
-
Flexible log ingestion
Integrate with your existing logging environment.
Supported integrations include OpenTelemetry via OTLP, Syslog, Filebeat, Fluent Bit, Fluentd, Logstash, Vector, Telegraf, journald, the Elasticsearch API, and Loki. -
Centralized search and analysis
Investigate application and infrastructure logs in one place.
-
Dashboards and alerting
Visualize log data and turn relevant patterns into operational alerts.
-
Contextual investigation
Connect logs with available operational context, where supported.
-
Managed retention and operations
We handle storage, retention, scaling, and ongoing platform operations.
Efficiency by design
More signal. Less overhead.
Our log engine processes more telemetry with significantly fewer resources – keeping logs efficient and costs more predictable.
-
Efficient architecture
-
Fast processing
-
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 / Metrics
Metrics for infrastructure and applications
Collect, explore, and alert on your metrics — from ingestion to dashboards.
-
High ingestion rate
Designed for large volumes of time series from infrastructure and applications.
-
Fast queries
Short response times for dashboards and alerting evaluations.
-
Lean storage
Efficient storage of time series for a smaller footprint.
-
Low memory footprint
Resource-friendly operation of the engine.
-
Horizontally scalable
The platform scales as telemetry volume grows.
04 / Commercial model
Capacity, not surprises.
We use a predictable capacity model instead of usage-based billing – so observability stays budgetable, without usage-driven cost spikes.
Pay-as-you-go
Costs follow consumption – hard to predict, with spikes that only become visible after the fact.
Capacity model
You reserve fixed capacity – costs are set in advance and stay predictable through operation.
01
Reserve capacity
You reserve the resources you need – cores, memory, and storage.
02
Fixed service fee
An ongoing fee for operating and maintaining the platform.
03
Optional extensions
Individual extensions can be added when you need them.
Good to know
Capacity doesn't have to be static – optionally enable auto-scaling so resources grow with your needs.
05 / The platform
A fully managed observability platform
We operate the entire platform. Your team focuses on applications and business services instead of running an observability stack.
01
Less platform maintenance
No patching, scaling, or troubleshooting of another critical platform.
02
Faster onboarding
Observability as a service instead of months of platform build-out.
03
Predictable operations
A specialist partner runs operation and availability.
04
Standards-based
OpenTelemetry at the center — no proprietary instrumentation.
Two products, one platform: Metrics and Logs work well together — but using both is not required.
06 / Where the platform runs
Built on and fully integrated with T Cloud Public.
We focus on the T Cloud Public and build a deep, native integration.
T Cloud Public Private telemetry path
-
Your workloads
-
OpenTelemetry
-
Private Endpoint
-
Metrikom
-
Insights
Workloads stay in your environment. Use OpenTelemetry — or other integration tools like Vector — to send telemetry over the private endpoint into the Metrikom platform.
- OTLP
- The OpenTelemetry protocol — the open standard for transporting telemetry data.
- VPC Endpoint Service
- Private network access within the cloud, without a path over the public internet.
07 / Company
A focused, independent partner
An independent company building managed observability for the T Cloud Public — so your teams get the benefits of sovereign European infrastructure without carrying the operational load. It's the first platform in a longer mission.
FAQ
Frequently asked questions
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.
How is the platform priced?
We use a predictable capacity model: you reserve resource capacity (cores, memory, storage) plus an ongoing service fee, with optional individual extensions. We discuss specific terms in a consultation.
Is the platform available yet?
The platform is currently in beta. Book a consultation to get involved early.
What about compliance and certifications?
An ISO/IEC 27001:2022 certification and a BSI C5 attestation for operations are in the works.
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 do you operate, and what do we operate?
You run your applications and instrument them with OpenTelemetry. We operate the observability platform: ingestion, storage, querying, dashboards, alerting, scaling, and upgrades.
Consultation
Let's talk about your observability
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