Technical reference

Reference for a Rootsy computer: the OS and user, preinstalled software, the directory layout, what persists, and the ports and paths that belong to the platform.

When a Rootsy computer sleeps, what wakes it, what survives, how to keep it awake for a long job, and when the workspace pauses.

Show your work in the workspace's Preview window with rootsy preview, open apps that need a real browser window, and check that a page works.

Reference for rootsy, the helper command on every Rootsy computer: each subcommand with its flags, output and exit codes.

Automatic and manual backups of a Rootsy computer, pinning and retention limits per plan, what a restore replaces, and what Reset keeps and wipes.

The error pages, banners and command messages you can see on Rootsy, each with its cause and what to do.

Run one-off and long-running jobs on a Rootsy computer, from its terminal or over MCP, and keep them alive through sleep.

Run a job on a timetable: a schedule sends a signed request to an endpoint on your Rootsy computer, which verifies it and does the work. Manage schedules from the workspace, the rootsy command or MCP.

Serve a static site or a running app from a Rootsy computer through nginx on port 8090, deploy new versions safely, and the request limits that apply.

Your Rootsy computer's address at <name>.rtsy.dev, connecting a domain you own with CNAME records from the workspace or over MCP, root domains and www, and what each status means.

Add a password with nginx basic auth, or sign-in inside the app, since Rootsy doesn't put a login in front of what a computer serves.

Connect Claude, ChatGPT or another MCP client to Rootsy, then create and manage computers, run commands, read files back, and manage schedules and domains through its 29 tools.

Personal accounts and organizations on Rootsy: creating one, inviting and removing members, what every member can do, and deleting it.

What each Rootsy plan enforces (computers, memory, storage, domains, monthly Runtime Credits), what spends credits, what happens when they run out or a plan ends, and how to cancel.

Every Rootsy limit that's the same on all plans: computer names, request deadlines and sizes, ports, schedules, MCP, uploads, backups, domains and organizations.

How Rootsy is put together, what it protects, what you must protect on your computer and in your apps, what Rootsy's systems can reach, and how to report a security problem.

Where your files and backups live, how to download a copy, and what deleting a computer, organization or account removes for good.

Customer-visible changes to Rootsy by date, newest first: new features, changed behavior and fixes you would notice.