Infrastructure and Billing
NOME Cloud, Sovereign BYOK, Enterprise VPC, credits, and cost management.
NOME Cloud vs Sovereign BYOK vs Enterprise VPC
NOME Cloud — subscribe and receive NOME Credits. We handle API negotiations, rate limiting, visible failover policy, and billing. One subscription, all models included.
Sovereign BYOK — connect your own API keys from any supported provider. NOME provides the interface, memory, routing, and orchestration. You pay providers directly.
Enterprise VPC — dedicated backend instances with enterprise SSO, tenant isolation, custom SLAs, and Nome-owned policy control.
API key setup for all providers
NOME supports keys from major frontier model providers. Each key is validated on entry with real-time provider status checks.
Keys are stored with encrypted persistence. Provider rotation, BYOK passthrough, and credit ledger tracking are built in.
NOME Credits: pricing and metering
NOME Credits are the canonical billing unit for cloud infrastructure usage. Credit summaries include total balance, available credits, usage this period, and included monthly allocation.
Tasks run on-device using local models consume no credits. BYOK mode routes to providers from your machine with no Nome credits consumed.
Token normalization across providers
Different providers use different tokenization strategies and pricing models. NOME normalizes token counts into comparable metrics across providers, enabling fair cost comparison and budget-aware routing.
The telemetry dashboard shows input and output tokens for each provider simultaneously, with normalized cost-per-token equivalents.
Rate limit management and failover
When one provider approaches its rate limit, NOME Cloud can move platform-managed overflow across a configured redundant provider only when the run policy allows it. The selected route, provider change, and cost lane remain visible in receipts.
Rate-limit enforcement spans platform, gateway, and access policy layers. User-pinned seats, BYOK keys, and specific model picks fail closed if that selected route cannot run.
Cost-aware routing policies
NOME tracks cumulative token cost per run and surfaces it as a first-class metric. Run mode respects cost budgets defined on the run.
Administrators can define per-department routing policies that control which teams access premium models vs cost-effective tiers. Identity meets cost governance.
Ready to try it?
Open NOME