# Install triton with Homebrew, Nix, apt Joyent Triton CLI. Version 7.18.0 via Homebrew; verified from local package data. Also installable with nix: nix profile install nixpkgs#triton. ## Install ```sh sudo av install brew:triton ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install triton ``` Evidence: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#triton ``` Evidence: nixpkgs package indexes: pkgs/by-name/tr/triton/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - Ubuntu apt (92%): ```sh sudo apt install python3-triton ``` Evidence: Ubuntu 24.04 LTS package indexes: python3-triton from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz ## Package facts - **Package key:** brew:triton - **Package manager:** Homebrew - **Version:** 7.18.0 - **Source summary:** Joyent Triton CLI - **Homepage:** - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - triton (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 7.18.0 ## Project history and usage The `triton` package is the Node.js command-line client for Triton DataCenter CloudAPI. It belongs to the Joyent/MNX Triton ecosystem, a SmartOS-based cloud management platform formerly known as SmartDataCenter. ### Project history Triton DataCenter presents itself as the successor name for SmartDataCenter and describes the platform as open-source cloud management for container-based, service-oriented infrastructure across one or more data centers. The main Triton README says a deployment runs SmartOS, has management and compute nodes, and exposes APIs, an operator portal, private services, and agents. The node-triton README places the CLI in that larger system: it is part of the Triton Data Center project and works with CloudAPI for both public and private Triton clouds. It also documents the transition from the older `node-smartdc` tooling, saying `triton` was intended to expand command coverage and eventually replace `node-smartdc` as both API client library and command-line tool. ### Adoption history The source-backed adoption story is narrower than a general-purpose cloud CLI: it is used by Triton public-cloud users and private-cloud operators who need scripted access to accounts, instances, networks, images, and packages through CloudAPI. Official docs show the CLI managing profiles for different data centers and users, and comparing Triton CLI commands with Docker commands on Triton Elastic Docker Host. Homebrew and npm distribution matter here because the client is a Node.js-era infrastructure CLI. The README's setup path is `npm install -g triton`, while the Homebrew formula gives macOS and Linux package-manager users a way to install the same cloud tooling without treating it as an application framework dependency. ### How it is used The documented workflow starts with Node.js installation and a Triton profile containing the CloudAPI endpoint URL, account login, and SSH key fingerprint. Users then run commands such as `triton profile create`, `triton instance list`, `triton instance create`, `triton ssh`, `triton images`, and `triton packages` to operate cloud resources. Triton documentation also explains the relationship between Docker API access and CloudAPI/Triton CLI access: Docker commands can manage Docker containers on Triton, while the Triton CLI manages infrastructure containers, hardware VMs, images, networks, packages, and account-level details through CloudAPI. ### Why package nerds care For package nerds, `triton` is a fossil and a useful map at the same time: it captures the Joyent SmartOS/Triton cloud-management world in a package-manager-installed CLI. It is most interesting when tracking old and still-maintained infrastructure clients, Node.js CLIs shipped through multiple packaging systems, and command-line tools tied to a specific cloud platform rather than a broad public-cloud market. It also illustrates a common packaging pattern for infrastructure tools: official docs center npm because the implementation is Node.js, but Homebrew packages it as a first-class executable for operators who expect `brew install` to populate their CLI toolbox. ### Timeline - SmartDataCenter era: Triton DataCenter README identifies Triton as formerly SmartDataCenter/SDC. - node-smartdc era: node-triton README documents `node-smartdc` as the older CloudAPI CLI. - Triton CLI beta era: node-triton README says `triton` was being expanded to cover CloudAPI commands and eventually replace node-smartdc. - Current docs: Triton CLI documentation covers profiles, CloudAPI access, instance management, Docker comparison, and data-center workflows. ### Related projects - Triton DataCenter, SmartDataCenter, SmartOS, CloudAPI, node-smartdc, Triton Elastic Docker Host, Manta ### Sources - - - - ## Security Notes narrow executable package without higher-risk signals. - **Geiger risk:** green / low - narrow executable package without higher-risk signals ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: ~/.triton/config.json - Windows: %APPDATA%/Joyent/Triton/config.json ## Other Package-Manager Records - Nix - triton: normalized package name match | nixpkgs package indexes: pkgs/by-name/tr/triton/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - Ubuntu apt - python3-triton - 2.0.0.post1-3ubuntu1: normalized package name match | Ubuntu 24.04 LTS package indexes: python3-triton from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | language and compiler for custom Deep Learning operations | https://github.com/openai/triton/ ## Combined YAML source View the package source record on GitHub. [combined/triton.yml](https://github.com/mxcl/pkgdb/blob/main/combined/triton.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph