Skip to content
BILLETRequest early access

Early access

Assign the right GPU desktop. Keep the infrastructure yours.

One control plane for isolated studios, departments, and clients. Billet is virtual desktop management you host yourself, for a single organization or for many.

Request early accessSee how it works

We are onboarding a small number of early access deployments.

How Billet assigns a GPU desktopThree isolated tenants, a studio, a department and a client, each reach one Billet control plane which authorizes the request and assigns a desktop. Everything downstream runs on infrastructure the operator controls: a relay or DCV gateway, and a pool of GPU desktops on a private network with no inbound ports.StudiotenantDepartmenttenantClienttenantAUTHORIZE+ ASSIGNYOUR INFRASTRUCTURERelay /DCV gatewayGPU desktop poolPrivatenetworkGPUhosts

One deployment.
Separate tenants.

No inbound
host ports

Windows, macOS
and Linux clients

The gap

Running desktops for more than one group

Parsec, HP Anyware, and Amazon DCV (formerly NICE DCV) all put a remote desktop on a screen well. The difficulty starts when you have to run desktops for more than one group of people: keeping them apart, connecting each to its own directory, and reaching machines on networks nobody wants to open up.

DCV carries a connection well and does not try to be a broker, which is why Billet manages DCV estates instead of replacing them.

Multi-tenant brokerSingle sign-onCodecs
BilletMany tenants, one deploymentSAML 2.0 and SCIM per tenantAV1, H.265 and H.264
ParsecOne team per accountSAML 2.0 and SCIMH.265 and H.264
HP AnywareSeparate productEnterprise licensingPCoIP and H.264
Amazon DCV / NICE DCVSession Manager API, or their consoleNo native SAMLH.264

Codec support as documented by each vendor, checked August 2026. The Billet relay and host agent are in early access.

Separation

A user in one tenant cannot see or reach a desktop belonging to another. The broker only ever considers desktops inside the requesting tenant.

Separation is the reason to run one platform instead of one per customer, so it is enforced when the request is answered. Inside a tenant you can narrow it further, down to named desktops for a named person.

Identity

Sign-on that belongs to each tenant

Single sign-on by itself is table stakes. What matters when you run desktops for several groups is whose directory it is, how many fit in one deployment, and who holds the registration.

One deployment, many directories

Thirty customers do not mean thirty accounts with a vendor. They are thirty tenants in the platform you run, each connecting its own Entra or Okta over SAML 2.0, each invisible to the others.

More than one per tenant

A tenant can hold several connections at once, so a customer can move between providers without a cutover weekend, or keep contractors and staff on separate directories.

Joiners and leavers

SCIM 2.0 user provisioning, built against what Entra and Okta send in practice, so accounts appear and disappear with the directory. Users today, groups not yet.

Control

Decide what a session is allowed to do.

What someone can move in and out of a desktop is usually what comes up in a security review. Policy is set per tenant and per host.

ControlWhat you can set
ClipboardOff, on, or one direction only. Copy into the desktop but not out of it, or the reverse, set per tenant and per host.
File transferEnabled or disabled, so a tenant handling regulated material can be stopped from moving files in or out while another is left open.
USB devicesUSB redirection switched on or off. The default is off, so nothing reaches the desktop until it is granted.

Visibility

What the estate is doing

Every machine reports in

An agent on each host samples system, GPU and DCV activity and sends it back, so the portal shows how the estate is behaving without anyone checking machines one at a time. It reports outbound, so it works on hosts that accept no connections.

Session activity, per user and per host

Who connected, to which desktop, and for how long. Enough to work out which machines are earning their keep, which are idle, and what to charge a department or a customer for.

Where Billet sits

Billet is the broker your DCV client asks.

A DCV client does not find a desktop on its own. It asks a broker, and Billet is that broker: it authenticates the user, decides which desktop they get, and returns the connection details. Billet then talks to the DCV gateway and to the DCV server on the host, so the assignment, the authentication and the configuration behind them are one system. The gateway carries the session itself.

The same broker works with our own relay and host agent, so a deployment can run DCV hosts, Billet hosts, or both.

Your DCV environment

Bring an existing DCV estate under Billet's user management and brokering.

  • Speaks to the DCV host and gateway architecture directly.
  • Full DCV user assignment and connectivity from the Billet portal, including guest access.
  • Host-level metrics, configuration and setup, so standing up and running DCV hosts is part of the platform.

Billet native streaming

Our own host agent and relay, for desktops you stand up on Billet directly.

  • In early access, and the part of the product still moving fastest.
  • AV1, H.265 and H.264, choosing the best both ends can handle in hardware.
  • Hosts on Windows or Linux. Users connect from Windows, macOS or Linux.

Deployment

Runs on infrastructure you already own

The portal, the broker, the directory connections, the relay and the hosts all run on infrastructure you control. Sessions never route through us. Desktops sit on your private network and reach out, so there are no inbound firewall rules to negotiate.

High availability

The portal and broker support high availability deployments, so the control plane does not rest on a single machine.

Where a Billet deployment runsEverything except the user runs on infrastructure the operator controls. Inside that boundary sit the Billet control plane, which handles SAML sign-in, SCIM provisioning and session brokering, and the relay or DCV gateway. Inside a further boundary, on a private network behind NAT, sit the GPU hosts. Users sign in to the control plane and receive a session grant, and their media flows to the relay. The hosts open outbound connections to the control plane to register and to the relay to carry media, so they need no inbound firewall rules. Sessions never route through Billet's own services.Your infrastructureYour usersBrowser, to sign inViewer, for the desktopCAD, Blender, DCCBillet control planePortal and session brokerSAML 2.0, per tenantSCIM 2.0 provisioningTenant isolationRelay or DCV gatewayOutbound-only rendezvousTCP where UDP is blockedPrivate network, behind NATGPU hostsWindows or LinuxBillet agent, or DCVNo inbound portssign in, grantmediaregistersoutboundHosts only make outbound connections.

Who it is for

Service providers

One deployment serves every customer. Each brings its own directory, sees only its own desktops, and cannot discover anyone else's. Billing, branding and support stay yours because the platform is yours.

IT and operations teams

Run it for one organization or split it by department, subsidiary or contractor. It sits on infrastructure you already own, so the security review covers your own network, not someone else's cloud.

What ships today

Where the product is.

Billet is in early access. Here are the edges.

Working now

  • Tenant separation, enforced when the request is answered
  • Single sign-on per tenant over SAML 2.0, with more than one directory connection per tenant
  • SCIM 2.0 user provisioning, built against what Entra and Okta actually send
  • Desktops reached on private networks, with no inbound ports opened on the host
  • An existing DCV estate brought under Billet user management and brokering
  • DCV user assignment, connectivity and guest access from the Billet portal
  • Host-level metrics, configuration and setup for DCV deployments
  • Clipboard direction, file transfer and USB redirection set per tenant and per host
  • System, GPU and DCV activity reported back from every host
  • Session activity per user and per host, including duration
  • High availability portal and broker deployments

Early access

  • The Billet relay and host agent
  • Clients for Windows, macOS and Linux
  • Hosts on Windows and Linux
  • Quality that adapts to the connection instead of stuttering at a fixed setting
  • Device access granted per tenant

Last updated 2026-08-29.

Tell us what you are running.

The fastest way to know whether Billet fits is a short conversation about your desktops, your directory, and your network.

Request early access