Why governance is a Relay feature, not an afterthought
When a team uses hosted models against company code, you need a shared answer for which models are allowed, how much a workspace can spend, and where inference runs. Relay puts those controls on the workspace.
Model allowlists
Limit VG Code to an approved subset of the Relay catalog. Configure this from Vibgrate Cloud → Settings → Billing → Credits.
Spend protection
Prepaid credit is the hard stop: a request cannot start if the estimated cost exceeds the available balance. Workspaces can also set an optional monthly spend ceiling and a max share of balance per request under Settings → Billing → Credits. When daily spend is well above the trailing 7-day average, owners get an anomaly alert (once per day). See Pricing & credits for reserve → serve → settle and the full protection list.
Residency pinning
Org-level residency pinning lets an organization constrain where its Relay requests are served, consistent with Vibgrate Cloud's broader data-residency posture. Confirm current residency guarantees against your account before relying on a specific region for a compliance requirement — data residency for Relay tracks the same jurisdiction-isolation work as the rest of Vibgrate Cloud, and is not universally available in every region yet.
Audit trail
Every balance change — a debit, a refund, a grant, an expiry — is written to Vibgrate's cross-cutting audit event stream with a correlation id and no secrets, so a SIEM export or compliance search sees Relay activity alongside every other billing event without a special case. Enterprise credit-limit changes are a reviewable lifecycle action with an approval record, never a plain dashboard toggle.