Where should I start if I am a new user?

Start with Getting Started, connect one cloud account, run one baseline scan, and export one PDF or CSV report.

Where can I find cloud provider credential requirements?

Use Provider Reference links to open the Provider Credentials page and runtime directory with credential fields, runtime IDs, and official entry references.

Does API coverage include scan orchestration and settings management?

Current API coverage focuses on status, scans, accounts, tokens, and automation references. API Center documents the current surface and next expansion path.

How does local-first architecture protect credentials?

Credentials remain on the operator machine. Cloud Waste Scanner calls provider APIs from the local environment and exports reports locally.

Can teams run a weekly governance workflow with current features?

Yes. Teams can run baseline scans, export PDF and CSV evidence, assign owners, and execute weekly review loops using playbooks and metrics definitions.

What is the migration status of old solutions pages?

Legacy solutions pages are transitional references with noindex and canonical mapping to playbooks. The docs center and playbooks are the long-term source of truth.

Docs Map

Primary Paths

Proof Pages

Fast path

Download the app.
Add one read-only cloud account.
Run one baseline scan.
Export the report and assign owners.

Documentation One front door for setup, scanning, providers, API, and support

Find the right Cloud Waste Scanner document in one click.

This Docs Center is the primary path for operators, platform teams, and buyers. It keeps the user journey simple while preserving deep reference pages for search, API implementation, provider review, and troubleshooting.

Start Here API & Automation Search Docs

Search Documentation

Search setup guides, providers, Kubernetes/container scanning, API endpoints, playbooks, and troubleshooting notes.

Open full search

Path 1

Start Here

Install, add one account, run the first scan, and export one report.

Path 2

Scan & Governance

Understand findings, reports, Kubernetes scans, and weekly review loops.

Path 3

Providers

Check runtime coverage, credential fields, and read-only setup expectations.

Path 4

API

Use Local API, tokens, errors, playbooks, webhooks, and MCP routes.

Path 5

Troubleshooting

Resolve install, proxy, credential, API, and scan-result questions.

Start Here

New users should complete one clean baseline workflow.

The first success path is deliberately small: install the app, connect one read-only account, run one scan, export one report, and review the findings with a real owner.

1. Install

Use the download center and verify the right package for your OS.

2. Connect

Start with one provider account and read-only permissions.

3. Scan

Run a baseline scan before changing policy or cleanup behavior.

4. Export

Export PDF or CSV evidence for the first review meeting.

Download App 15-Minute First Scan Core Setup Guide

Scan & Governance

Move from scan output to weekly operating discipline.

Use this path when the team already installed CWS and now needs to understand what gets scanned, how evidence is interpreted, and how findings become repeatable cleanup work.

Need	Best page	What it answers
Understand local-first custody	Security	Credentials stay local and provider calls run from the operator environment.
Review a scan result	Sample Report	What findings, savings, and evidence look like before rollout.
Run Kubernetes/container scanning	Kubernetes scan release guide	Pods, nodes, workloads, services, PVs, PVCs, reports, and action plans.
Build a weekly loop	Weekly rhythm guide	How to assign owners and review progress without ad-hoc cleanup.

Execution Insight

Cloud waste is an ownership failure, not only a technical failure. The docs path therefore ends with owner assignment and evidence export, not just a scan button.

Providers & Credentials

Validate cloud coverage and credential fields before rollout.

Use this path when security, platform, or procurement teams ask whether a provider is supported and which read-only credential fields are required.

Provider Directory

Runtime names, provider coverage, and canonical provider links.

Credential Schemas

Field-level credential requirements for supported provider runtimes.

Proxy Setup

Network and proxy setup for restricted corporate environments.

API & Automation

Use one API path: overview, reference, tokens, errors, playbooks.

Automation pages remain separate for SEO and implementation depth, but the user journey should be linear: understand the surface, copy endpoint examples, configure tokens, handle errors, then automate playbooks.

1. API Overview

Current coverage and expansion tracks.

2. Reference

Endpoint-level contracts and examples.

3. Tokens

Local token setup and auth expectations.

4. Errors

Failure shapes, retry logic, and diagnostics.

5. Playbooks

Automation examples and runbooks.

Troubleshooting & FAQ

When something fails, diagnose by layer instead of guessing.

Use the FAQ for common questions, then follow the troubleshooting order: install/runtime, network path, proxy path, provider permission, scan stage, report export, API call.

Troubleshooting FAQ

Common install, proxy, scan, and report problems.

API Errors

Error contract, failure handling, and automation diagnostics.

Contact Support

Send version, provider, region, proxy mode, timestamp, and relevant logs.

Release Ledger

Check whether a behavior changed in a recent release.

Documentation Center

Start from one path, then go deep only when the task requires it.

Download the app, run one local-first scan, and use the docs to turn findings into a weekly governance loop.

Download Trial View Sample Report