Model-spend caps
Set hard USD limits with 1-day, 7-day, 30-day rolling, or calendar-month windows and an optional lower soft threshold.
GD
Cost & rate guardrails
BetaSet limits before usage runs away.
NovaGuard configures organization- and project-scoped model-spend caps plus request and token rate limits. Your connected application or gateway fetches the effective policies, enforces BLOCK decisions, and reports usage events back to Noveum. Now in beta.
2
policy types
Org + project
policy scopes
Beta
design-partner program
NovaGuard · policy engineBETA
org_cost_cap · 30d rollingBLOCK
project_cost_cap · calendar monthBLOCK
request_limit · 1 minuteBLOCK
token_limit · 1 dayBLOCK
Saved policies require a connected application or gateway to enforce them
01: Capabilities
Practical controls for model spend and traffic.
Request limits
Cap request counts over one-minute, one-hour, or one-day windows for the organization or an individual project.
Token limits
Limit input and output token volume over the same minute, hour, or day windows used for request controls.
Organization or project scope
Create organization-wide defaults and project-specific policies; the effective-policy endpoint resolves the applicable set.
Fail-closed choice
Record whether an enforcing client should fail closed when it cannot obtain the policy state, alongside enabled state and priority.
Usage & block events
Connected clients report allowed usage to update policy state and report blocked decisions that can trigger an owner alert.
02 - How it works
Configure. Enforce. Report.
Noveum manages policy state; your application or gateway owns the request-path decision.
01
Configure limits
Create cost-cap or rate-limit policies, choose organization or project scope, and set the relevant windows and thresholds.
02
Enforce in the data plane
A connected application or gateway fetches the effective policies, maintains hot-path counters, and applies the supported BLOCK action.
03
Report decisions
The enforcing client sends allowed-usage and blocked events back to Noveum so counters stay current and blocked decisions can trigger an owner alert.
NovaGuard is in beta. Policy configuration alone does not intercept traffic; production blocking requires integration with your application or gateway.
Join the beta03: Under the hood
The control plane and enforcement boundary.
NovaGuard exposes policy and usage APIs for cost and rate controls. Request-path enforcement remains in the connected data plane.
Policy API
Create and update COST_CAP or RATE_LIMIT policies with enabled state, priority, scope, fail-closed preference, and the supported window configuration.
Effective policy set
A dedicated endpoint combines applicable organization-wide and project-specific policies for clients to fetch, with an ETag for efficient refreshes.
Supported action
Current cost-cap and rate-limit policies use one hard action: BLOCK. Content moderation, rewrite, retry, and human escalation policies are not part of this beta.
Enforcement boundary
The Noveum API stores and resolves policy state; your connected runtime or gateway evaluates counters and blocks calls before provider usage.
Usage reports
The project usage endpoint accepts allowed and blocked events with cost, tokens, request count, model, timestamp, and optional policy and reason context.
Access & deployment
Organization access controls protect policy management, and the broader Noveum platform supports managed cloud and enterprise deployment options.
The loop
Part of one closed loop.
NovaGuard adds spend and traffic limits alongside the quality loop. It does not replace NovaEval, and production enforcement depends on your connected data plane.
Team-owned change
Review and deploy ↺
NovaGuard (beta) - Cost and rate policies for a connected data plane to enforce
Trusted in production by enterprise and high-growth teams