One control plane.
Every workspace.
Provision, assign and manage desktop resources for each employee from one admin view.
Keep desktop infrastructure centrally managed while letting employees work from virtually anywhere. Designed for lean IT teams and growing businesses.
Provision, assign and manage desktop resources for each employee from one admin view.
Planned controls include MFA, access policies, session controls and managed backups; implementation must be validated before a pilot.
Check device, application and connection compatibility during pilot scoping.
Your team opens a desktop from the devices they already have. It runs on our dedicated Glixy server, next to Glixy SLM, so every desktop can ask questions about your documents.
Your device sends clicks and receives the picture of your desktop. The apps and files run on the Glixy server.
Keystrokes and clicks go up; screen updates come back down. Business files can stay on the server, depending on the file-transfer rules you agree.
Business desktops with Microsoft 365 Apps, as configured in the app builder. Illustrative, before GST.
Your own mix of teams and apps changes this. Try the app builder →
Targets, not current capacity — each step is validated with real workloads before anything is promised.
Proposed onboarding, subject to an agreed pilot scope. The service and client are under development; this page does not provision desktops.
Share team size, applications, device types, work locations and typical workloads.
Confirm licensing, resource fit, connection tests, security needs and the written quote.
Once the service is ready, test agreed applications and access with a nominated group before rollout.
Agree acceptance results, user guidance, support contacts and recovery expectations before wider use.
Glixy Virtual Workspace is under development. These are the requirements and proposed service arrangements to discuss before a pilot, rather than confirmed production capabilities.
Windows and Mac clients are planned. Supported operating-system versions, device specifications and any browser-access option have not been confirmed.
MFA, access policies, session controls and managed backups are planned, not verified as implemented.
Start with a requirements discussion, an agreed test group and acceptance criteria. Use the proposed onboarding steps to plan a rollout.
Support channels, service hours, response targets, escalation contacts, maintenance responsibilities and any onboarding fees must be agreed in writing. This preview offers no response-time guarantee.
A single-server pilot can be interrupted by server or network failure. No production SLA, uptime commitment or recovery guarantee is established here.
Agree backup scope, schedule, retention, restore testing, recovery-time and data-loss targets. Backups alone do not provide uninterrupted availability; resilience needs a validated infrastructure design.
Downloads activate when the app is released. This is a product preview; the guide below describes the intended setup, not a live VDI connection.
When released, choose Windows or Mac for your device. Check the published requirements before downloading.
Follow the installation instructions supplied with the released app.
Sign in following the access instructions provided by your organization.
Choose the desktop assigned to you once your organization has enabled access.
Choose the released client for your device’s platform after checking its published requirements. The Windows and Mac buttons above stay disabled until installers are released; no installation is required to explore this page’s demo console.
For a future pilot, check the access instructions from your organization and ask its nominated administrator to confirm your account and assigned desktop. Do not share passwords or access codes in an enquiry. This preview has no customer sign-in or assigned desktops.
Once a pilot is available, note the time, device and operating system, work location, affected app and the error message. Check your local connection and contact the support channel agreed for your pilot. Remove confidential information from screenshots. For planning questions now, use Book a free demo session.
Our first dedicated Glixy server runs Glixy SLM first; VDI desktops follow on the same server, with the SLM built in. Capacity must be validated against real customer workloads before a production SLA is offered.
Book a free demo sessionSimultaneous office desktops on our first server*
With added server capacity and validation
Multi-server design with resilience
*Planning target for the dedicated server that also runs Glixy SLM. VDI capacity will be benchmarked once the SLM is in place, and the GPU stays reserved for AI workloads. Registered accounts and simultaneous users are different.
Bring your device and location list, required applications, expected concurrent users and acceptance criteria. Agree responsibilities, support and recovery expectations before a test begins.
Tell us how your team works. We'll help plan a practical VDI deployment for your applications, usage and security needs.