Core concepts
Panicly is a spend-control gateway. The important objects are workspaces, projects, Panicly keys, provider keys, policy controls, request evidence, and usage capacity.
The top-level operator boundary. It owns plan tier, members, projects, billing state, credits, audit events, and global controls.
A protected unit of traffic inside a workspace. It owns environment, Panicly API keys, provider connection, thresholds, and request history.
The credential your app sends to Panicly. Keys are project-scoped, returned once, and use environment-aware prefixes such as pk-dev- and pk-live-.
The upstream provider credential Panicly uses for approved requests. A project can connect provider keys for supported providers, with one active key per provider.
The emergency stop control that pauses provider traffic for a project before it can create upstream spend.
Purchased capacity used after included monthly request volume is exceeded.
Preferred naming
Product names
Plans
Customer-facing language
Use Plus, Premium, Kill Switch, Network Controls, Region Rules, Requests, Usage, Credits, and Workspace Audit when describing Panicly.