Per-tenant cap
Top-level ceiling so one tenant cannot burn another's budget.
Quotas & rate limits
Spend budgets you can see.
Per-tenant, per-event quotas with warning and critical thresholds. Alerts fire before you hit the wall. No more reading vendor invoices to understand who used what.
The knobs
Four numbers per tenant. That's it.
The configuration surface is intentionally small: a cap, a warning, a critical line, and the unit of measurement. Status colours on the dashboard are load-bearing — green, amber, red mean exactly that.
Per-event cap
Send 1,000 password resets a day, 100,000 marketing emails — independently.
Warning threshold
An alert fires when usage crosses 70%. Hook it into the channels your on-call already watches.
Critical threshold
At 90% the platform throttles instead of blowing through. Soft-fail with a clear reason.
What you avoid
The surprises operators dread.
- No more "our SMS bill is suddenly 4× higher this month" postmortems.
- No one tenant exhausting the shared provider budget the rest of the platform depends on.
- No silent over-sends because the throttle is upstream of the provider, not at it.
More platform features
Keep exploring.
Routing engineStrategies, IF/ELSE rules, failover chains, retry with backoff. All configured, never coded.TemplatesHandlebars-style syntax with conditionals, loops, and helpers. Multi-language.Multi-tenancyRepository-level isolation per tenant. Per-tenant providers, audit, quotas.Audit trailEvery event and every admin action, per tenant. PII redacted at the field.ObservabilityEvents per minute, delivery rate, p95 latency, per-provider health, live.Agent CLIThe Nemofy skill installs in Claude Code, Codex, Cursor, OpenCode, Aider.