Why governance is a Relay feature, not an afterthought
The moment more than one person on a team uses a hosted model against company code, someone has to answer: which models are we allowed to send code to, how much can any one workspace spend, and where does inference actually run. Relay centralizes those controls at the workspace/org level instead of trusting every individual seat to self-police.
Model allowlists
An org can restrict VG Code to a curated subset of the Relay catalog rather than every model Relay offers — useful when a security or compliance review has only cleared specific providers or model families for use against your codebase. Configure this from Vibgrate Cloud → Settings → Billing → Relay.
Spend caps
Beyond individual auto top-up limits, a workspace can set:
- A hard monthly spend ceiling, enforced at the same atomic point as the balance check itself — a workspace that sets a $500 cap cannot spend $501 no matter what an automated agent attempts.
- A per-request ceiling, so a single pathological prompt can't reserve an outsized share of the balance in one call.
- Anomaly alerts, emailing the workspace owner when spend far exceeds the trailing 7-day average, while it's happening.
See Pricing & credits for the full spend-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.