Skip to content
SuperCharged — Connect AnywhereSuperCharged — Connect Anywhere
On this page

Inventory sources

The connection tree comes from your configured catalogue sources. NetBox, phpIPAM, CyberArk and ControlPlane stay read-only. KeePass is a local file you can create and edit in the app.

Each source appears as its own root. Supported today:

Kind Tree shape
NetBox Site / Role / Region / Tenant layouts (choose in the catalogue panel)
phpIPAM Section → Device
KeePass Same Site / Role / Region / Tenant layouts as NetBox (typed folders in the .kdbx file)
CyberArk Safe → Device
ControlPlane Groups as organised in ControlPlane → Device

Manage sources

At start-up, select the sources available for this session (the window shows how many are checked). Add, edit, or remove a highlighted source; Remove all deletes every saved source from settings (not just unchecking them). Kind is chosen first when adding. Unselected sources remain saved but won’t be loaded. During sign-in, Back returns to this list so a dead or wrong source never traps you.

You can also use Tools → Options → Catalogue sources later.

Kind What you enter
NetBox Site URL
phpIPAM Site URL. A phpIPAM admin must create an API app named supercharged (Admin → API; SSL with user token; at least Read).
KeePass Path to the .kdbx file (optional key file). Browse to pick files, or Create a new empty database (master password + confirm; optional key file). Creating a key file later does not attach it to an existing database.

After changing sources, sign in again and Refresh. KeePass asks for the master password (not a username). The master password is never stored. The app writes the KeePass file only when you create a vault or change folders and devices on a KeePass root. A KeePass device is one machine: Identity holds the default host and credentials; several logins (root SSH, operator SSH, IPMI, VNC, Proxmox) are accesses on that device, not extra tree rows. Leave access username/password empty to use the Identity defaults.

Tree views (NetBox and KeePass)

Choose the layout in the catalogue panel (saved automatically):

Mode Hierarchy
By Site Site → Device Role → Device
By Rack Site → Rack → Device
By Role Device Role → Site → Rack → Device
By Region Region → Site → Device Role → Device
By Tenant Tenant → Site → Device Role → Device

Devices without a site, role, rack, tenant, region, or section are placed under the nearest real folder that exists in the selected view; no placeholder Unassigned or Unracked folders are shown. Devices without a usable hostname are skipped.

Action Effect
Refresh Reloads sources unlocked this session; open session tabs stay open
Search box Filters the tree in realtime by name or hostname; expands matches and selects the first matching device

Connect

Action When
Double-click / Connect to SSH Opens SSH using that device’s SSH access. Several SSH logins: pick one. NetBox/phpIPAM/ControlPlane use your sign-in for that source. CyberArk uses the vaulted account credential. KeePass uses the access username and password.
Connect to IPMI When the device has an IPMI access (NetBox interface named ipmi, or KeePass IPMI access) — see IPMI
Connect to Proxmox When the device has a Proxmox access (KeePass type Proxmox, or NetBox platform/manufacturer/device type/role/custom field matching Proxmox or PVE; default port 8006) — see Proxmox
Open WinBox When inventory marks MikroTik / RouterOS (or KeePass access type WinBox) on Windows or Linux — see WinBox
KeePass folder menu (right-click) Selects that folder first, then Add Tenant / Region / Site / Rack / Role, add device, rename or delete folder, Move to… Empty typed folders stay visible after save (no device required).
KeePass device menu (right-click) Edit device (name, host, list of accesses), delete device, Move to…
Tools → Import mRemote Reads confcons.xml into an unlocked KeePass folder. Folders become regions. Connections to the same host become one device with several accesses. Encrypted files may need the mRemote encryption password.

Connect to All

Right-click a branch in the catalogue tree. Connect to All is the first menu item. Choose a mode from its submenu to open one connection to each device directly inside that branch.

  • Only devices at the first level count. Devices inside subfolders are excluded.
  • The submenu contains only connection modes available on every direct device. For example, if all direct devices support SSH and SFTP, both are offered; a mode supported by only some devices is omitted.
  • Each connection uses that device’s own access settings. If a device has several accesses for the same protocol, the first matching access is used.
  • The menu item is greyed out if there are no direct devices or no common connection modes.

For example, a branch containing two direct devices and a folder with three more devices opens two connections. The three devices in the nested folder are excluded.

Related: Security model · Support · Release notes