Remote desktops on your infrastructure, for your teams or your customers.
Billet is a high-performance remote desktop for any Windows, macOS or Linux machine you run. Sessions are hardware-encoded in AV1, H.265 or H.264 and travel on Billet's own UDP transport, straight from the viewer to the desktop wherever the network allows. Providers give each customer its own tenant and sign-on. In-house teams get one control plane for the machines they already have.
We are onboarding a small number of early access deployments.
One deployment.
Separate tenants.
No inbound
host ports
Windows, macOS, Linux, iOS,
Android and web browsers
Speed
Built for speed, from the transport up.
Billet is a high-performance remote desktop. Every native session gets all of this by default, with nothing to tune.
Straight to the desktop
The viewer connects directly to the desktop, peer to peer, whenever the network allows. Media goes between the two networks without a stop in the middle.
Its own transport, over UDP
Billet's real-time transport runs on QUIC over UDP. Video, input, the clipboard and devices each have their own stream, so a busy video stream does not hold up your mouse and keyboard.
Encoded in hardware
AV1, H.265 or H.264 in hardware, whichever is the best both ends support. A host without a hardware encoder still streams, in VP8 in software.
Adjusts in small steps
When the link narrows, quality drops by about what the link lost instead of falling to the lowest setting, and climbs back as the link shows it can carry more. Sessions do not start at the bottom.
Changes path without reconnecting
A session that opens on the relay moves onto the direct path when one opens, without reconnecting, and drops back to the relay the same way if that path closes.
On the machines you have
Hosts run on any physical or virtual Windows, macOS or Linux machine, with or without a GPU. People connect from Windows, macOS, Linux, iOS, Android or a web browser.
The gap
Running desktops for more than one group
Parsec and HP Anyware both 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.
Running Parsec today? See how Billet compares and what changes when you move. Planning to replace HP Anyware? See how Billet compares and what changes when you move.
| Who runs it | Tenants | Single sign-on | Hosts | Codecs | |
|---|---|---|---|---|---|
| Billet | You do, on your own infrastructure | Many tenants, one deployment, with policy set per tenant | SAML 2.0 per tenant, more than one connection each, SCIM 2.0 | Windows, macOS and Linux, physical or virtual | H.265, H.264, AV1 and VP8 |
| Parsec | Parsec's service, with an optional self-hosted relay | Teams, with each user in one team | SAML 2.0, with SCIM on Enterprise plans | Windows and macOS | H.265 and H.264 |
As documented by each vendor, checked August and October 2026.
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.
Because the broker checks the tenant first, you can run one platform for every customer instead of one per customer. Inside a tenant you can narrow access further, down to named desktops for a named person.
Identity
Sign-on that belongs to each tenant
Most remote desktop products offer single sign-on. When you run desktops for several groups, the questions are whose directory each group signs in with, how many directories one deployment can hold, and who holds the registration.
One deployment, many directories
Thirty customers are thirty tenants in the platform you run, not thirty accounts with a vendor. Each connects its own Entra or Okta over SAML 2.0, and none can see 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.
A second step where a password is used
Where a person signs in to Billet with a password, a tenant can ask for an authenticator app code, or a security key or passkey, after it. Off, optional or required, set per tenant, with recovery codes for a lost phone.
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.
| Control | What you can set |
|---|---|
| Clipboard | Off, on, or one direction only. Copy into the desktop but not out of it, or the reverse, set per tenant and per host. |
| File transfer | Enabled or disabled, so a tenant handling regulated material can be stopped from moving files in or out while another is left open. |
| USB devices | USB 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 and GPU 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.
Already run Amazon DCV?
Manage it from the same portal.
Billet can be the management and control plane for a DCV estate you already run, under the same tenants and sign-on. DCV desktops stay DCV. How Billet works with Amazon DCV.
Deployment
Runs on infrastructure you already own
Where the network allows it, a Billet session carries its media directly between the viewer and the desktop, and it falls back to your relay when it cannot. 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. The portal checks in with our license service about once an hour, and nothing it sends names a tenant, a person, or a desktop.
High availability
The portal and broker support high availability deployments, so the control plane does not rest on a single machine.
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. You bill your customers and support them yourself.
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.
Studios and engineering teams
Artists, engineers and freelancers each reach their own GPU workstation, and only theirs, drawing with a pen tablet from Windows or macOS with pressure and tilt. Give a contractor one named desktop, and switch off clipboard and file transfer for the tenant they sit in.
What ships today
What works today.
Everything listed here works in the product today.
Streaming
- Billet native streaming on our own real-time transport over UDP, with authenticated hole punching and an encrypted relay fallback
- Hardware-encoded AV1, H.265 and H.264, picking the best both ends support, and VP8 in software on a host with no hardware encoder
- Quality that adapts to the connection instead of stuttering at a fixed setting
- The Billet relay and host agent
- Hosts on any physical or virtual Windows, macOS or Linux machine, with or without a GPU
- Clients for Windows, macOS (Intel and Apple silicon), Linux, iOS, Android and web browsers. The Android app also runs on ChromeOS
- Pen tablets from the Windows and macOS clients to any host, with pressure and tilt
- Desktops reached on private networks, with no inbound ports opened on the host
Identity and access
- Tenant separation: a user only ever sees desktops in their own tenant
- 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 send in practice
- A second step at sign-in for password users: authenticator apps, security keys and passkeys, with recovery codes
- Device access granted per tenant
Control and operations
- Clipboard direction, file transfer and USB redirection set per tenant and per host
- System and GPU activity reported back from every host
- Session activity per user and per host, including duration
- High availability portal and broker deployments
Last updated 2026-11-21.
Tell us what you are running.
A short conversation about your desktops, your directory and your network is usually enough to tell whether Billet fits.