Platform · Integrations

An open framework, not a walled garden.

Randoli is OpenTelemetry-native by design. Any OTel receiver in, any OTel-supported backend out, no proprietary agent, no forced backend, no lock-in.

No lock-in, no proprietary formats

Randoli's data plane stores your telemetry in Loki, Tempo, and Prometheus or VictoriaMetrics. These are open, standard formats, not a proprietary store you'd need to migrate off of later. It's also what lets the telemetry proxy pull up raw logs, traces, and metrics on demand during an investigation.

You retain full ownership. It's your infrastructure, so you control security, retention, and usage on your own terms. And nothing stops you from also sending the same telemetry to any other OTel-compatible backend you run, at the same time.

Categories

Cloud & infrastructure

AWS
Microsoft Azure
Google Cloud
Red Hat OpenShift

OpenTelemetry & backends

(default: Loki, Tempo, Prometheus/VictoriaMetrics)

OpenTelemetry
Loki
Tempo
Prometheus
VictoriaMetrics
Pyroscope
Perses

Workflow & incident response

(via Raiya MCP — any MCP-compatible tool works)

GitHub
Jira
Confluence
Slack
Microsoft Teams
PagerDuty
ServiceNow
+ any MCP tool

Alerting

Email
Slack
Microsoft Teams
PagerDuty
Webhook
Raiya, extended via MCP

The SRE agent connects to whatever your team already uses.

Raiya integrates with third-party tools through the Model Context Protocol (MCP), so it isn't limited to a fixed integration list. Any MCP-compatible tool can plug into root cause analysis, executable runbooks, or Raiya's chat interface.

RCA

Pull context from ticketing, docs, or internal tools into root cause analysis.

Runbooks

Executable runbooks can call out to any MCP-connected tool your team has approved.

Chat

Ask Raiya questions that span your stack and your other connected tools, in one conversation.

Keep your tools. Add Randoli.