Install locally

Scout Private Beta

Choose your beta path.

Private beta is limited. Start locally if you want the cleanest path. Choose hosted only when you want a convenience API key with finite, metered beta credits.

Beta paths

Local install first. Hosted beta when convenience matters.

Local beta

Best for first tests, private workflows, browser capture, and artifact inspection.

Open quickstart

Hosted beta checkout

Creates a Stripe checkout session only after hosted pricing and payment configuration are approved.

Hosted beta is capped and metered. It is not unlimited crawling.

Current hosted beta is invite-only while unit economics are validated. Final credits, price, retention, and overage rules require founder approval.

Before inviting testers

Run the launch readiness checker.

Scout ships a packaged readiness check so beta operators can tell the difference between controlled private beta readiness and public launch readiness. 

scout launch-readiness
scout launch-readiness --require-public

Private beta

The expected beta result is `ready_with_limits`.

Public launch

The public gate is expected to stay blocked until the open release checklist items close.

Hosted beta checkout

Request hosted API access.

Scout will only redirect to Stripe if hosted beta payment is configured. Otherwise, the page tells you to use the local beta path and try again later.

Hosted beta pricing is not approved yet. Limited credits, not unlimited crawling.

By requesting hosted access, you acknowledge the beta terms placeholder and beta privacy placeholder.

Support

Beta support is evidence-first.

Tester handoff packet

Send approved testers the docs/product/private-beta-tester-handoff.md packet before their first run. It explains local-first setup, hosted finite credits, artifact inspection, feedback format, and secret-handling boundaries.

Report bugs

Use the private beta bug template with your surface, version, command or endpoint, run ID, and non-sensitive artifact path.

Request workflows

Use the private beta feature template for missing product, company intel, hosted API, CLI, Docker, skill, or documentation workflows.

Keep secrets out

Do not paste API keys, cookies, private customer data, paid-site content, or screenshots containing secrets into public feedback.

Security reports should not be filed as public issues. Follow Scout legal and security guidance and report vulnerabilities privately to the maintainer.