What Rootsy handles
The work Rootsy does around your code that a rented server, an app builder or a set of cloud parts leaves to you.
Sleep and wake
A computer sleeps when nothing needs it and wakes when a request arrives. It spends no Runtime Credits while it sleeps. A rented server bills for every hour. See Sleep and wake.
Sleep asks one thing of your apps. Running processes can restart on wake, so keep state on disk.
An address and HTTPS
Every computer gets an HTTPS address with no DNS setup. Rootsy manages the certificate. Connect your own domain with a CNAME record, and Rootsy issues its certificate too. See Addresses and custom domains.
Backups and Reset
Rootsy backs up each computer in use automatically. Make your own before a risky change. A restore winds the computer back. Reset rebuilds a broken system and keeps everything under /home, /root and /srv. System packages, configuration and databases installed with apt return to factory state. Docker data isn’t touched by Reset, and backups don’t include it. See Backups and Reset.
Jobs on a timetable
A schedule sends a signed request to your computer at the times you choose. The request wakes the computer if it’s asleep. Cron can’t do that on a machine that sleeps. See Scheduled tasks.
Many computers, shared
Each project can have its own computer. Create one from the dashboard, or from an AI tool over MCP. An organization shares its computers with every member. See Organizations.
Your code in plain files
Your app is code in files on a Linux computer. Use any language or framework that runs on Linux. Your AI writes the code, and you can read every line of it. See No lock-in.
Kept apart from your apps
Your workspace and your apps sit on separate hostnames. A page your app serves never shares an origin with your terminal. Requests from the internet reach a computer only through Rootsy’s edge. See Security.
What stays with you
You have root, so the software you install is yours to update. Rootsy doesn’t patch it. Rootsy puts no login in front of your apps, so add one where you need it. Secrets you store are ordinary files on the disk. See Security.
A narrower way in
There’s no SSH, and only HTTP requests come in. WebSocket upgrades don’t pass through. If your software needs those, a plain server suits it better. Limits lists the rest.