A little context.
A clear next step.

One home for your extensions.

Rivetin 0.1.0 brings extension management, independent settings, lifecycle controls, an extension marketplace and operation logs into CloudTower. Functional settings are saved on the server; the browser stores personal interface preferences only.

The project is MIT licensed and independently developed. It is not an official SmartX product. Current extensions must be trusted and reviewed; fault isolation, publisher signatures, automatic configuration-schema migration and web-based framework self-update are not implemented.

Choose your client.

The portable client embeds SSH, HTTPS and installation resources. A released client does not require Node.js, Python, an external SSH program or kubectl on your computer. It does not change PATH, the registry or the system trust store.

The six platform targets below have local contract and cross-build coverage. The framework deployment has completed acceptance in one CloudTower 4.9.0 development/test environment; this does not establish live installation coverage for every client target. File names identify source build outputs, not public download links.

After obtaining a verified build through an authorized channel, keep its LICENSE, THIRD_PARTY_NOTICES.txt and SHA256SUMS alongside it. Verify the checksum before use. The examples use the selected platform’s executable; change its architecture or local path when needed.

rivetin help --lang en-US
rivetin version
rivetin licenses

npm run setup
npm test
npm run build
npm run package

node cli/scripts/prepare.mjs --go <GO_EXECUTABLE>

Check the exact build.

Two checks apply: the installer matches an exact Tower image and component layout; the framework checks an extension’s declared Tower build identifiers, framework API and optional framework-version range. A major release such as “4.9” does not establish compatibility.

This exact profile originated from historical installer validation. The coordinating project has completed a controlled Rivetin upgrade, state readback, child-plugin updates and limited read-only browser acceptance in its CloudTower 4.9.0 development/test environment. Fresh installation, uninstall and other client platforms were not revalidated in this round. That acceptance does not extend to other builds or production environments. A plugin declaration such as 4.9.0 is the version reported by Tower; it must not be interpreted as proof of that exact RC image or support for every 4.9.x build.

An empty towerBuilds list does not permit live installation or activation. Network Topology and Policy Converter currently have empty lists. Context Menu and Disk SMART now declare only 4.9.0, with the limited acceptance scope documented below. Do not add a guessed build to get past the gate.

Inspect first.
Install with a known target.

These are CLI reference examples, not a one-command public installer. Replace every placeholder and use a verified build only in an authorized environment. The connection options below match the current CLI help.

1. Prepare the connection.

   Use SSH access to the Tower VM with passwordless sudo, a Tower administrator account, and independently verified host trust. The SSH hostname and the Tower HTTPS hostname must match.

2. Verify certificates and keys.

   Use --ssh-hostkey for the known host fingerprint. --ca-file adds a private CA without changing system trust. The alternative --tls-cert-sha256 pins an independently verified DER leaf certificate and cannot be combined with --ca-file. There is no unconditional skip-verification option.

3. Run read-only preflight.

   detect, status and plan inspect the target over SSH. They do not deploy resources. An unknown build may be shown for diagnosis, but deployment remains blocked.

rivetin detect --ssh tower.example.invalid:22 --ssh-user <SSH_USER> --ssh-hostkey SHA256:<VERIFIED_HOST_KEY> --lang en-US
rivetin plan --ssh tower.example.invalid:22 --ssh-user <SSH_USER> --ssh-hostkey SHA256:<VERIFIED_HOST_KEY> --lang en-US

For installation, add the matching Tower HTTPS origin, administrator and certificate options. Passwords use non-echoing prompts; do not put passwords or private keys in command arguments, logs or website forms.

rivetin install --ssh tower.example.invalid:22 --ssh-user <SSH_USER> --ssh-hostkey SHA256:<VERIFIED_HOST_KEY> --tower https://tower.example.invalid --user <TOWER_ADMIN> --ca-file <CA_CERT_FILE> --lang en-US

The installer creates its own backend resources and registers the Rivetin Island. It does not patch official frontend files or restart official Tower services. It refuses unknown ownership instead of taking over an unmanaged deployment. Installation finishes globally disabled.

rivetin enable --ssh tower.example.invalid:22 --ssh-user <SSH_USER> --ssh-hostkey SHA256:<VERIFIED_HOST_KEY> --tower https://tower.example.invalid --user <TOWER_ADMIN> --ca-file <CA_CERT_FILE> --lang en-US

Enabling the framework does not enable an individually disabled extension or grant SSH collection rights.

Install. Configure. Enable.

The extension center separates the installed-plugin view from the marketplace. The marketplace only exposes published entries backed by real release assets, checksums and a nonempty declared build list. The current catalog contains a draft IPMI entry; no public installable market entry is available.

With an authorized package, upload its .rivetin.json file through the extension center or use the CLI. Installation verifies the package, identity, version, checksum and current compatibility. Installation and updates leave the extension disabled.

