Skip to content

docs: link the hosted service from the README - #5

Open
rchildress87 wants to merge 1 commit into
mainfrom
docs/hosted-option
Open

docs: link the hosted service from the README#5
rchildress87 wants to merge 1 commit into
mainfrom
docs/hosted-option

Conversation

@rchildress87

Copy link
Copy Markdown
Contributor

The CLI never mentioned Disco Cloud anywhere — grep for saas, hosted, commercial, or discocloud across README.md, FEATURES.md, CONTRIBUTING.md, SECURITY.md, and CODE_STRUCTURE.md returned nothing. The link between the open source scanner and the hosted product ran one way, SaaS to CLI only.

What this adds

One ## Hosted section, placed after "Why disco" and before "Install". Placement is deliberate: the first three sections stay entirely about the tool, so a reader learns what disco does and why before encountering any commercial mention.

The section leads with what the CLI is on its own — MIT, local, no telemetry, no paid edition — and names the six verbs that have no hosted equivalent, before describing what the service adds. The wording for the split is taken from the pricing page so the two do not drift.

Claims and where each was checked

Every factual claim was verified against source rather than assumed:

Claim Settled by
MIT-licensed LICENSE:1
No telemetry Only outbound calls are the AWS Service Reference index and the GCP Discovery API (internal/providers/aws/aws_servicereference.go:19, internal/providers/gcp/gcp_coverage.go:69); no analytics, update check, or crash reporting
No paid edition No license-key gating, build tags, or version locking anywhere in the CLI
The six CLI-only verbs exist cmd/graph.go:63 (path), cmd/diff.go:49, cmd/graph.go:71 (--orphans-only), cmd/tag_coverage.go:45, cmd/check.go:102 (SARIF), README:19 (byte-identical JSON)
Each is absent from hosted Greps for shortest-path, scan-to-scan diff, orphans, tag-coverage, and Rego/SARIF across the hosted app's internal/ return no feature — only unrelated prose and one doc comment for a compliance-pack entitlement that nothing reads yet
Free cap is 3 accounts internal/plan/plan.go:41 in the hosted app
No trial clock trial_period: null on both prices in the hosted app's Paddle catalog
No seat cap on any tier internal/plan/plan.go:63 — "There is deliberately no user or seat cap"
Azure is by arrangement Azure has no self-serve connector wizard deployed; its wizard returns 503
discocloud.io resolves HTTP 200

The absence half of the fourth row is the one that mattered most: claiming the hosted product lacks something it actually ships would be the worst possible defect in this file, so each of the six was checked in both directions.

One softening applied after review: the CLI-only verbs are described as having no hosted equivalent "today" rather than "by design", since a curated OPA compliance pack is a planned hosted entitlement (internal/plan/plan.go:77) even though nothing reads that field yet.

🤖 Generated with Claude Code

https://claude.ai/code/session_01TyMpXR3ctnUmvRgGyVXwTD

The CLI never mentioned Disco Cloud, so the only path between the open
source scanner and the hosted product ran one way. Adds a Hosted section
between "Why disco" and "Install": what the CLI is on its own first, the
six verbs that have no hosted equivalent, then what the service adds.

Every claim checked against source — MIT in LICENSE, the free cap and
null trial period in the SaaS plan and Paddle catalog, and each CLI-only
verb confirmed absent from the hosted app rather than assumed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TyMpXR3ctnUmvRgGyVXwTD
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant