Reference / Limits

Limits

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

Updated 2026-10-21 · View as Markdown

This page lists the limits that are the same on every plan. How many computers and custom domains an account gets, and each computer’s memory and storage, depend on the plan. Billing lists those numbers. Backup retention and counts per plan are on Backups and Reset.

Computers

LimitValue
Address<name>.rtsy.dev, where <name> is the computer’s slug
Slug length3 to 32 characters
Slug characterslowercase a–z, 0–9 and single -, not at the start or end
CPUs per computer8 vCPUs
Computers created per rolling 24 hourstwice the plan’s computer count, and at least 10. Deleted computers count. A refused create says when you can try again.

Some slugs are reserved and can’t be used, including any slug that contains rootsy.

Requests to your apps

These apply to requests that reach your computer at its address or at a custom domain.

LimitValue
Time to first response headers, GET and HEAD15 seconds, including any wake
Time to connect to your app5 seconds
Longest wait between two reads from your app90 seconds
Longest wait between two writes to your app90 seconds
Request body size1,048,576 bytes (1 MiB), counting multipart framing
WebSocket upgradesnot passed through
Paths /_iw and under /_iw/always 404. Your app never sees them.

When a GET or HEAD gets no response headers within 15 seconds, the visitor gets a 503 page with Retry-After: 60. Other methods have no header deadline, but still hit the 90-second read limit. Your nginx’s own default proxy_read_timeout is 60 seconds, so a proxied app gets 60 seconds unless its location sets proxy_read_timeout 90s;. A larger request body usually gets 413, and a much larger one can fail as a dropped connection. When your app returns 502, 503 or 504, or isn’t running, visitors get a Rootsy 503 page instead of your response. Rootsy never retries a request to your app.

Your apps sit behind your nginx on port 8090. See Serve an app.

Ports inside a computer

These ports belong to Rootsy. Don’t listen on them, stop what’s on them, or change their configuration:

PortUse
7681–7687terminal, platform auth, uploads, the Files window, preview control, the terminal relay and MCP commands
8080the platform’s web server that every request passes through
8081the code editor

Port 8090 is your nginx, the web server for your apps. Add config to it, but keep it on that port. Run your own app servers on any other port and proxy to them from 8090. Your computer lists each port.

Outbound network

LimitValue
TCP port 25 (SMTP)blocked, for the computer and its Docker containers, over IPv4 and IPv6
Other outbound connectionsopen

Scheduled tasks

LimitValue
Schedules per computer20
Shortest interval1 minute
MethodsGET, POST
Path length512 characters, starting with /, with no query string
Payload64 KiB of valid JSON, POST only
Name length100 characters
When value length500 characters
Response deadline90 seconds. Your nginx stops at 60 unless the server block sets proxy_read_timeout 90s;.
Retriesnone
Run now1 per minute and 10 per hour, per computer
Changes60 per minute, per computer
History kept30 days, up to 10,000 requests per schedule
Request ID reuse window24 hours
Signed request ageat most 120 seconds old, at most 5 seconds in the future

When several runs are overdue, only the latest is sent, and only within 5 minutes of its time. See Scheduled tasks.

MCP

LimitValue
One MCP request524,288 bytes (512 KiB)
Page size for list_accounts and list_computers1 to 100, default 50
Command script16,384 bytes
Working directory path4,096 bytes
Command time limitdefault 300 seconds, at most 900 seconds
Commands running at once, per computer4. A command started past that never runs.
Command output returnedlast 1,000 journal records, then at most 65,536 bytes
Finished command results kept24 hours. A computer holds at most 1,000 results, running ones included. Past that, new commands don’t start.
File moved by import_file or export_file1 to 262,144 bytes
File path4,096 bytes
Time for one file call60 seconds
Imports in progress, per computer4
Import receipts kept256 per computer, 2,048 per account
Time for one domain change75 seconds

A command’s time limit is also cut to what the account’s Runtime Credits can fund. See Connect with MCP.

Uploads and downloads

LimitValue
File dropped on the terminal100 MiB each, up to 20 files at a time
File uploaded in the Files window10 GiB each
Free disk space a Files upload must leave2 GiB
Unfinished Files uploadsdeleted after 7 days without activity
Download sizeno limit
Entries shown in one folder2,000
Items in one Download selection2,000
File or folder name255 bytes

Files dropped on the terminal land in ~/uploads.

Backups

LimitValue
Manual backups1 per minute
Restores10 per 24 hours, at least 5 minutes apart, failed attempts included
Backup note200 characters
Return pointsthe newest 3 that can be restored

How long backups are kept, and how many manual and pinned backups a computer can hold, depend on the plan. Backups and Reset lists them.

Custom domains

LimitValue
Hostname length253 characters
Labels in a hostname6 at most
Internationalized (xn--) namesnot supported
Time to connect before a domain expires7 days
Time over the plan’s domain limit before the newest domains detach24 hours

A root domain and its www count as one custom domain. Domains are counted across the account. See Domains.

Storage

LimitValue
What countseverything on the disk except the platform’s first 4 GB
Over the plan’s limitTerminal, Editor, uploads and MCP commands pause until the computer is back under 95% of the limit

See Billing.

Organizations

LimitValue
Organizations you can create3
Organizations you can belong to10
Organization name1 to 100 characters
Invitations10 per hour, per member, per organization
Invitation linkexpires after 7 days

See Organizations.