ReliOp | FAQ

Coverage Today vs Roadmap

Deterministic today: service configs

YAML/JSON service definitions with dependencies, SLOs, failover, circuit breaker, rate-limit, and blast-radius fields. These findings are reproducible and rule-based.

Advisory today: deploy configs

Kubernetes, Helm, ArgoCD, and CI/CD configs are part of the next deterministic rule packs. Until promoted, they are reviewed as advisory findings, not deploy-blocking gate logic.

Roadmap: IaC and operating context

Terraform, DB migrations, feature flags, observability gaps, SNOW incidents, PRBs, CMDB, and runbooks feed continuous risk intelligence after rule calibration and enterprise integration.

Product

ReliOp is Reliability Risk Intelligence. It traces failure paths, scores service and deploy risk, and turns findings into controlled remediation work before incidents become outages or control events.

Observability tells you something is wrong after it happens. ReliOp shows what can break next, why it matters, and which fix reduces the most risk — before deploy and during continuous scans.

Security & Data

No. ReliOp is fully config-first: no agents, no instrumentation, no production access. You get value in minutes by uploading configs.

ReliOp does not need direct production access and can run fully inside your environment on Enterprise. For the public demo, use sanitized configs and remove secrets, credentials, customer data, regulated records, and internal identifiers you would not share externally.

Yes, if the config is safe to submit to the public demo after sanitization. Use representative service names if needed, keep the dependency structure realistic, and remove secrets or sensitive data. For sensitive production configs, contact [email protected] for a private enterprise path.

Only if you opt in to an external AI provider. Enterprise deployments can instead point ReliOp to the bank's approved LLM endpoint. The LLM explains findings and drafts actions; deterministic ReliOp rules remain the source of truth for scoring and gates.

Usage

Minutes. Upload a config and get a risk report immediately. Enterprise deployments typically show value within weeks.

YAML or JSON with a list of service definitions. Each service should include: name, tier (e.g. tier-1), owner, slo_target, slo_current, dependencies (a list of service names), and optionally deployment info like az_count.

No. Even partial configs provide meaningful insight. A small set of services can reveal critical risks and dependency gaps.

Email [email protected] for a private deployment, financial-services design partnership, or adoption discussion. The Design Partner Program is the right path when configs, incidents, SNOW/CMDB records, PRBs, or continuous scans involve sensitive production data.

Try ReliOp with a Safe Service Config

Use a sanitized real config or a representative sample. For sensitive production data, join the Design Partner Program.

Run Audit → Start Enterprise Evaluation