DocsStart here

How Devexana is delivered

Devexana is a white-glove service: Devexana installs, updates, monitors and supports the appliance for you. Devexana connects your sources with your team. Your team provides the site, the network access and the accounts.

In production use
NVIDIA DGX Spark appliance, installed by Devexana
In production use
Signed updates with automatic code rollback
Available
Daily encrypted database snapshots, on by default
Off by default
Encrypted offsite copy to your own S3 bucket
On this page

This page lists what Devexana does, what your team provides, and how the appliance connects to your network.

What Devexana does

StageWhat Devexana does
InstallDevexana installs its software on the appliance. Devexana checks each file and model. Devexana runs an acceptance check of the GPU, services and models
Set upSets up HTTPS for the web interface, creates the first administrator account and gives it to your named contact
ConnectConnects the read-only sources with your team. An administrator on your team approves each read function
UpdateDelivers signed updates. The appliance verifies each update before installation
MonitorChecks the health of the service, the models, the sources and the backups
SupportAnswers questions and fixes problems through support@devexana.com
Diagram titled Install and update, in two rows. Install from the offline card: card verified against a SHA-256 manifest, installation copies the files, models verified after each copy, then an acceptance check of the GPU, services, health and each copied model. Update from a signed bundle: bundle verified by its Ed25519 signature, new code applied, a health check the service must pass, then automatic code rollback if unhealthy. A footer says that database rollback is manual.
The checks that run when Devexana installs the appliance (top row) and when Devexana applies a signed update (bottom row). If the health check fails, the appliance restores the previous code. Open full size

What your team provides

ItemDetail
A site for the applianceA secure location with power. Follow NVIDIA's guidance for the DGX Spark. Devexana does not publish thermal, power or rack figures
A network locationA management network that reaches your sources and that staff reach over HTTPS. See Network placement
Firewall openingsThe ports in the table below. Keep a default-deny outbound rule for the appliance
Read-only accountsOne account for each source, with read access only. See Create read-only accounts
A named contactOne person who receives the first administrator account and works with Devexana support

The appliance

PartValue
SystemNVIDIA DGX Spark (GB10), 128 GB unified memory
Operating systemDGX OS
ModelsRun on the appliance. The model server listens only on the appliance itself

Devexana supports only the NVIDIA DGX Spark. Jetson boards, general x86 servers and virtual machines are not install targets.

Network placement

Place the appliance on a management network that meets these conditions:

  • The appliance can reach the network devices and systems that Devexana reads.
  • If you use listeners, your network devices can send records to the appliance.
  • Staff on your IT subnet can reach the web interface over HTTPS.
  • Your firewall controls what the appliance can reach.

The operating system needs a one-time online package install during installation. Plan this network access with Devexana.

Ports

DirectionPortUseState
InboundTCP 443HTTPS web interfaceSet up by Devexana. Devexana confirms the port at installation
InboundTCP 42108Web interface and API over plain HTTP, behind the HTTPS frontOpen to your IT subnet only. Give staff the HTTPS address
InboundUDP 514, 162, 2055 (or a port above 1024)Syslog, SNMP traps, NetFlow and IPFIX listenersOff
InboundUDP 5353mDNS name of the appliance on the LANOn
OutboundTCP 22, UDP 161SSH and SNMP reads of switches, routers and firewallsWhen a source is added
OutboundTCP 443API sources, for example the helpdeskWhen a source is added
OutboundTCP 636LDAPS directory readsWhen a source is added
OutboundSMTPAlert email through your relayOff
OutboundDNS and NTPYour internal DNS and time serversOn
OutboundHTTPSOptional cloud featuresSee Outbound connections: the complete list

Ports and protocols lists every port, with discovery probes and webhook receivers.

Names on your network

The appliance publishes <short name>.local over mDNS on its network segment. For a DNS name, add an A record for the appliance's IP address on your DNS server. The IP address works without either name.

Updates and backups

  • Updates. The appliance refuses an update with a wrong signature, target, version or file hash. If the service fails its health check after an update, the appliance restores the previous code.
  • Backups. The appliance takes an encrypted database snapshot every 24 hours and keeps 14. Devexana records each snapshot in the audit log.
  • Offsite copy. An encrypted copy to your own S3 bucket is off by default.
  • Database key. Snapshots do not contain the database key file. Agree with Devexana who keeps a protected copy of the key.
  • Restore. Devexana support restores the database from a snapshot when a restore is necessary.

Access for Devexana

The signed heartbeat to Devexana Cloud is off by default. The vendor support channel is off by default. The Government/Education edition has no remote-access feature. In the Business edition, WireGuard remote access exists, and an administrator turns it on.

Contact

Send questions and problem reports to support@devexana.com. Include the time of the problem and the page or answer where you saw it.

Applies to Devexana release 0.3.182. Page updated 2026-10-20. Questions or corrections: support@devexana.com.