Norcube CLIBackup, Monitor & 2 more: Backup, Monitor, LangSync, DomainRadar

The Norcube platform, in your terminal

Back up, monitor, translate and check domains without leaving your terminal. Sign in once in the browser, and script everything with JSON output and clear exit codes.

macOS · Linux · WindowsTokens in your OS keyringOne-command upgrades

Install in one command

Pick your platform. Every install is the same single binary, and one command keeps it up to date.

macOS and Linux. Installs the binary plus bash, zsh and fish completions.

  1. 1

    Install the cask:

    brew install --cask norcubeplatform/tap/norcube
  2. 2

    Sign in. Your browser opens the Norcube sign-in page:

    norcube login

One CLI, one sign-in

Each product has its own command namespace. The binary, the sign-in and the upgrade path stay the same.

Account and organizations

Sign in through your browser, switch organizations and keep separate profiles.

Account and organizations

Sign in through your browser, switch organizations and keep separate profiles.

nrc login, nrc whoami and nrc org list / switch / create. Sign-in happens in your browser and gives the CLI its own session, stored in your OS keyring (Keychain, Secret Service or Windows Credential Manager). Named profiles (nrc --profile client-acme …) keep separate accounts and organizations apart, each with its own sign-in. Over SSH or on a server, nrc login --device signs in with a code you approve in any browser, your phone included.

Backup

Back up now, restore-test, restore and download, and gate your CI on the result.

Backup

Back up now, restore-test, restore and download, and gate your CI on the result.

Add data sources, create and attach policies, run a backup now and list every backup job. Restore a backup into a new database, a new server or over the original, download any backup straight into pg_restore or mongorestore, and run restore tests on demand or on a schedule. A restore test with --wait fails the pipeline when a backup doesn't restore.

Details on the Backup CLI page

Monitor

Create and run monitors, follow incidents and fail a CI job while something is down.

Monitor

Create and run monitors, follow incidents and fail a CI job while something is down.

Create, pause and run HTTP, SSL certificate and domain expiry monitors, and read their check results, uptime, response times and certificates. List, inspect and acknowledge incidents, and manage alert channels (email, webhooks, Slack, Discord and SMS). In CI, nrc monitor status --fail-on critical fails the job while a critical incident is open, and nrc monitor monitors run <monitor> --wait fails it when the check finds the monitor down.

Details in the CLI reference

DomainRadar

Check one domain or 100,000 in bulk, then export the results.

DomainRadar

Check one domain or 100,000 in bulk, then export the results.

Check domains with nrc domainradar check, or pipe a list of up to 100,000 into nrc domainradar bulk create and watch the results stream in, then export them as CSV or JSON. Saved domains, brand watchers and their hits, and the name generator are there too.

Details in the DomainRadar CLI docs

LangSync

Sync your i18n JSON files with LangSync and let AI fill the gaps.

LangSync

Sync your i18n JSON files with LangSync and let AI fill the gaps.

Namespaces, terms, translations, custom prompts, the glossary and its languages, API keys, CSV import (wait for it to finish, or check on it later) and the audit log, plus project-level langsync init and langsync sync for the translation files in your repo. Sync keeps i18n/<lang>.json in step with the server, including per-developer source-language overrides.

Details on the LangSync CLI page

Billing

Usage, estimates, invoices and spending caps, readable by a CI token.

Billing

Usage, estimates, invoices and spending caps, readable by a CI token.

See whether the account is in good standing, this month's usage and estimate per metric, your subscriptions and invoices, download invoices as PDF and set monthly spending caps and alert thresholds. A CI token with billing.read can run every read command.

Details in the Billing docs

Other products

PromptHub commands come later, in the same binary.

Three guarantees, every command

Tokens in your OS keyring

Tokens live in your system keyring, one session per profile. Without a keyring the CLI says so and uses a file only you can read. Signing out removes them.

Browser sign-in

You sign in through your browser. Without one, the CLI gives you a code to approve on your phone. Your password never touches the CLI.

One-command upgrades

One static binary per platform. A single command fetches the latest release, verifies its checksum and replaces it, no sudo needed.

Common questions

What's the difference between the CLI and the dashboard?
They use the same backend and the same account. The dashboard is visual and interactive; the CLI is scriptable, with JSON output on every command, and fits into makefiles, scripts and editor integrations. Most teams use both.
How do I use its output in scripts?
Every command takes -o json, -o yaml or -o text (tab-separated, for cut and awk), and --query picks out what you need with a JMESPath expression, for example nrc backup jobs list -o json --query "[?jobStatus=='failed'].jobId". Results go to stdout while progress and prompts go to stderr, so pipes stay clean. Exit codes tell a script what went wrong: 1 when a job it waited for failed, 3 for not found, 4 for signed out, 5 for missing access. Details are in the CLI docs.
What if a command fails?
nrc doctor checks your config, profile, session, clock and the connection to every Norcube service, and tells you which one is the problem. Add --debug to any command to see each HTTP request and response with credentials redacted. For an endpoint the CLI has no command for yet, nrc api calls it with your sign-in. Details are in the CLI docs.
Where does the CLI store my session?
In your operating system's keyring (macOS Keychain, Linux Secret Service, Windows Credential Manager), one entry per profile. If a machine has no keyring, the CLI tells you once and stores the session in a file readable only by your user. Access tokens are short-lived and refresh automatically, and nrc logout (or nrc logout --all) removes the stored session. Read more about our security model.
How do I sign a machine out?
Run nrc logout on it, which also ends the session on our side. To sign out a machine you can't reach, open Account → CLI sessions in the dashboard: it lists every device signed in to the CLI, with when it was last used, and lets you revoke any of them. Sessions you don't use for 30 days end on their own.
Can I use it in CI?
Yes, with a CI token. Create one under IAM › CI tokens in the dashboard or with nrc auth ci-token create, give it only the scopes the job needs (for example langsync.sync), and store it as the secret NORCUBE_TOKEN. A CI token belongs to the organization, not to a person, so it keeps working when whoever created it leaves; it always expires and you can revoke it at any time. On GitHub Actions, setup-norcube installs the CLI and passes the token in one step. For backups, see Back up your database in CI. Details are in the CLI docs.
Can I sign in over SSH or from my phone?
Yes. nrc login --device prints a short code and a link (and a QR code when the terminal fits one). Open the link in any browser, check that the code matches and approve; the CLI finishes on its own. The approval page shows which machine is asking, from where and when, so only approve sign-ins you started.
Which language is it written in?
Go. The source is at github.com/norcubeplatform/cli under the Apache 2.0 license. The API clients are generated from each service's API spec, and the command reference is generated from the CLI's own help text.
Does it work offline?
No. Every command talks to the platform. nrc langsync sync --dry-run asks the server for a plan and changes nothing, so it's the safe way to preview a sync.

Install the Norcube CLI

One command with Homebrew or the install script on macOS and Linux, a zip on Windows. nrc upgrade keeps it current.

  • macOS · Linux · Windows
  • Keyring tokens
  • Apache 2.0
  • One-command upgrades
// tick. tick. tick.
0 ticks since founding
Coming soon

Join the PromptHub waitlist

PromptHub is in active development. Leave your email and we'll invite you as soon as it opens, with a free tier and no credit card.

One email when access opens. No newsletter, no spam.