Type at least two letters to search every page of the docs.

↑ ↓ to navigate ↵ to open esc to close

Guides

rdev compared with other setups

There are three common ways to give yourself and your AI agents a development environment: a local setup on your laptop, a hosted cloud environment such as GitHub Codespaces, or a server you own. This page compares them honestly, so you can pick the one that fits.

At a glance

Local setup Hosted cloud environment rdev on your server
Where the code runs Your laptop The provider's machines Your server
Agents keep working when you leave No, they stop when the laptop sleeps Only until the idle timeout stops the environment Yes, around the clock
Cost model Your hardware Per hour of compute, plus storage A fixed server price plus a fixed rdev plan
Setup You install and update everything A config file per repository One install; projects are added with a command
Who has root and the data You The provider You
Laptop load Heavy Light Light

Local setup

Tools like Docker, Laravel Herd or a hand-built stack run everything on your laptop. That is free and works offline, but every new laptop or teammate means setting it up again, the fans spin during builds and tests, and an agent stops the moment the laptop sleeps. It is a good fit when you work alone, mostly offline, and do not run long agent tasks.

Hosted cloud environments

Services such as GitHub Codespaces start a fresh environment per repository in the provider's cloud. They are quick to start and nothing runs on your laptop. They are billed by the hour of compute, and an environment stops after a period without activity, which also stops any agent running in it. Your code and data live on the provider's machines. They fit short sessions, open-source contributions and teams that already live inside one provider.

rdev on your server

rdev turns a Linux server you rent into a complete environment: PHP and other runtimes, databases, services, trusted HTTPS sites at https://<name>.dev.test and a ready profile for Claude Code, Codex and other agents. The server runs all the time, so agents finish long tasks while you are away, and you come back to the same terminal session from any device. You pay your provider a fixed monthly price for the server and a fixed price for your rdev plan, and you keep root access and your data.

The trade-off: you need a server and an internet connection to reach it. The panel can create the server for you in a few minutes; see Getting a server.

Which one should you pick?

  • Pick a local setup if you rarely run agents for long and want to work offline.
  • Pick a hosted cloud environment for short, per-repository sessions where hourly billing stays low.
  • Pick rdev if you want agents to work while you are away, a light laptop, predictable monthly costs and your code on a server you control.

Every plan comes with a 14-day money-back guarantee on the first payment; see Payments, renewals and refunds.