Questions and answers

Self-hosted monitoring and management for Citrix estates: NetScaler, XenServer, Windows Server and Hyper-V, Citrix session performance and failed-launch troubleshooting, on one Windows server inside your network. Every panel gives a verdict in words, with the row it is about.

NetScaler appliances and HA pairs (health, topology, certificates, configuration over NITRO, support bundle forensics), XenServer pools (health and XenCenter's operations in the browser), Windows servers and Hyper-V hosts (diagnostics, Windows Update, security posture, consoles), Citrix sessions from the VDA agent and NetScaler HDX Insight, syslog analytics, Uptime monitoring and certificate workflows. See the overview.

Teams whose business runs on Citrix: an in-house infrastructure team, or an MSP running several client estates, each on its own installation.

Yes, the live demo is the real dashboard on generic data, no sign-up. For your own estate, start a free trial.

One Windows Server VM. The installer sets up Python, the service and optionally IIS in front of it. The database is local SQLite.

No. NetScalers are read over SSH and NITRO, XenServer over XenAPI, Windows over WinRM. The one exception is the optional Windows agent, which you deploy to the servers you want it on, running as a least-privilege service account, not as an administrator.

Only where a management module is licensed, and only when an operator or administrator asks for a specific change. Every change is confirmed first and logged afterwards. Reading and managing are sold apart, so you can start with read-only.

Each installation updates itself from Settings → License, Updates & Manage with one click, or from the update zip. An installation that reports to the fleet console can take a released build automatically.

Nothing, unless you switch a cloud opt-in on. The three opt-ins are update checks, publishing Uptime status, and the fleet console. Each is off by default and needs a key. Details on the security page.

Your own password is never stored. You type it for the action, it is held in memory and handed over stdin, and the audit line says "credential not stored". Monitoring credentials are encrypted with a key local to the machine, and appliance certificates are pinned before a credential is sent.

Write to dtrvantage@dtrnetworks.com. The process is on the security page and in security.txt.

No. The security page says what stands in place of that and what we can provide as evidence.

By module, each counted in its own unit: an HA pair, a pool, a server, a Hyper-V host, or an installation. Keys are signed and checked offline, and bound to the installation they were issued for. The shape of the pricing is on Pricing & licensing; rates are on request.

Every module for 14 days, on small caps (2 HA pairs, 1 pool, 10 servers), on your own server. DTR Networks approves each trial. DTR Networks does not see your dashboard. Request a trial.

The dashboard drops to limited mode and your data is kept. A purchased key brings everything back.

Yes. Partners issue and manage their customers' keys through the licensing portal, with tiered discounts. Each client still runs its own installation.

Launch analysis: type the user's name. It reads the gateway, the store, the VDA and the session, gives a verdict per attempt, and says which side it could not read. See Failed launches.

Only if it says so. Every panel tells "asked, and there is nothing" apart from "could not ask", and gives the reason, such as a refused credential, a changed certificate or an agent that is not reporting.

Yes. Support bundle analysis and the live Appliance analysis check for crashes, resource pressure and signs of compromise, including the September 2026 exploitation's indicators. The integrity check reads the appliance directly over SSH.

Not today. A failure inside brokering shows as a sign-in with no launch, and the Launch analysis says so. Broker integration is on the roadmap.

Not today. Reports (PDF and HTML), a certificates CSV, e-mailed scheduled reports and the Uptime status page are what leave it.

It is smaller than they are. It is built around Citrix plus the NetScaler and XenServer management those tools do not do. A side-by-side comparison with sources is on Compared with others.