Hyperping's server agent embeds an OpenTelemetry collector and exports OTLP over HTTP with gzipped payloads, using the metric names of the OpenTelemetry hostmetrics receiver. You don't run a collector of your own, and the signals stay portable if you later want to send them somewhere else as well.
The part that matters day to day is the naming. system.cpu.time or system.memory.usage means the same thing no matter who collected it or where it's stored. Instrumentation lives in your code and on your hosts, the backend becomes a routing decision, and switching vendors turns into a configuration change instead of a re-instrumentation project.
For infrastructure, the hostmetrics receiver defines the standard CPU, memory, filesystem, disk, and network metrics. Any agent that follows it produces host metrics you can compare across tools.
It isn't a backend. OpenTelemetry produces and moves telemetry, and something else has to store it, chart it, and alert on it. It also doesn't decide what to measure for you: a service instrumented with OTel but no useful spans or metrics tells you as little as before.
Yes. It's open source under the Apache 2.0 license. You pay for wherever you send the data.
Prometheus is a metrics backend and a pull-based collection model. OpenTelemetry covers traces, metrics, and logs, and pushes data over OTLP. They work together: the collector can scrape Prometheus endpoints, and Prometheus can ingest OTLP.
No, but it's worth choosing an agent that follows its conventions, so your metric history means the same thing if you change tools.