A workspace beyond one device
Remote desktop infrastructure for legitimate applications and controlled access.
Content revised · English
- Architecture to evaluate
- RDP / SSH + tmux / remote editor
- Prepared starting points
- 5 plans
- Responsibilities
- Application, rights and recovery
A fit shortlist, not installed software or live inventory.
Keep these in view.
- RDP / SSH + tmux / remote editor.
- Keep the access route narrow.
- Make the work portable.
RDP / SSH + tmux / remote editor
Windows GUI work can suit a compatible RDP product. Terminal work may use SSH with tmux or Mosh, while a developer may evaluate VS Code Remote or code-server. Each requires its own supported application and maintenance; no remote-editor installation is made.
Keep the access route narrow
Use a VPN or source restriction for RDP, verify certificates and enable NLA in a compatible deployment. Review clipboard and drive redirection, separate team accounts and retain a recovery path. More RAM does not grant more licensed Windows sessions.
Make the work portable
Store source, documents and environment configuration in a backed-up workflow outside one session. Test reconnection after restart and recovery to another machine. Containers such as Docker or Podman do not automatically require a promise of nested virtualisation.
Match the operating system
Check the application's platform, licensing and graphics requirements. Windows desktop and multi-user access can have separate licence conditions; verify the exact plan and allowed use.
Keep access narrow
Use strong account authentication, Network Level Authentication where supported and restricted inbound access. A remote desktop exposed broadly to the internet needs careful defence and maintenance.
Keep the work portable
Define where files are stored and how they are exported. Test reconnect behaviour and account recovery, and plan updates around working hours and application availability.
Capacity to consider.
Match these starting points to the representative application. Software installation and live inventory are not connected; the exact specification and period total come from the catalogue.
Dusk 2
Start a Windows workspace with two virtual CPUs, 4 GB of DDR4 memory and 60 GB of SSD storage, managed through administrator RDP access. Choose from the listed Windows Server and desktop editions, with a 1 Gbps port, 3 TB of monthly transfer and application installation tooling.
- Compute
- 2 vCPU (Xeon)
- Memory
- 4 GB DDR4
- Storage
- 60 GB SSD
- Transfer
- 3 TB / month
billed monthly
Dusk 4
Move remote work and Windows applications onto four virtual CPUs, 8 GB of DDR4 memory and 120 GB of SSD storage. The configuration includes Windows licensing, administrator access and a multi-user RDP option, alongside 6 TB of monthly transfer and a 20 Gbps network mitigation tier.
- Compute
- 4 vCPU (Xeon)
- Memory
- 8 GB DDR4
- Storage
- 120 GB SSD
- Transfer
- 6 TB / month
billed monthly
Dusk 8
Give heavier Windows applications eight virtual CPUs, 16 GB of DDR4 memory and 240 GB of SSD storage. Administrator RDP and a configuration supporting up to 20 users sit alongside a 1 Gbps port, 10 TB of monthly transfer and a 40 Gbps network mitigation tier.
- Compute
- 8 vCPU (Xeon)
- Memory
- 16 GB DDR4
- Storage
- 240 GB SSD
- Transfer
- 10 TB / month
billed monthly
Umbra 2
Give web applications, containers or a private tunnel two AMD EPYC virtual CPUs, 4 GB of ECC memory and 60 GB of NVMe storage. Root access on KVM, a 1 Gbps port and 3 TB of monthly transfer provide more room than the entry configuration without moving to dedicated hardware.
- Compute
- 2 vCPU (AMD EPYC)
- Memory
- 4 GB DDR4 ECC
- Storage
- 60 GB NVMe SSD
- Transfer
- 3 TB / month
billed monthly
Umbra 4
Balance four AMD EPYC virtual CPUs and 8 GB of ECC memory with 120 GB of NVMe storage for several services or a growing application. This KVM configuration includes a weekly snapshot, 6 TB of monthly transfer on a 1 Gbps port and a 20 Gbps network mitigation tier.
- Compute
- 4 vCPU (AMD EPYC)
- Memory
- 8 GB DDR4 ECC
- Storage
- 120 GB NVMe SSD
- Transfer
- 6 TB / month
billed monthly
Before this workload goes live.
- Check the exact plan’s CPU, memory, disk, transfer and port.
- Choose a listed region and verify the workload’s permitted use.
- Test the representative application and an independent restore.
Questions, answered.
Can several people share one Windows RDP plan?
Verify the OS and remote-session licensing. Capacity and catalogue RAM do not grant additional concurrent user licences.
Will video calls work well over remote desktop?
Test the client, codec, peripherals and real network route. A usable terminal session does not establish a high-quality video-call path.
Will services recognise the address as a data centre?
They may. A server address is not a residential address or a guarantee of acceptance by a third-party service.
Can I run containers or a remote editor?
Evaluate the actual image, runtime and resource requirements. Neither Docker nor a remote editor is preinstalled by the configurator, and ordinary containers do not imply nested virtualisation.
What is kept in my account workspace?
Your configuration, selected plan, image, location and billing term are kept with the order and payment request references. Quotes, payment-state reads and support conversations remain linked to your account. Read fulfilment details separately from payment status.