rivetin plugin list --ssh tower.example.invalid:22 --ssh-user <SSH_USER> --ssh-hostkey SHA256:<VERIFIED_HOST_KEY> --tower https://tower.example.invalid --user <TOWER_ADMIN> --ca-file <CA_CERT_FILE> --lang en-US
rivetin plugin install --package ./rivetin-ipmi-redirection-0.1.2.rivetin.json --ssh tower.example.invalid:22 --ssh-user <SSH_USER> --ssh-hostkey SHA256:<VERIFIED_HOST_KEY> --tower https://tower.example.invalid --user <TOWER_ADMIN> --ca-file <CA_CERT_FILE> --lang en-US

The package path above is a file-name example from the current source version. It is not a download link or an acceptance claim. Review the extension’s settings and compatibility before enabling it.

rivetin plugin enable --plugin-id rivetin-ipmi-redirection --ssh tower.example.invalid:22 --ssh-user <SSH_USER> --ssh-hostkey SHA256:<VERIFIED_HOST_KEY> --tower https://tower.example.invalid --user <TOWER_ADMIN> --ca-file <CA_CERT_FILE> --lang en-US

Save functional changes explicitly. Closing an unsaved editor offers save, discard or cancel; failed saves retain the draft. Uninstall removes the active registration but retains configuration and packages. Package updates must increase the version and preserve the current configuration schema; automatic schema migration is not available.

A shared channel.
An explicit approval.

The framework includes rivetin-ssh-channel by default, with its lifecycle and collection configuration both off. Installation does not connect to hosts. A consuming extension’s collection capability is unapproved until an administrator reviews and confirms its operations, targets and schedule.

rivetin channel status --ssh tower.example.invalid:22 --ssh-user <SSH_USER> --ssh-hostkey SHA256:<VERIFIED_HOST_KEY> --tower https://tower.example.invalid --user <TOWER_ADMIN> --ca-file <CA_CERT_FILE> --lang en-US

Connection drafts can be edited in the authenticated SSH settings page or imported from a controlled sensitive file through the CLI. Credentials use an explicit host-over-cluster-over-global priority without mixing fields across levels. The backend encrypts saved secrets; read responses expose presence flags only. Draft changes require an explicit save, revoke approvals, and do not start host connections. This website never collects credentials.

rivetin channel import-host --host-profile-file <HOST_PROFILE_JSON> --ssh tower.example.invalid:22 --ssh-user <SSH_USER> --ssh-hostkey SHA256:<VERIFIED_HOST_KEY> --tower https://tower.example.invalid --user <TOWER_ADMIN> --ca-file <CA_CERT_FILE> --lang en-US

Importing or removing a profile revokes related approvals and does not start a host connection. Changes to commands, versions, targets, schedules or channel settings require a new review. Arbitrary shell, destructive operations and unknown operation types are rejected.

SSH Channel 0.1.1 is enabled in the controlled deployment; connection editing, inventory and unsaved-draft exit have read-only browser acceptance. Collection settings, credentials, approvals and schedules remain unconfigured, and no real SSH host has been connected. The bounded recent-result buffer is separate from the framework’s persistent per-disk SMART history. The shared provider and HTTP history consumer have local integration coverage, but real samples, actual history and cross-day collection remain unverified.

Keep a way back.

Framework updates use the CLI; plugin updates may use a verified local package or a published market entry. Updates back up state and leave the relevant component disabled. Web-based framework self-update is not implemented.

rivetin update --ssh tower.example.invalid:22 --ssh-user <SSH_USER> --ssh-hostkey SHA256:<VERIFIED_HOST_KEY> --tower https://tower.example.invalid --user <TOWER_ADMIN> --ca-file <CA_CERT_FILE> --lang en-US

If a write has an unknown result, inspect status and its recovery information before trying again. Do not repeat an uncertain operation just because a connection timed out.

rivetin status --ssh tower.example.invalid:22 --ssh-user <SSH_USER> --ssh-hostkey SHA256:<VERIFIED_HOST_KEY> --lang en-US
rivetin recover --operation <RECOVERY_ID> --ssh tower.example.invalid:22 --ssh-user <SSH_USER> --ssh-hostkey SHA256:<VERIFIED_HOST_KEY> --tower https://tower.example.invalid --user <TOWER_ADMIN> --ca-file <CA_CERT_FILE> --lang en-US

Emergency disable only needs the verified SSH connection. It writes a persistent disable marker and does not depend on healthy Tower Web/API or Kubernetes services. A browser that is already stuck may need a refresh; this is not process isolation.

rivetin disable --ssh tower.example.invalid:22 --ssh-user <SSH_USER> --ssh-hostkey SHA256:<VERIFIED_HOST_KEY> --lang en-US

Source versions.
Clear delivery boundaries.

These are current local source versions, not released package versions or proof of live acceptance. Open a module on the homepage for its capabilities and remaining integration work.

Current Rivetin naming is intentionally separate from old deployments. Switching an existing environment needs a separately reviewed backup, old-instance removal, new installation and configuration-entry plan. This website does not migrate or modify deployments.

Local operation logs are available in the extension center. Mirroring them into Tower’s native audit service was blocked by a system-user restriction in historical tests; it must not be described as working native audit integration.

Reviewed October 28, 2026 against the project’s local documentation, manifests, catalog and installer profile. The GitHub repository rename was verified; access remains private. Windows amd64 help/version were checked offline for this guide. No installation, host connection or live deployment was performed by the website task.