Scout · Self-hosted

License & heartbeat

Self-hosted Scout cannot serve /v1 without a valid license. Heartbeats register deployments and refresh offline grace tokens.

Terms of use

Scout Self-Hosted uses your existing Macrocontent account. License tiers, commercial use rules, and Stripe billing are covered in Macrocontent Terms of Use — §6 Macro Scout (same as Cloud, Store, and Account).

License tiers

Developer (free) — 1 non-production deployment, 2 workers. Dev, evaluation, personal projects only.
Developer+ — €990/year, 1 production deployment, 2 workers. Commercial use allowed.
Team — €2,990/year, 1 production deployment, 10 workers (~€299/worker/year)
Business — €7,990/year, 5 production deployments, 30 workers (~€266/worker/year)

What is a browser worker?

One browser worker can run one active browser job at a time. Ten workers = up to ten parallel screenshots, journeys, or crawls.

License key format

Keys use the prefix lic_scout_ and are issued from the Scout console. Store them as secrets — same care as API keys.

Validation flow

On startup, Scout calls POST /internal/scout/license/validate on the Macrocontent platform.
The platform checks tier limits (workers, max deployments) and registers or updates the deployment instance.
A signed offline JWT (7 days) is returned and cached locally for grace when the platform is unreachable.
Heartbeats repeat every ~5 minutes while the process runs.

Instance identity

Set SCOUT_INSTANCE_ID to a stable id per cluster (e.g. ci-eu-1). If omitted, Scout generates a UUID persisted under .scout/instance-id.

Console heartbeat status

In Scout console → Self-hosted, each license lists deployments with healthy (heartbeat < 15 min), stale, or offline.

Revocation

Revoking a license in the console marks it inactive immediately. Running servers fail validation once offline grace expires.