Scan your architecture in one pass. See every cross-service dependency as a live graph. Click any resource — know in under 30 seconds what else breaks if it fails.
When something breaks, you open 4 tabs to answer one question. You tab between compute, databases, queues, functions, trying to piece together what actually depends on what.
The console is a service browser. It cannot show you cross-service relationships. It cannot tell you what breaks if a queue goes down. It cannot compare your live infra to your IaC.
Not a dashboard. Not another observability tool. An incident-response surface that answers one kind of question — fast.
No tabs. No guessing. Click any resource — connected resources highlight, everything else dims. The subgraph you need. Nothing you don’t.
RiftView scans every service your provider exposes in a single run and holds the topology as a connected graph. Not per-service snapshots — a whole-account model that stays live.
Most scanners hand you 40 findings sorted by nothing. RiftView surfaces the three highest-severity chain-of-failure risks — the ones that take your stack down, not the ones your compliance tool nags about.
RiftView compares your current deployment against your state file. Changes that happened outside your IaC — console clicks, one-off CLI fixes — show up as diff lines with the fix commands ready to run.
No copy-pasting commands into a terminal at 2am, no double-checking the region flag. RiftView generates the exact CLI command for each finding, asks you to confirm, streams the output back to you.
RiftView reads from your provider’s local credentials file, environment variables, or an SSO session. Credentials stay local — read-only by default.
RiftView enumerates every service in parallel and assembles the graph. Typical account: 4 to 12 seconds. Large accounts: up to 30.
Instant blast radius. Top risks panel. Drift view. Remediation commands generated inline. This is the 2am workflow.
Same scanner. Same analysis. Stable JSON, deterministic exit codes, no Electron runtime. Published as @riftview/cli on npm.
Every subcommand uses the cloud SDK in read mode — write operations stay in the desktop app. Output is pinned to schemaVersion: 1; any breaking change bumps the version.
$ npm install -g @riftview/cli
Composable building blocks for CI pipelines: capture a snapshot once, gate risks and drift off it, diff against yesterday’s scan to see what changed.
scanFull account scan. Optional --snapshot writes JSON for later runs.risksSeverity-sorted findings. --fail-on S1|S2|S3 gates CI.driftCompare live infra to terraform.tfstate. --fail-on-drift trips on any change.diffStructurally diff two snapshots. Added, removed, field-level changes.versionBuild metadata: semver, git commit, build date, Node version.Every CI pipeline can branch on $? directly — the contract is enforced by tests, so a future release won’t silently reshuffle the codes.
Point RiftView at your cloud profile. In 30 seconds you’ll see what your infrastructure actually looks like.