Norcube CLI · single binary, every product

The whole Norcube platform, in your terminal

Q: Which language is it written in?

Go. The repo is at [github.com/norcubeplatform/cli](https://github.com/norcubeplatform/cli), MIT-licensed. The client packages live in `internal/api/ /` and are generated from each backend service’s Swagger spec.

Q: Does it work offline?

Some commands do (anything that operates on local state — `nrc langsync sync --dry-run` against an existing config, for example). Anything that touches the platform needs a network. The auth flow caches access tokens, so quick repeated commands stay snappy.

`norcube` (alias `nrc`) is the command-line client for the platform. Browser-based login, OS-keyring tokens, one binary, every Norcube product reachable without leaving your shell. Manage backups, sync translations, switch organizations, and more — without a browser tab in sight.

Install the CLI See the source →

macOS · Linux · Windows OS-keyring tokens OAuth loopback login Single binary, no deps Auto-update built in

What it does

One CLI, every product

Each Norcube product has a top-level command namespace. New products grow new namespaces — the binary and the auth flow stay the same.

Account & organizations

`nrc login`, `nrc whoami`, `nrc org list / switch / use`. Browser-based OAuth login mints an independent CLI session, stored in your OS keyring (Keychain, Secret Service, Windows Credential Manager). Multi-org users switch with a single command.

SnapDB (Backup)

Browse and manage SnapDB data sources, list backup jobs across the org, pause and resume policies. Backup download and restore commands land once the SnapDB endpoints ship.

LangSync

Full namespace and term CRUD plus project-level `langsync init` and `langsync sync` for repo-side translation files. The CLI keeps your `i18n/<lang>.json` files in lockstep with the server, including per-developer source-language overrides.

Details on the LangSync CLI sub-page →

Coming next

PulseCheck, DomainRadar, and PromptHub command namespaces are on the [public roadmap](/roadmap/). New product namespaces ship alongside the products themselves; one install, one upgrade path, every product.

how it works

Three guarantees, every command

principle 01

OS-keyring tokens

Refresh and access tokens live in your operating system keyring, not in a dotfile. Logging out clears everything. Logging in on a new machine mints an independent session.

principle 02

OAuth loopback login

`nrc login` opens your browser, you sign in, the CLI receives a session over a one-shot localhost callback — the same pattern `gh auth login`, `flyctl auth login`, and `stripe login` use. Your password never touches the CLI.

principle 03

One binary, auto-upgrade

A single static binary per platform. `nrc upgrade` checks GitHub releases, verifies the SHA-256 against the signed checksums file, and atomically replaces the running binary. Per-user install path, no sudo needed.

FAQ

Common questions

What is the difference between the CLI and the dashboard?

They share the same backend and the same account. The dashboard is interactive and visual; the CLI is scriptable and fits into CI, makefiles, and editor integrations. Use whichever fits the task — most teams use both.

Where does the CLI store my session?

Refresh tokens live in your operating system keyring (macOS Keychain, Linux Secret Service, Windows Credential Manager). The CLI never writes secrets to dotfiles. Access tokens are short-lived and refreshed automatically. Logout removes the keyring entry. Read more about our security model.

Can I use it in CI?

Personal Access Tokens (paired with a backend revocation table) are on the roadmap. Until then, the recommended pattern is a long-lived CI account that completes the browser flow once on a developer machine and exports the keyring secret into your CI vault.

Which language is it written in?

Go. The repo is at github.com/norcubeplatform/cli, MIT-licensed. The client packages live in internal/api/<service>/ and are generated from each backend service’s Swagger spec.

Does it work offline?

Some commands do (anything that operates on local state — nrc langsync sync --dry-run against an existing config, for example). Anything that touches the platform needs a network. The auth flow caches access tokens, so quick repeated commands stay snappy.

Products the CLI talks to

Each product page has its own deep dive. The CLI just gives you another way in.

Backup

Install the Norcube CLI

One curl command on macOS or Linux. Pre-built binaries on Windows. Auto-updating from there.

Install via the README Sign in to the dashboard

macOS · Linux · Windows Single static binary

OS-keyring tokens Never in dotfiles

MIT-licensed Public source on GitHub

Auto-update `nrc upgrade` does it