WINDOWS FOR THE WAY YOU WORK
Create a personal Windows 11 Pro Jump‑Desk with administrator access. Choose from 20 Azure regions, three performance tiers and Hours, Months or Years—then connect from iPad, Mac, Android, Linux or Windows.
Built with trusted technology
Jump‑Desk is Jump‑IT’s personal Windows 11 Pro cloud desktop: choose a region, billing plan and performance tier, let Jump‑IT create the Windows machine, then manage it from one dashboard and connect through a personalised RDP file.
Each Jump‑Desk gives you administrator access to install compatible Windows development software. Your IDEs, SDKs, repositories, settings and files remain on the desktop while the Jump‑Desk exists. The dashboard shows its status, credentials and connection controls, and can reset the administrator password while the machine is running.
This makes Jump‑Desk especially attractive when you need a Windows-only toolchain, a separate client environment, a temporary PC for a project, or Windows access from an iPad, Mac or Linux device. It is not a public server or universal workstation: internet access is required, every current tier has a 128 GB drive, no dedicated GPU is listed, and specialist virtualisation or networking requirements must be confirmed first.
Windows 11 Pro + adminInstall compatible Windows development tools on your own persistent cloud desktop.
20 Azure regionsChoose among the configured locations shown in the Jump‑Desk creation flow.
Three performance tiersStandard, Pro and Pro+ provide progressively more memory and storage performance.
Hours, Months or YearsMatch the commitment to a short test, recurring project or longer-lived workspace.
A developer PC created and controlled through Jump‑IT
Jump‑Desk removes much of the setup between “I need a Windows PC” and “I can start working”: choose the configuration, create it, connect and keep the workspace for the next session.
Select a Jump‑Desk region, billing plan and tier in the Jump‑IT creation flow. Jump‑IT provisions the Windows 11 Pro desktop and presents its controls in the dashboard; you do not begin with a blank server and configure the desktop stack yourself.
Administrator access lets you install compatible IDEs, SDKs and utilities. Stopping the Jump‑Desk is not deletion, so installed tools, repositories, settings and files remain while the Jump‑Desk exists.
Create multiple independently billed Jump‑Desks under one login when projects should not share the same desktop. The dashboard lists the machines separately and Usage groups their billing independently.
Download the personalised RDP file from Jump‑IT and open it in a compatible client on iPad, Mac, Android, Linux or Windows. The code and applications run on the Jump‑Desk; the local device displays and controls them.
Choose Hours for intermittent use, Months for a recurring workspace with 300 hours of monthly uptime, or Years for the published unlimited usage and uptime arrangement.
The dashboard shows whether each Jump‑Desk is running, unlocks Connect while it is running and can reset its password. Usage shows session history, while invoices are available through the billing area.
Closing the remote desktop client only disconnects the session. It does not stop an Hours Jump‑Desk.
YOUR NEXT STEP
Test your editor, dependencies and a representative build before choosing a tier. Keep source in version control and check specialist hardware or virtualisation requirements separately.
Configure your Jump-Desk
Your Jump‑Desk does the Windows work
The local device does not install or emulate Windows. It sends keyboard, pointer and touch input to your Jump‑Desk and receives the remote display. Your Windows editor, compiler, browser and project files remain together on the cloud desktop.
For sustained coding, use a physical keyboard and mouse or trackpad. Jump‑IT provides device-specific client links in the dashboard, including Microsoft remote desktop clients and Remmina guidance for Linux, followed by the personalised RDP connection file.
Install compatible tools on your own Jump‑Desk
A Jump‑Desk behaves like a personal Windows 11 Pro desktop, but the current CPU, RAM, storage, networking and acceptable-use limits still determine whether a specific toolchain fits.
Install a compatible Windows editor or IDE with your own licence, then keep its extensions, settings and project folders on the persistent Jump‑Desk.
Install Windows-compatible .NET, Java, Python, Node.js or other toolchains that fit the selected Jump‑Desk tier and the current 128 GB drive.
Clone, edit, commit and push from inside the Jump‑Desk. Keep repository credentials protected and treat the remote repository—not the VM disk—as the authoritative copy.
Use the Jump‑Desk as a separate Windows 11 environment for Windows-specific behaviour, desktop-browser checks and client application testing.
Use PowerShell and permitted Windows command-line tools interactively. Jump‑Desk is not an unrestricted runner for continuous automation, mining or stress workloads.
Run compatible local development services for your own session, subject to the blocked-port policy. A Jump‑Desk is a personal desktop, not public hosting for a website, API or database.
These are examples, not bundled software or compatibility guarantees. Check the current requirements and licences for the exact versions you intend to use.
PS C:\workspace> git clone https://example.com/your-project.git
Cloning into 'your-project'...
PS C:\workspace\your-project> npm install
Packages installed
PS C:\workspace\your-project> npm test
Tests: passed
PS C:\workspace\your-project> git pushFrom the developer’s perspective, the loop is familiar: connect to the Jump‑Desk, install the toolchain, retrieve the project, build and test, then commit and push before ending the session.
The important difference is operational: the Windows computer is remote. Network quality affects interaction, and stopping the machine must be done through the Jump‑IT dashboard—not by merely closing the remote desktop window.
The same location and tier system as the Jump‑IT app
Choose the available Jump‑Desk region nearest to you, then compare the Windows development capacity in Standard, Pro and Pro+. Selecting a location changes the destination image and loads that region’s current pricing from Jump‑IT.
Choose a region near your regular workplace, then check the available plans.
Every tier can be created with Hours, Months or Years. Choose the tier for the software requirements first, then choose the billing plan for how often the development workspace will run.
WINDOWS CLOUD PC
For lighter editors, command-line work and narrowly scoped Windows testing.
MORE ROOM TO MULTITASK
A practical starting point for many compatible IDE, browser and local-tool workflows.
WINDOWS CLOUD PC
For compatible builds and multitasking that benefit from more CPU and memory.
Current regional prices load from Jump-IT. Review the final price and availability in the product before purchase.
Hours uses prepaid funding. Compute is charged while running; the separate service charge continues while the desktop is retained. Months includes up to 300 hours of uptime per month. Check taxes, included usage and the complete terms in Jump-IT.
Developer recommendation: compare your IDE, SDK, browser and local-service requirements with the tier specifications. Pro is a sensible starting point for many workflows; choose Pro+ when the compatible workload genuinely benefits from 4 vCPU and 16 GB RAM.
Open live Jump‑Desk configurationLive prices vary by Azure region and use the currency selected above. Taxes, currency conversion, service charges and checkout conditions may apply; the final configuration and total shown by Jump‑IT at checkout take precedence.Select a location and currency above for current prices.
Choose Jump‑Desk for the right development job
Personal desktop, server or managed fleet?
Jump‑Desk is deliberately positioned between buying another developer laptop and operating infrastructure: it is a personal Windows cloud desktop, not a public server and not an enterprise VDI control plane.
Personal cloud workstation
Best when one developer wants Jump‑IT to create and manage access to a persistent Windows 11 Pro desktop, with region, plan, tier, status, connection and billing presented through the product workflow.
Server infrastructure
Better when the goal is server infrastructure: public services, server-level networking and direct operating-system administration that you will configure, secure and maintain yourself.
Organisation-managed desktops
Better for central IT teams that need centrally governed identities, policies, application delivery and lifecycle control across a larger managed workforce.
The exact Jump‑IT journey
Check the IDE, SDKs, runtimes, storage, GPU, virtualisation and port requirements against the current Jump‑Desk specifications and limitations on this page.
Open Create Jump‑Desk and choose an available region, Hours/Months/Years billing and Standard/Pro/Pro+ performance tier. Review the live total before checkout.
After creation, use the dashboard power control to start the Jump‑Desk. When its status shows Running, the Connect control becomes available.
Select Connect to download the personalised .rdp file, open it in the compatible client for your device and sign in with the credentials shown on the Jump‑Desk card.
Use administrator access to install licensed compatible tools. Work inside Windows, commit and push valuable changes, and keep a separate backup of anything irreplaceable.
Finish writes and builds, close applications, disconnect the client and then stop the Jump‑Desk through Jump‑IT. Closing the remote desktop window alone does not stop an Hours machine.
Protect the work, not only the machine
Treat the Jump‑Desk as a working copy, not the only copy. Commit and push frequently, especially before major changes, plan transitions or deletion.
Do not commit tokens, passwords or keys. Use the appropriate secret-management method for the toolchain and protect the Jump‑IT and repository accounts.
Windows 11 Pro is included as stated. You remain responsible for licences and subscriptions for IDEs, SDKs, databases and other third-party tools.
For Hours, disconnecting is not stopping. Stop the Jump‑Desk in the dashboard and review session history and usage so costs remain visible.
Technical limits developers should know
The following constraints are important enough to check before moving a development workflow.
Direct developer answers
Yes, when the tools fit Windows 11 and the selected CPU, memory, storage and network limits. Jump‑IT creates the Jump‑Desk, gives you administrator access, shows its status and credentials in the dashboard, and provides the personalised RDP file used to connect from a supported client device.
You have administrator access and can install Windows 11-compatible development applications. Check each tool’s current system requirements, storage needs and licence terms before selecting a tier. Jump‑IT does not include third-party software licences.
These tools can depend on hardware virtualisation, nested virtualisation or Windows features that are not advertised in the current Jump‑Desk specifications. Do not assume they are supported; ask Jump‑IT Support to confirm your exact requirement before purchasing.
Jump‑Desk is designed as a personal Windows desktop, not as a public web server or VPS. Its locked-down network policy blocks several inbound service ports, including 80, 8080 and 8443. Use an appropriate hosting platform or VPS for public production services.
Yes. The Windows desktop, installed tools, settings and files remain while the Jump‑Desk exists. Stopping is not deletion. Important source code should still be committed to a remote repository and backed up separately.
Standard can suit lightweight editing and command-line work. Pro adds 8 GB RAM and SSD storage and is the practical starting point for many IDE-and-browser workflows. Pro+ provides 4 vCPU and 16 GB RAM for more demanding CPU and memory workloads. Always check your toolchain’s requirements.
Yes. The current Jump‑IT workflow supports multiple Jump‑Desks under one login, with each deployment managed and billed independently. This can help separate projects or test environments, but it is not an automated cloning or ephemeral-environment service.
Hours charges running usage while the Jump‑Desk is started, plus a separate per-hour service fee for retained storage and the public IP while it exists. Months includes 300 hours of uptime per month and automatic shutdown after three idle hours. The current Years configuration lists unlimited usage and uptime. Regional prices and the final total are shown in the live Jump‑IT creation flow.
No. Closing the remote desktop client only disconnects the session. Stop the Jump‑Desk from the dashboard when finished. Running compute usage ends when it is stopped, while the Hours service cost can continue for retained resources while the Jump‑Desk exists.
The Jump‑IT Team reviewed the current Jump‑Desk creation flow, regional pricing, tier configuration, regional map, dashboard connection options, network restrictions, account support content and service terms in Jump‑IT on 16 July 2026. Unsupported GPU claims were excluded because the current Standard, Pro and Pro+ specifications do not list dedicated graphics.
Microsoft describes Windows App as software for connecting remotely to Windows devices and applications across supported platforms. Exact client features vary by platform. Read Microsoft’s Windows App overview.
Technical compatibility depends on the exact software version and configuration. Check the live Jump‑IT creation flow before purchasing and contact Jump‑IT Support when a tool requires GPU acceleration, virtualisation, special drivers, unusual ports or more storage.
SEE THE PRODUCT IN ACTION
These recordings show the current Jump-IT interface with demonstration data. Use the controls to pause, replay or view a recording full screen.
Name your desktop, choose a region and plan, and review the configuration before checkout.
Find the display settings, adapt the connection to your screen, and download the connection file.
CURRENT WORKFLOWS · SEPTEMBER 2026
An assistant can help draft a report, explain a formula or plan a workflow, while the final task still depends on a Windows desktop application, plug-in or client system. Start with that application and its requirements. A browser-based assistant alone is not a reason to add another computer; a compatible Windows-only workflow may be.
A retained Jump-Desk keeps that Windows environment available between sessions. For colleagues doing the same kind of work, Jump-Teams adds invitations, roles and desktop assignments. AI subscriptions, Microsoft 365 and other paid applications require their own licences; a cloud PC does not include those subscriptions or promise specialist GPU hardware.
Read the business guide to invitations, roles, funding and desktop assignments.
Explore Jump-Teams →Follow a practical onboarding checklist, from a first pilot to reviewing access when a role changes.
Read the team onboarding guide →Eligible Hours desktops use prepaid funding. Compute charges apply while running, and the separate service charge continues while the desktop is retained. Stopping the desktop preserves its files and ends running compute charges; deleting it permanently removes the desktop. Review the wallet, current rates and funding permissions in Jump-IT before creating one.
For regular work, Months includes up to 300 hours of uptime per desktop each month. Review the current Years option when a longer commitment suits the requirement. Each desktop has its own plan, region and performance tier.
Compare current plans →Create a persistent Windows 11 Pro Jump‑Desk for a Windows-only toolchain, temporary project or separate test environment—then connect from the device you already use.
The GPT-6.1 Terra Windows-workflow guide brings together launch data and independent evaluations, then follows a field-service client from an AI-assisted brief through a real Windows build, acceptance checks and Team handover. Use the workflow with your chosen model and tools.
The Surface Laptop Ultra guide examines CUDA and Windows on Arm checks; the touchscreen MacBook Pro guide covers the Apple-silicon alternative. Choose each project’s execution environment explicitly. Keep local model experiments, Windows builds, repository access and acceptance evidence separate, and validate the actual dependency stack before committing to hardware or cloud capacity.
Related device guidance added 31 October 2026.
