Citrix and Horizon seats for AI workers: move them to a computer per worker
Take AI worker and contractor seats off your VDI renewal and give each worker its own computer.
If AI workers, contractors, or unused seats are part of your Citrix or Horizon renewal, you can move those seats without replacing the VDI platform. Give each of those workers its own Orgo computer: a full Linux or Windows desktop that keeps running until you stop it.
Keep your VDI for the people it was built for. Orgo is the computer layer. It runs next to your cloud and your agent or automation tools, not instead of them.
What is a per-worker hosted desktop?
A per-worker hosted desktop is one dedicated cloud computer for each worker, person or AI, instead of a session handed out from a shared pool. Every Orgo computer is a full desktop with a browser and the standard userland, reachable over HTTP and VNC, and it runs until you stop it. Its files, installed software, and configuration on disk survive stops and restarts (Introduction).
The difference from a VDI seat is what you buy. A VDI seat is a license to reach desktops that you or a provider host, through the vendor's broker. An Orgo computer is a virtual machine of its own, sized for one worker, with screenshot, mouse, keyboard, and shell actions in its API.
Orgo provides the computer. You bring the agent, such as Claude, an OpenAI model, your own loop, or the automation you already run, or you use Orgo's computer use API.
What changed at Citrix and Horizon?
Citrix changed how it licenses, and Horizon changed owners.
- Citrix. Citrix ended sales of its Hybrid Rights entitlements, including the Citrix DaaS Hybrid Rights add-on, on October 11, 2023 and ended renewals on December 6, 2023. Those customers move to Citrix Universal licenses at renewal (Citrix CTX575761). In April 2023, Citrix said Universal had a minimum initial order of 250 for new subscriptions. It also said Universal was the only Transition and Trade-up offering for customers modernizing an on-premises perpetual Virtual Apps and Desktops deployment (Citrix, April 2023). Check current terms with Citrix or your reseller.
- Horizon. Broadcom sold its End-User Computing division, which includes Horizon, to KKR for about $4 billion. The deal closed on July 1, 2024, and the business now operates as Omnissa (KKR announcement, Omnissa launch).
Neither change means you should leave VDI. They are a reason to recount seats at renewal, and seats that serve AI workers, short-term contractors, or nobody at all are the easiest ones to question.
Which seats should move off VDI, and which should stay?
Move a seat when the worker needs a whole machine of its own more than it needs your broker:
- AI workers. An agent that drives a legacy app, portal, or thick client through its interface needs a persistent, unattended desktop that stays up when nobody is logged in. That is what a dedicated computer is. A pooled desktop that resets at logoff is the opposite.
- Contractor and project seats. A seat that exists for a few months is easier to give as one computer you create and later delete than as another named user on a term subscription.
- Unused seats. Seats you pay for but cannot map to a person or workload are the first ones to audit before renewal.
Keep a seat on VDI when it serves a large group of people, depends on your on-premises network, or sits inside a compliance boundary you have already certified. Orgo is not meant to replace a large VDI farm.
Citrix or Horizon seat vs an Orgo computer per worker
| Citrix or Horizon seat | Orgo computer per worker | |
|---|---|---|
| What you buy | A license counted per user or device, or per concurrent user (Citrix, 2023, Omnissa) | One cloud computer, sized in vCPU, RAM, and disk |
| Who hosts the desktops | Usually your data center or cloud account, with the vendor's broker in front | Orgo |
| Built for | People connecting to apps and desktops | Agents and people who need a whole desktop, driven over the HTTP API, the orgo CLI, or MCP (Compare platforms) |
| Agent control | Your own tooling, or agent features your vendor offers | Screenshot, mouse, keyboard, and shell actions built in (Introduction) |
| Operating systems | Mainly Windows desktops and published apps | Linux on every plan, Windows on Scale or as an add-on, Mac and iPhone by request (Pricing) |
| Always on | Depends on your pool and power settings | Runs until you stop it (Introduction) |
| Standard image | Your gold image and its update cycle | Linux templates, built once into a golden snapshot, with immutable versions (Templates), or a clone of a computer you set up |
| Minimum order | Citrix Universal: 250 for new subscriptions (Citrix, 2023) | None: Starter includes one computer, and you add more one at a time (Pricing) |
| Resell to clients | Through the vendor's partner programs | A workspace and billing per client, under your business name, with Invoicing (Invoicing) |
This post does not include a cost comparison. Seat prices depend on your contract, so price your own mix against Orgo pricing.
How do I move AI worker and contractor seats to Orgo?
- List the seats. Before your renewal date, pull the seats tied to service accounts, bots, automation runners, contractors, and unassigned users.
- Rebuild the image. For Linux workers, describe the apps, files, services, and secrets one worker needs in an
orgo.ai/v1template. Orgo builds it once into a golden snapshot, and every launch starts from it (Templates). Building your own templates needs a Scale plan or higher. Ready-made templates work on any paid plan. Templates are Linux only, so for Windows workers, set up one computer and clone it for each worker (Clone computer). - Size each worker. Sizes run from Small (0.5 vCPU, 4 GB RAM, API only) to XL (6 vCPU, 32 GB RAM, 150 GB disk). XL is the largest size you can create on your own, as long as your account has the RAM and vCPU for it, and add-ons raise both. 2XL (8 vCPU, 64 GB RAM, 300 GB disk) is set up on request. Give a Windows worker at least 8 GB of RAM, so Small is for Linux only.
- Create one computer per worker. For a Windows worker, set
ostowindowsandramto 8 or more. Windows needs a Scale plan or a Windows computer add-on. Without one, the create returns403with codeWINDOWS_REQUIRES_SCALE(Create computer). - Connect the worker. Point your agent or automation at the computer through the HTTP API, the
orgoCLI, or MCP. For a contractor, invite them to the workspace with View only or Full access, and they use the live desktop in the browser. Besides the owner, a workspace can add 1 person on Starter, 5 on Growth, and 25 on Scale. - Check network reach. An Orgo computer runs on Orgo's servers, not on your network. If a worker must reach systems inside a customer network, ask Orgo before you cut the seat.
- Drop the seats at renewal. Reduce the VDI seat count only after the workers run cleanly on their own computers.
How do MSPs resell a computer per worker?
Orgo Invoicing lets you run Orgo for each client from your own app. Each client gets its own workspace and an API key that reaches only that workspace, and the client never signs up to Orgo.
You either cover a client's computers on your plan, or bill the client monthly through a payment link in your business's name. Orgo keeps the client's computer cost, Stripe's card fee comes out of your side, and you keep the rest (Invoicing). When the build is done, you can transfer the workspace to the client's own Orgo account. Invoicing is on every paid plan.
That gives an MSP a cost per computer to price against, without building a broker farm for a handful of AI workers.
Does Orgo replace my VDI platform or my cloud?
No. Orgo runs one thing: persistent computers for AI agents. It is not a general cloud platform (Introduction). Keep Citrix or Horizon for the people it serves well, keep your cloud for the rest of your stack, and keep the agent or automation tools you already run. Orgo sits under those tools as the computer each worker uses.
FAQ
Can an AI worker run on a Windows desktop on Orgo? Yes. Windows is included on Scale and is an add-on on the other paid plans (Pricing). The screenshot, mouse, and keyboard actions work on Windows too, with a few differences in the fields they accept, and the bash endpoint runs PowerShell there (Run a command).
Does the computer stay on when nobody is logged in? Yes. A computer runs until you stop it, unless you turn on auto-stop for it. Its disk persists across stop and start, but memory and running processes do not (Instance types).
Can I control who sees or operates each worker's computer? Yes. Workspaces separate teams, projects, or clients, and each person you invite gets View only or Full access. A view-only member can see the workspace and its computers but cannot change them (Authentication).
How many computers can I add? Up to 100 added computers on your own, on Plan & billing or through the capacity API. Past that, Orgo raises the limit for your account on request, to thousands of computers at the same prices (Scaling).
Should I migrate my whole Citrix or Horizon farm to Orgo? No. Orgo is aimed at seats that need a dedicated computer per worker, such as AI workers, contractors, and unused seats, not at replacing a large VDI estate.
Where is Orgo's security documentation? In the Orgo Trust Center. Review it before you move regulated workloads.