Setting spend caps and controls

Why caps matter

Credits come out of one shared pool and generation can spend fast, so Pinnora gives you three controls to fence spend inside a boundary you set. All three live around the Usage and team views on the organisation home. Set them up once and they work like a circuit breaker: quiet in the background until the day they save you.

The hard spend cap

The hard credit limit is a ceiling on how many credits the org can spend. Set it, and generation stops the moment spend reaches that number, which protects you from a runaway batch or a loop quietly draining the balance. Each plan has a maximum ceiling you can set, so the cap is yours to tune within the plan's range. On the Free tier that ceiling matches the 10 welcome credits.

The spend pause

The spend pause is a manual switch. Flip it on and the org stops spending credits until you flip it back off. It is the fastest way to freeze everything at once, say, the moment you spot unexpected spend and want to look before anything else runs.

Per-member caps

On top of the org-wide controls, you can set a monthly credit cap for each member. This lets you give a teammate real access to generation without handing them the whole pool. They hit their own cap and stop while the rest of the org keeps working. Member caps are set alongside roles and project scope in the team view.

Who sets them

Spend controls are part of billing and org management, so they sit with owners and admins depending on the action. Plan them with the same care as roles. A good cap is the backstop that turns we might overspend into we cannot spend past this number.