Relivio is unclaimed —

Relivio

post-deploy verification, one verdict per deploy·relivio.dev

Relivio verifies the first 15 minutes after a deploy using runtime signals and returns a single verdict — STABLE, WATCH, or RISK — along with the likely affected API and a recommended next action. It is designed as a narrow verification layer that sits alongside existing monitoring tools rather than replacing them, using deploy-window error signals instead of full log search. Teams can integrate it via an SDK, REST API, or an MCP server for agent-driven workflows, and receive verdicts in channels like Slack or Discord.

What it's for

Verifying deploy health in the first 15 minutes after releaseDetecting regressions and error pattern shifts right after deploymentSurfacing which API is likely affected after a deployFeeding post-deploy verdicts into CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins)Letting AI agents read deploy verdicts via an MCP serverReceiving deploy verdicts in Slack or Discord

Features 15

15-minute post-deploy observation window
Console for setting up channels and monitoring
Deploy-window error signal analysis (not full log search)
deploy_ack and summary_final notification events
Idempotency-Key support to avoid duplicate events
MCP server for agent workflows
OAuth session cookie auth for Console APIs
One verdict per deploy: STABLE, WATCH, or RISK
Outcome labeling (OK, Issue, Rollback) to improve future verdicts
Recommends a next action after each deploy
REST API integration path (deployments and ingest endpoints)
SDK integration path
Surfaces the likely affected API after a deploy
Works alongside existing monitoring/observability tools
X-API-Key auth for Runtime APIs

At a glance

API

TypeWeb app

DeploymentCloud

PlatformsWeb

LanguagesEnglish, Korean

Forengineering teams, developers, teams running CI/CD pipelines, agent-driven workflows

CompanyRelivio

Integrations

SlackDiscordGitHub ActionsGitLab CIJenkins

Resources

Pricing

No pricing page or prices were found; the site currently states launch-phase usage limits (2 projects per account, 100 deployment registrations per month) rather than paid plans.