Documentation
Everything, stated once.
How RELIASTRA observes a dependency, what it does with the observations, and how to call all of it from your own systems. Every number in these guides is read from the running code, not restated from memory.
Start
Operate
- ConfigurationEvery field on a dependency, its default, and the two that can lock you out of your own endpoint.
- MonitoringWhat a probe does, what it records, and the four things it structurally cannot see.
- IncidentsThe detection rule, the fields on an incident, and what resolution does and does not mean.
- EvidenceWhat the artifact contains, how it is generated, and how long it is retained.
- VerificationHow a third party checks an artifact without trusting RELIASTRA, and without an account.
Integrate
- REST APIAuthentication, the endpoints that matter, pagination and rate limits.
- CLIInstall, authenticate, read dependencies and incidents, retrieve evidence, and gate a pipeline on verification.
- WebhooksPush incidents and evidence into your own systems instead of polling for them.
- MCP serverLet a compatible AI coding agent use Reliastra: 18 tools over stdio or Streamable HTTP, authenticated with a scoped API key.
Reference
An account is the shortest path to a real observation.
Add one dependency you already own, and read what the probe records before deciding whether the rest is useful.