DTR Vantage

Licensing portal ↗Request a demo

Pricing, the shape

Per module, per unit, bought direct or through the partner that runs your estate. Rates are a conversation; everything else about how it is priced is here.

Sold
per module
each on its own unit: pair, pool, server, host or installation
Partner tiers
3
Registered 20% · Silver 30% · Gold 40% off list
NFR
included
a lab key with every partner tier, on no pool
Key bound to
the install
the Installation ID; verified offline
Rates
on request
the shape is public, the numbers are a conversation

What a unit is

Reading modules first; a management, protection or analytics module presumes the reading module of its product on the same key, and the portal refuses a key without it.

ModuleCoversUnitPresumes
NetScaler
NetScaler monitoringpolling, health, Analyze, certificates, reportsper HA pair
NetScaler configurationchanges from Vantage: the object editor, bindings, policies, gateway blocking enforcement, AppFlow setupper HA pairNetScaler monitoring
NetScaler identity threatgateway sign-in protection, report only or enforcedper HA pairNetScaler monitoring
NetScaler analyticsHDX Insight data and Session performanceper HA pairNetScaler monitoring (Windows Infrastructure for the VDA side)
Config Compare · Config Import · NetScaler Documentation · AI Enhancementdrift comparison, ns.conf import, documentation export, AI explanationsper installation
XenServer
XenServer healthhealth reports, trends, notificationsper pool
XenServer consoleXenCenter's operations in the browser: VMs, storage, networks, updatesper poolXenServer health
Windows and Hyper-V
Windows Infrastructurethe agent, inventory, notifications, certificatesper server
Hyper-V consoleHyper-V Manager's pages and actionsper Hyper-V hostWindows Infrastructure
Windows Updatescan and install updates across the estateper serverWindows Infrastructure
Windows identity threatserver sign-in protectionper serverWindows Infrastructure
The whole installation
Uptimemonitors and the company's status pageper installation
Syslogthe receiver and the messages viewper installation
Direct

Your own estate

  • One key, the modules you use, with the capacity written on it: NetScaler pairs, XenServer pools and hosts, Windows servers, Hyper-V hosts. A direct key may leave a capacity open.
  • A term with an expiry date on the key; the dashboard says when it is close.
  • A trial for the reading modules to start with; the management modules are added to the same installation later, no reinstall.

Getting a quote. A signed-in customer or partner asks for one on the licensing portal under Quotes: the modules and units, the term, and an estimate at list less the partner tier's discount; DTR answers there and by mail. Not signed up yet: the contact form.

Through a partner

The partner programme

TierOff listWhat comes with it
Registered20%A pool of units per module, bought at the tier's price and issued to your own clients as keys from the licensing portal, each installation on its own record and its key bound to it. An NFR key for your lab: 2 pairs, 1 pool, 10 servers, 2 Hyper-V hosts, one year, drawing on no pool.
Silver30%
Gold40%
  • The pool counts live keys. A revoked key returns its units; a key waiting for an installation still holds them.
  • Issued in minutes, from the portal. A client activates from the dashboard with a short code, or you issue against their Installation ID.
  • Release channels. A build reaches the dev channel first; accounts you mark early-access see it before everyone.
  • Quotes from the portal. Ask under Quotes for your own units or a client's; the estimate carries your tier's discount, DTR confirms the figure.

Updates across a partner's clients

Each installation updates itself: an administrator presses Check for updates on its Settings page, the package downloads with its SHA-256 checked, and Install now applies it through a system task that stops the service, backs up, deploys, restarts and rolls back on failure. Without internet, the same update zip is applied by hand. Nothing checks on a timer: the dashboard contacts the portal only when someone presses the button.

What that means for a partner with thirty clients: thirty installations, thirty Check for updates. Today the portal gives you the staging (dev channel first, early access per account, release to everyone when you are satisfied) but not the push. Partner-initiated updates across every client's installation from the portal are on the roadmap; until they land, we say so here rather than on the call.

Not in the product today