Skip to main content

Plans and Limits

Tiers​

TierEvaluations per monthPrice
ProUnlimited$5/month — see accounts.sigmashake.com
EnterpriseUnlimitedContact sales

A valid Pro or Enterprise subscription is required to run ssg. Activate your license after subscribing:

ssg auth login

The evaluation counter is per-device and resets at the start of each calendar month. It is shown for usage reporting; Pro is not capped.

What counts as an evaluation​

One evaluation is one call to the governance engine — one PreToolUse hook firing, or one direct ssg eval call. Both write an audit row and increment the monthly counter. Ambient-rule reads, ssg status, ssg policy status, and other read-only CLI commands do not count.

What happens if the license check fails​

The two code paths that run governance have different policies when the license cannot be verified, by design:

ssg eval (direct invocation) — fail-CLOSED​

When the license check fails or the subscription is not active, ssg eval returns a block decision:

{
  "decision": "block",
  "reason": "License check failed. Run: ssg auth login"
}

If the counter check itself fails for any reason (database unavailable, counter file unreadable), the result is also a block:

{
  "decision": "block",
  "reason": "Eval limit check failed — please retry. If the issue persists, run: ssg status"
}

The rationale: a direct ssg eval caller expects an authoritative governance decision. Failing open would silently remove governance, which is worse than a temporary block.

ssg hook eval (PreToolUse hook) — fail-OPEN​

When the license cannot be verified inside the PreToolUse hook, ssg allows the call through and prints a warning to stderr:

[ssg] ⚠ License check failed — allowing through. Run: ssg auth login https://accounts.sigmashake.com

The rationale: blocking the PreToolUse hook bricks the host editor (Claude Code, Cursor, etc.) until the issue is resolved. That is a worse outcome than letting the call pass with a visible warning.

Progressive warnings​

As the subscription period nears expiry, ssg surfaces two warning thresholds:

  • At 7 days before license expiry: a soft reminder is printed to stderr.
  • At 1 day before license expiry: an urgent warning is printed to stderr.

Checking your usage​

ssg status           # shows this month's eval count and subscription tier
ssg flight           # full telemetry including monthly eval count

The dashboard Overview card also displays this month's eval count in real time.

Subscribing​

Subscribe at accounts.sigmashake.com. Pro gives unlimited evaluations per month.

After subscribing, activate the license on your machine with the device-flow login — there is no key to copy or paste:

ssg auth login       # opens the browser, writes the license automatically

For headless, Docker, Kubernetes, or CI environments where the browser flow isn't available, mint a CLI token in Settings → CLI Tokens and pass it as SSG_API_KEY:

docker run --rm -e SSG_API_KEY ghcr.io/sigmashakeinc/ssg:1.0.7 status

Legacy direct license JWT injection is also supported:

export SSG_LICENSE_KEY="<your-jwt>"

Run ssg status to confirm the tier:

ssg status --json | grep tier

See also​