Surface · CLI
One command to live
npx novence deploy ./dist uploads the directory, runs the quality gate, publishes to the edge, and prints the URL. Same control plane as REST, GraphQL, and MCP.
Start
npx novence deploy ./dist Created project site (abcd1234) Uploaded 12 files Checks passed https://abcd1234.novence.ai/
No install needed. Node 18+. With no directory it auto-detects dist, build, out, public, or _site. The first run asks for an email and a 6-digit code, then stores the key in ~/.novence/credentials.
Commands
| Command | What it does |
|---|---|
novence deploy [dir] | Upload, check, publish, print the live URL |
novence open [project] | Open a project's live URL |
novence checks [project] | Lighthouse, axe, and link results for the last deploy |
novence domains add <host> | Attach a custom domain and print the DNS records |
novence domains status | Custom domain state |
novence keys list | API keys on the account |
novence keys revoke <id> | Revoke a key |
novence projects | List projects and their URLs |
novence login | Sign in, verify email, or recover a key |
novence whoami | Plan, verification, and usage against quota |
Unknown flags are rejected and the valid ones listed, so a typo fails loudly instead of silently changing what you deployed.
CI & agents
Progress goes to stderr and the live URL is the only thing on stdout, so it pipes cleanly. Set NOVENCE_API_KEY and pass --no-input so nothing ever prompts. Failures exit non-zero.
URL=$(npx novence deploy ./dist)
# machine-readable, for agents and pipelines
npx novence deploy ./dist --json --no-input
# → { "ok": true, "url": "https://…", "files": 12, "checks": { "passed": true } }Key lookup order: NOVENCE_API_KEY, then ./.novence-key, then ~/.novence/credentials. Never commit a key.
FAQ
Do I need to install anything?
No. npx novence deploy ./dist runs the current version without installing. Use npm install -g novence if you would rather have it on PATH. Node 18+ is required.
Do I need an account before the first deploy?
The first run asks for an email and a 6-digit code, then stores the key in ~/.novence/credentials (mode 0600). After that deploys are one command. There is no dashboard to sign up for.
How do I use it in CI?
Set NOVENCE_API_KEY and pass --no-input so the CLI never prompts. Add --json for a machine-readable envelope. Any failure exits non-zero, so a failed deploy fails the build.
Where does it look for my API key?
NOVENCE_API_KEY first, then ./.novence-key in the working directory, then ~/.novence/credentials. Never commit a key — it is a server-side credential.
Can I script around it?
Yes. Progress goes to stderr and the live URL is the only thing on stdout, so URL=$(novence deploy ./dist) captures exactly the URL. Every command also accepts --json.
What if I mistype a flag?
The CLI rejects unknown flags and lists the valid ones. A typo like --nmae fails loudly instead of silently deploying under the default project name.
Ship with Novence
One command from a build directory to a live URL. API at https://api.novence.ai.