DOCS / API / TIER GATING
API tier gating
There is none. Since August 2026, nothing in the Glassmkr API is tier-gated: hosted accounts and self-hosted instances both get the full read+write API.
#Overview
This page used to document which API capabilities required the paid Pro plan. As of August 2026, Glassmkr is fully open source and has no paid tiers, so there is nothing left to gate. The page stays because URLs live forever.
Every account API key (read, write, or admin scope) reaches the full API surface: server management, channel CRUD, alert mutations, trend warnings, health history, AI analysis, key management, and ingest. The web dashboard is likewise complete for every account.
#What changed, and when
In August 2026 the entire stack went open source (dashboard monorepo AGPL-3.0-only, Crucible agent MIT) and the Free/Pro split was retired. The three limits Pro used to lift are now handled like this:
- Node count. Hosted accounts have a 10-node per-account cap, a capacity protection rather than a tier. Self-hosted instances have no node limits.
- Retention. Every account keeps 90 days of snapshot history, hosted and self-hosted alike. It is enforced by a ClickHouse table TTL, so a self-hosted operator can change the window on their own instance.
- AI analysis. Enabled on hosted accounts; a self-hosted instance enables it by pointing
LLM_API_URLat any OpenAI-compatible endpoint.
The 402 pro_required response documented here previously is no longer returned by any endpoint. The only quota-shaped error a hosted account can hit is the 10-node cap on POST /api/v1/servers.
#Existing keys and integrations
Historical gmk_acct_live_ account keys keep working unchanged, with the same scopes they were minted with. No integration changes are required; code that handled 402 responses simply never sees them anymore.