Skip to main content

Novavision CLI

NovaVision CLI offers an interface for managing servers and applications locally. It allows you to register and install a server, deploy, and manage an app using Docker Compose.

NovaVision simplifies the process of setting up and managing servers, allowing you to deploy and run applications on edge, local, and cloud servers.


Installation

Install NovaVision CLI with pip:

pip install novavision-cli

# Verify installation
novavision --version

pipx is optional. Use it if you want the CLI in an isolated environment:

pipx install novavision-cli

Features

install

Performs creation and installation of a device on your system.

novavision install [edge|local|cloud] <USER_TOKEN> --host <HOST> --workspace <USER_WORKSPACE_NAME> --port <PORT> --non-interactive

Parameters

  • DEVICE_TYPE: Specifies the server type. Options: edge, local, or cloud.
  • USER_TOKEN: User token required for registering and installing the server.
  • --host: Suite host URL. Default: https://suite.novavision.ai (or host in ~/.novavision/config.json). Common values: suite.novavision.ai, alfa.suite.novavision.ai.
  • --workspace: User can specify which workspace will be used for creating device. User must type the name of the workspace they have. If this parameter is not entered, workspace selection will be performed while device creation.
  • --port: Server API port. Skips the port prompt when set.
  • --non-interactive: Skip prompts. Requires --workspace. Uses port 7001 if --port is omitted. Fails instead of asking which device to delete when the account is at its device limit.

self-update

Upgrades this CLI from PyPI. A pip install upgrades with pip. A pipx install upgrades with pipx upgrade.

novavision self-update

update

Downloads the latest server package for an existing server and rebuilds it.

novavision update server <USER_TOKEN> --id <SERVER_ID>

Parameters

  • USER_TOKEN: User token required to download the server package.
  • --id: Server folder ID, or the device ID stored in server metadata. If omitted, you will be asked to select a server.
  • --yes: Skip the update confirmation prompt.

uninstall

Stops a local server, deletes the registered device from Suite, and removes the local server folder.

novavision uninstall server <USER_TOKEN> --id <SERVER_ID>

Parameters

  • USER_TOKEN: User token required to delete the device on the host.
  • --id: Server folder ID, or the device ID stored in server metadata.
  • --yes: Skip the uninstall confirmation prompt.

Optional file ~/.novavision/config.json can set default "host" and "workspace" values for install.


list

Shows installed servers, whether they are running, and their apps.

novavision list
novavision list --json

status

Shows running state for a server and its apps. Omit --id to show every server.

novavision status
novavision status --id <SERVER_ID>

logs

Shows Docker Compose logs for a server or app.

novavision logs server --id <SERVER_ID> --follow
novavision logs app --id <APP_ID> --tail 100

start

Launches the server's or application's Docker Compose environment, starting the server or application if it isn’t already running.

novavision start [server|app] --id <ID>

Parameters

  • --id: Server folder ID when starting a server. Required App ID when starting an app.

The parent server must be running before starting an app.


stop

Stops the running server or application by shutting down its Docker Compose environment.

novavision stop [server|app] --id <ID>

Parameters

  • --id: Server folder ID when stopping a server. Required App ID when stopping an app.
  • --close-apps: When stopping a server, also stop apps belonging to that server.

The parent server must be running before stopping an app.


service

Enables, disables, or shows status for automatic server startup.

novavision service [enable|disable|status] server --id <SERVER_ID> --apps <APP_ID>

Parameters

  • --id <SERVER_ID> (Optional): Specifies which server to manage. If omitted, you will be asked to select one.
  • --apps (Optional, enable only): App IDs to start after the server. Use "*" to start all apps.

Linux requires sudo. Windows requires an Administrator terminal. On macOS and Windows, Docker Desktop must start automatically.

Global flags: -q / --quiet, --json (for list and status), --no-color (also honors NO_COLOR).

Metadata

Release files for novavision-cli 0.1.8

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for novavision-cli 0.1.8
File Size Uploaded
novavision_cli-0.1.8.tar.gz 85.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for novavision-cli 0.1.8
File Interpreter ABI Platform
novavision_cli-0.1.8-py3-none-any.whl Python 3 none any Details

Total release size: 151.7 kB

Release files / novavision_cli-0.1.8.tar.gz

Download URL novavision_cli-0.1.8.tar.gz
Size 85.6 kB
Tags Source
SHA-256 checksum
How to use checksums
3eb50bfeffafe17de709d04c4c0bc581cc0d63dfa46b6900c7634ccca95541df
BLAKE2b-256 checksum
How to use checksums
11560bc84d2f5f8111939dd98ed192679a6961785a9cd00970dd46ad5cbafeef
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.

Transparency log

Release files / novavision_cli-0.1.8-py3-none-any.whl

Download URL novavision_cli-0.1.8-py3-none-any.whl
Size 66.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a35a6960f41eb6b1cc39ee3bb3d6261e4307c90dbf6bbc8df5ed950aa76f402e
BLAKE2b-256 checksum
How to use checksums
cfe16144fb08fbef77a0cdd5e675c06ea1c048e4ab8e0ac0b99bf1ad9fcce0f6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.8 This release

2 release files

0.1.7

2 release files

0.1.6

2 release files

0.1.5

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

0.0.9

2 release files

0.0.8

2 release files

0.0.7

2 release files

0.0.6

2 release files

0.0.5

2 release files

0.0.4

2 release files

0.0.3

2 release files

0.0.2

2 release files

0.0.1

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page