Operational controls for production model traffic.

Panicly keeps budgets, routing decisions, Sentry Mode, Network Controls, Region Rules, and workspace evidence readable when model traffic turns expensive or unpredictable.

Request path

The request path stays short and inspectable.

Each request goes through the same policy sequence, then lands in Requests with enough context to explain the result.

1Authenticate key
2Load project rules
3Estimate request shape
4Apply rules
5Forward or block
6Write request record

Operator controls

Named control surfaces, not generic admin.

The core operator actions are explicit: stop traffic, block ingress, enforce geography, and keep a reviewable history of who changed the workspace.

Emergency stop

Sentry Mode

Hold live traffic before the provider call so the on-call engineer can stop spend while the incident is still moving.

Ingress controls

Network Controls

Review source addresses hitting the gateway and block unwanted networks without rotating provider keys or touching app code.

Geography

Region Rules

Apply IP-based country and regional restrictions before provider forwarding begins, so blocked traffic never becomes provider activity.

Operator record

Audit Log

Keep key changes, rule edits, Sentry Mode actions, and other operator changes reviewable in one workspace history.

Spend policy

Budget enforcement

Define spend and request ceilings by request, project, and workspace. Panicly checks them before forwarding traffic.

Model access

Model controls

Enable approved models per project and keep everything else disabled until a team member turns it on.

Evidence

Request evidence

Review route, model, provider, policy reason, token estimate, cost estimate, and sender details from one stream.

Ingress

Network Controls

Review sender addresses reaching the gateway and block unwanted sources across the workspace.

Geography

Region Rules

Block countries and regions before requests reach upstream providers.

Emergency stop

Sentry Mode

Arm a project-wide stop before provider traffic starts when spend, abuse, or provider behavior needs review.

Policy ledger

Policies that stay readable under pressure.

The operator can see the rule, the source, the spend context, and whether Sentry Mode intervened, so a blocked request is explainable without jumping across tools.

Open workspace
Request cost ceiling$0.50review
Monthly workspace budget$2,000review
Region ruleEUblock
Network source198.51.100.24block
Sentry Modearmedhold