Billing

Norcube bills usage, with no seats. LangSync and DomainRadar have a monthly free-tier allowance on every metric and no commitment. Backup is billed by plan: a flat monthly fee that includes some usage, with usage above it billed per unit, and a $0 Free plan. Usage accrues during the month, becomes an invoice on the 1st of the next month, and is charged to your organization's default card.

What each product meters

Product services report usage to billing continuously (collected every few minutes), so the dashboard numbers track reality closely.

Watching the month: Billing home

Billing (in the application switcher, under Manage) shows this month at a glance:

• Current usage — accrued so far, with days elapsed.
• Billing estimate — the projected month-end total.
• Billing period — which month, and when it closes.
• Billing currency — the currency your invoices are issued in (USD, CZK, or EUR per organization; set it up with support).
• A cumulative usage chart — "today's actual vs the month-end projection."

Free tier: per-metric drill-down

Billing → Free Tier breaks the estimate down per billable metric: "Where you are this month against the free quota for each billable metric. Rows flagged in red are on track to incur charges."

Each row shows the metric, its product, current usage, the free-tier quota, the end-of-month projection, and last month's usage — with a search box, a per-service filter, and a "Projected to overflow" toggle that isolates the rows that will cost money. This page is the answer to "why is my estimate not zero?". Backup isn't listed here: its included usage is part of your plan, shown on Backup's Plan & usage page.

If you're on track to incur charges but haven't finished billing setup (card + billing details), Norcube emails you a heads-up mid-month rather than surprising you at invoice time.

The month-end cycle

1. 1st of the month: an invoice is generated from the previous month's metered usage: plan fees prorated for the days you were on a plan, usage above what your plan includes, and free tiers and any credits applied.
2. Charging runs automatically against the org's default payment method — once your billing preferences are complete.
3. Failures enter the dunning flow — a 14-day full-access grace window before anything is blocked.

Invoice statuses, PDFs, preferences, and credits: Invoices, preferences, and credits.

From the CLI

The CLI reads the same numbers (CLI 0.20 and later):

nrc billing status                 # active, grace (until when) or blocked
nrc billing usage estimate         # this month so far, and the projected total
nrc billing usage metrics          # the Free Tier page: usage, quota, projection per metric
nrc billing subscriptions list     # how each service is billed, and its current plan
nrc billing invoices list
nrc billing budget get

usage metrics marks metrics on track to exceed their free tier with OVER, the CLI's version of the Projected to overflow toggle:

nrc billing usage metrics -o json --query "[?overflowProjected].metricCode"

Every read command works with a CI token that carries the billing.read scope, so a scheduled job can watch the estimate or collect invoices. Plans and payment methods are changed in the dashboard; the only change the CLI makes is the budget, and that needs a person signed in. Every command and flag is in the CLI reference.

Related