October Infrastructure Sale · code OCTOBER15 — until 1 Nov See the offer →
BPO · Data entry · Managed desktops

Data-entry desktops that can’t walk out the door.

One Windows server, many RDP seats — the work, the files and the audit trail all live on your server, not on a freelancer’s laptop.

The data-entry model has a structural problem: send files to remote workers and you’ve lost control of the data — copies on unknown laptops, unknown USB drives, unknown WhatsApp backups. An RDP setup inverts it: the work lives on your server, and workers connect to it. Files never leave; access ends the day the contract does.

It’s also the cheapest way to standardise. Everyone gets the same desktop — same Excel version, same fonts, same folder structure — regardless of whether they’re on a ₹15,000 laptop or a phone. Your process, one image, zero "it works on my machine".

And it’s auditable: one server means one place to check who worked on what, instead of trusting screenshots of spreadsheets.

Set up in 5 steps.

  • 1. Size the server: ~1GB RAM per concurrent user — Bungalow (8GB) covers ~6 seats, Manor (16GB) ~14.
  • 2. Deploy Windows, receive admin credentials, install the tools your team uses (Office, your CRM, browser profiles).
  • 3. Create a standard Windows user per worker — no admin rights, no ability to install.
  • 4. Disable clipboard/drive redirection for workers if files must not be copied out — mstsc options control this.
  • 5. Hand out the server IP; revoke a user the day they’re done.

Recommended tiers

Bungalow — $8.79/mo
4 vCPU / 8GB — ~6 concurrent seats
Deploy →

Manor — $19.49/mo
8 vCPU / 16GB — ~14 concurrent seats
Deploy →

Common mistakes

  • • One shared login for the whole team — no audit trail, sessions stomp each other. A user account per worker is free.
  • • Leaving drive/clipboard redirection on — that’s the copy-files-out channel; turn it off for worker accounts.
  • • Buying per-seat "cloud desktop" pricing — an RDP server you manage is dramatically cheaper per seat.
  • • Under-sizing RAM — ~1GB per concurrent seat is the working rule; starving RAM is how RDP gets "laggy".

When this is NOT enough

One VPS is comfortable to ~15 concurrent seats. Past that, run a second server and split teams — or if you need true VDI management (pooled desktops, profile disks, broker), that’s an RDS deployment on dedicated hardware: talk to us rather than stretching one VM.

Real questions

Data entry RDP FAQ

Seats, security and controlling file access.

Ask on Discord ↗
About 1GB RAM per concurrent seat is the working rule — 8GB covers ~6, 16GB covers ~14 comfortably.
Not if you disable it — turn off drive and clipboard redirection in the RDP settings for their accounts and files stay on the server.
Each person needs a Windows login — you manage them. Office tools need their own licences as usual. Confirm RDS licensing terms for large teams.
Any device that runs an RDP client — old laptops, tablets, phones with "Windows App". The server does the computing.
One server = one audit point — login history, file access times, and whatever logging your apps produce, all in one place.
Yes — included on every tier at no extra cost.