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.
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
Install the cask:
brew install --cask norcubeplatform/tap/norcube - 2
Sign in. Your browser opens the Norcube sign-in page:
norcube login
macOS and Linux. Installs to ~/.norcube/bin with the short nrc alias, so upgrades never need sudo.
- 1
Run the installer. It checks the download's SHA-256 against the release's
checksums.txtbefore installing:curl -fsSL https://github.com/norcubeplatform/cli/raw/main/install.sh | sh - 2
If the script tells you
~/.norcube/binisn't on yourPATH, add it to your shell profile:export PATH="$HOME/.norcube/bin:$PATH" - 3
Sign in:
nrc login
- 1
Download the
.zipfor Windows from the latest release and extractnorcube.exeto a folder on yourPATH. There's no installer yet. - 2
Sign in:
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.
Backup
Back up now, restore-test, restore and download, and gate your CI on the result.
Monitor
Create and run monitors, follow incidents and fail a CI job while something is down.
DomainRadar
Check one domain or 100,000 in bulk, then export the results.
LangSync
Sync your i18n JSON files with LangSync and let AI fill the gaps.
Billing
Usage, estimates, invoices and spending caps, readable by a CI token.
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?
How do I use its output in scripts?
-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?
nrc logout (or nrc logout --all) removes the stored session. Read more about our security model.How do I sign a machine out?
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?
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?
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?
Does it work offline?
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
Products the CLI talks to
Each product page goes deeper. The CLI is one more way in.