Billing, credits, and plans
Use this guide when you want to understand what stays free in local Guard, what Guard Cloud adds later, and why plan pressure should feel like pain relief instead of random upsell.
What stays local and unmeteredDirect link to What stays local and unmetered
Core local Guard safety is not the premium story.
Local Guard still gives you:
- harness discovery
- install and wrapper protection
- local approvals
- local receipts and diffs
- local policy decisions
That is why Guard can feel useful before sign-in.
What billing is actually attached toDirect link to What billing is actually attached to
/guard/billing and related plan routes matter when the cloud product is doing work such as:
- syncing trust memory across devices
- keeping longer receipt history
- powering alerts and watchlists
- sharing policy across a team
- supporting delegated approvals and managed workspaces
Read billing as operator pressureDirect link to Read billing as operator pressure
The Billing route is most useful when it answers:
- are device or sync limits blocking the command center from becoming useful?
- are credits or buckets shaping what Guard can remember?
- is the current plan still aligned with how many people or machines rely on shared trust memory?
Good upgrade momentsDirect link to Good upgrade moments
The strongest upgrade moments are operational, not cosmetic:
- “I do not want to rebuild trust memory on another laptop.”
- “I need alerts when a trusted artifact changes.”
- “My team should not rediscover the same policy every week.”
- “Managed workspaces need one approval queue.”