Panicly is an operational control layer for model traffic, not a replacement for provider agreements.
These terms summarize the operational expectations around routing, workspace ownership, and billing boundaries for a Panicly deployment.
Workspace responsibility
You are responsible for the provider accounts, prompts, models, and downstream product traffic routed through your Panicly workspace.
Gateway controls
Panicly applies the limits, model policies, and emergency controls configured in your workspace before forwarding approved traffic upstream.
Billing expectations
Panicly plan billing is separate from provider usage charges. Upstream model providers may continue to charge for requests that Panicly forwards successfully.
Availability and response
Because Panicly sits on the critical path for model traffic, you should review workspace settings carefully before enabling production workloads and Sentry Mode controls.