Trust
Security: your monitoring data stays yours
Encryption, SSRF-safe probing, tenant isolation, evidence integrity.
Encryption
Stored secrets such as request headers are encrypted at rest. Traffic is served over HTTPS. Card details are handled by the payment provider; RELIASTRA never stores card numbers.
Safe probing
Before any check request leaves, the target is resolved and validated against an SSRF policy that rejects private, loopback, link-local and metadata addresses. Blocked targets are recorded as configuration problems - never as vendor outages - and no request is sent.
Tenant isolation
Dependencies, incidents, evidence and credentials are scoped per account and enforced server-side: one account is one tenant in the data model, and no route accepts a tenant identifier from the client. Public observatory records describe public endpoints only - never a customer's endpoints, headers or credentials.
Evidence integrity
Generated records are checksummed and bound to the account that produced them. Verification is unauthenticated and confirms existence and integrity without disclosing private configuration. Audit-log entries cover security-relevant actions.
Sessions and access
Short-lived access tokens with rotation, HttpOnly admin session cookies, and rate limiting on authentication and public endpoints. The admin control plane is a separate security domain with its own credentials.
What to do next
Read the Privacy Policy, review Terms, or contact us with security questions at support@reliastra.com.
Add one dependency you already own.
RELIASTRA probes the external services your software relies on, confirms a fault deterministically, and keeps a record you can verify later. One plan, $9/month, and a 14-day trial that needs no card.