RDPSchool is not a separate company or service. The brand has been retired and rdpschool.com now points here permanently.
Same team, same servers, same support — new name. Existing RDPSchool accounts, services and renewals continue exactly as before; only the name and the web address have changed.
Cursor · Remote SSH · Self-hosted agents
Cursor does not live on a VPS the way a website does. A server fits in three different ways, and this page explains each one with the exact commands. Then the plans: a private Linux VPS with full root and a dedicated IP, from $14.99₹1,389.27 a month for 4 GB.
HOW IT FITS
The first two use a Linux VPS from this page. The third needs a server with a desktop.
| 1. Remote SSH | 2. Self-hosted cloud agents | 3. Cursor on a remote desktop | |
|---|---|---|---|
| In one sentence | The editor stays on your computer. The code and the terminal live on the VPS. | The VPS becomes a worker. You start tasks from cursor.com/agents and they run on your server. | The whole Cursor app runs on a remote machine that you open like a screen. |
| What you run on the server | Nothing by hand. You only need SSH access. | agent login, then agent worker start, kept running. | The Cursor desktop app. |
| Open ports | SSH only. | None. Outbound connections only. | Remote Desktop only. |
| What you need from Cursor | The Cursor editor and your Cursor account. | Premium or higher, Teams, Enterprise or a legacy paid plan. Team Pools need Enterprise. | The Cursor app and your Cursor account. |
| Server to pick | Linux VPS on this page, 4 GB. | Linux VPS on this page, 4 GB or more. | Ubuntu RDP, or a Windows RDP with a Windows 10 image. |
| Good for | Daily coding on a project that should stay on a server. | Handing off tasks and checking back later. | People who want one always-on desktop with everything in it. |
The worker can run on your server. The models and the Cursor service cannot. With a self-hosted worker, the repository is checked out on your VPS and the builds and commands run there, but Cursor states that inference still happens in its cloud. A VPS does not replace a Cursor plan, and nothing here runs Cursor offline.
WAY 1
The server needs nothing installed by hand. Most of the work is making sure plain SSH works first.
Choose a plan below and pick Ubuntu 24.04 on the order form. The IP address and root password arrive by email.
Log in as root once and make a user for your work. Replace YOUR_SERVER_IP with the address from the email.
ssh root@YOUR_SERVER_IP
adduser dev
usermod -aG sudo dev
exitAdd these lines to the file ~/.ssh/config on your own computer.
Host cursor-vps
HostName YOUR_SERVER_IP
User devThen run ssh cursor-vps in a terminal. If it logs you in, SSH is ready.
In Cursor on your computer, open the command palette, choose the Remote SSH command for connecting to a host and pick cursor-vps. Cursor sets up its own server process on the VPS the first time, which takes a moment.
Open a project folder on the VPS. The editor, chat and agent look the same as before, but files are saved on the server and terminal commands run there.
WAY 2
This is what the searches for "cursor agent worker start" are about. It needs a Cursor plan that includes Cloud Agents.
Log in as the normal user from the steps above. tmux keeps the worker alive after you disconnect, and the last command is Cursor's official CLI installer. The CLI is called agent.
ssh dev@YOUR_SERVER_IP
sudo apt update && sudo apt install -y tmux git
curl https://cursor.com/install -fsS | bashStart a tmux session and log in. The server has no browser, so this form of the command prints a login link. Open the link on your own computer or phone and approve it.
tmux new -s cursor
NO_OPEN_BROWSER=1 agent loginPut the repository on the server, then start the worker. Cursor's instruction is simple: keep this process running.
git clone https://github.com/you/your-project.git
cd your-project
agent worker startPress Ctrl+B then D to leave tmux with the worker still running, and close your terminal. Start tasks from cursor.com/agents. To look at the worker again later, reconnect and re-attach.
tmux attach -t cursorPRICING
Cursor publishes no server requirement for Remote SSH. Our suggestion is the 4 GB plan, so the remote server process, your language servers and indexing have room. Billed monthly, with no long contract.
| Plan | vCPU | Memory | Storage | Bandwidth | Setup | Price | |
|---|---|---|---|---|---|---|---|
| 4GB Plan Recommended | 4 vCPU | 4 GB | 80 GB SSD | 5 TB | Instant | $14.99/mo₹1,389.27/mo | Buy Now |
| 6GB Plan | 4 vCPU | 6 GB | 100 GB SSD | 5 TB | Instant | $19.99/mo₹1,852.67/mo | Buy Now |
| 8GB Plan | 6 vCPU | 8 GB | 100 GB SSD | 5 TB | Instant | $29.99/mo₹2,779.47/mo | Buy Now |
| 16GB Plan | 8 vCPU | 16 GB | 100 GB SSD | 5 TB | Instant | $59.99/mo₹5,559.87/mo | Buy Now |
WHY A VPS
Cursor works fine on a laptop. These are the reasons people still put the project on a server.
A worker on a VPS is still there at night. Start a task from the browser, close everything, and read the result later.
The agent worker only makes outbound connections. Cursor says no inbound ports, public IPs or VPN tunnels are required.
With Remote SSH or a self-hosted worker, the repository and build tools sit on a server you control, not on a laptop that travels.
Installs, test runs and dev servers use the server's processor and memory. Your own computer only draws the editor.
Every server has its own IPv4 address. Preview the app at the same address every day, or allow that one address in a database firewall.
If an agent leaves the system in a mess, reinstall the operating system from the client area and begin again.
SIZING
| What you run | Plan to pick | Why |
|---|---|---|
| Remote SSH on one web app, API or script project | 4 GB | Room for Cursor's remote server process, the language servers for your code, indexing and a dev server. |
| Remote SSH plus Docker, a database or a large repository | 8 GB | Containers and a database each take their own memory on top of the editor's side of things. |
| One self-hosted agent worker | 4 GB | The agent installs packages, builds and runs tests on this machine, like a developer would. |
| Several agent tasks at once, or a full stack that stays up | 8 GB or 16 GB | Each running task and each service needs its own share. |
| Cursor desktop app on a remote desktop | Ubuntu RDP, 4 GB and up | A graphical desktop is a different product from the terminal-only VPS on this page. |
| Small scripts and bots, no Cursor | 1 GB or 2 GB | Fine for light programs. We do not suggest them for Remote SSH. |
A Cursor VPS is an ordinary Linux server that you pair with Cursor. Either you connect the editor on your computer to it over SSH, or you run Cursor's agent worker on it and send it tasks from the web. Every VPSLake plan is a private KVM virtual machine with reserved memory, SSD storage, full root access and its own IPv4 address.
You do not need this if you code on one computer, your projects fit on it and you close Cursor when you stop for the day. Cursor on a laptop is complete on its own. You also do not need a VPS just to use cloud agents: Cursor runs those in its own managed machines unless you choose to bring your own.
We deliver a clean server with the operating system you picked, a root password and a fixed IP. Nothing is preinstalled and there is no one-click installer, which is a plus here: you run Cursor's official installer and get the version Cursor ships today. Cursor needs its own account and plan, bought from Cursor and not included in the price of the server. For the server side, such as SSH access or a reinstall, support answers by ticket, WhatsApp and Telegram seven days a week.
Cursor does not publish a memory, processor or operating system requirement for the server end of Remote SSH, so nobody can quote you an official number. What we can say is how it behaves. Cursor places its own server process on the VPS, and your language servers and the code index run next to it. That is our reason to suggest 4 GB. Use a current Ubuntu such as 24.04. Upgrading to a bigger plan later keeps your files and needs only a reboot.
There is no GPU in these servers. Cursor does not need one, because the model runs in Cursor's cloud, but it also means you cannot run a large local model here and point Cursor at it. A VPS has no screen, so the Cursor desktop app itself does not run on it. For that, use an Ubuntu desktop server, where Cursor installs from its apt repository with sudo apt install cursor, or a Windows RDP with a Windows 10 image. Cursor names Windows 10 and later and does not state Windows Server support.
You choose the location on this page: Miami, Florida, Frankfurt, Germany or Amsterdam, The Netherlands. With Remote SSH the closest location feels the most responsive. For an agent worker it matters much less. If you would rather use a terminal agent than an editor, the same server works as a Claude Code VPS or a Codex VPS.
Cursor is a product of Anysphere. VPSLake is an independent hosting provider and is not affiliated with Anysphere.
Pay the way you already pay
FAQ
agent worker start, so the repository is checked out there and the builds and commands run there. The AI models and the Cursor service itself cannot be self-hosted: Cursor states that inference stays in its cloud.agent login, run agent worker start and keep that process running. You then start tasks from cursor.com/agents, and the work happens on your server.NO_OPEN_BROWSER=1 agent login. It prints a login link instead of trying to open a browser. Open that link on your own computer or phone and approve it. The other documented way is an API key set as CURSOR_API_KEY.Order a 4 GB VPS, connect over Remote SSH or start an agent worker, and keep your project in one place. Billed monthly, cancel when you like.
EXPLORE