ry deploy web --source .

One cloud for apps,data and agents.

Ship it yourself, or let your agent. One API, one bill, and limits your agent cannot talk its way around.

curl -fsSL https://get.rytiv.com/install.sh | sh

~20 s to roll out a new version, with zero dropped requests

211 to 255 ms to wake a sleeping app

Measured on our own fleet. The roll-out: two machines from one version to the next under load, 234 requests through the load balancer, zero non-200. The wake: first request against a sleeping machine, end to end, a machine up to 2 GB whose host has room.

A drawing of a server cabinet with nine units. The top unit is a sled, drawn in orange, sliding out of the cabinet.

Stop stitchingproviders together.

Database, files, mail and cron right next to your app. And when your client asks where it runs: in the EU.

GitHubNext.jsNode.jsViteAstroSvelteGoElixirPhoenixRustPythonDjangoRailsLaravelBunDenoDockerClaude CodeCodexCursorOpenCodeMCPPostgreSQLS3

ry rollback web

Deploy on a Friday.Roll back without a rebuild.

A drawing of a server chassis with three sleds. The middle sled, in orange, is pulled far out; its board, heat sinks, memory and fans are visible. The other two stay in place.

Run ry deploy or connect the repository. A new machine gets traffic only once it answers. Until then, your users get the old version.

Connect GitHub once.

ry git connect web --repo acme/web --branch main

Every push deploysBuilds and rolls out the same way ry deploy does.
A preview per branchAn app of its own, protected by a link.
Closed with the pull requestOr after 14 idle days.

Apps in detail

machines per app: 1 to 20
memory per machine, from 128 MB: 16 GB
error rate watched after a deploy to machines: 5 min

A real capture from our fleet, 1 August 2026

$ ry apps create ledger-api
✓ app ledger-api created
  ry deploy ledger-api --image <oci-image>
$ ry deploy ledger-api --source .
building ledger-api from .
✓ built node app (40afbf82)
rolling deploy ledger-api → nl-ams
✓ deployed ledger-api (.)
new machines:  75b7423a
retired:       none

console.rytiv.com

Prefer to click?It is all here too.

An illustration of the console, not a live account

Home

Example team, runs in the EU

New

AppsView all

NameStatusMachinesSizeLast deploy

lledger-apiledger-api.rytiv.app running 2 machines 1 GB, 1 vCPU 40afbf8

ccheckout-webcheckout-web.rytiv.app running 3 machines 512 MB, 1 vCPU 7c19e02

rreport-workerreport-worker.rytiv.app sleeping 1 machine 2 GB, 2 vCPU aa10f2c

mmedia-proxymedia-proxy.rytiv.app running 1 machine 512 MB, 1 vCPU 3f2a91c

iinvoice-renderinvoice-render.rytiv.app sleeping 1 machine 1 GB, 2 vCPU 9d04be1

PostgresView all

ledger-dbPostgreSQL 16, 0.25 to 2 CUrunning

ledger-db-trybranch of ledger-dbsleeping

reports-dbPostgreSQL 16, 0.25 to 2 CUsleeping

ComputersView all

dev-1base, 2 vCPU, /data 100 GBrunning

agent-1small, 1 vCPU, /data 50 GBsleeping

Storage

ledger-uploadsbucket, attached to ledger-api

SandboxesView all

sbx-1a2b3c4d5e6ffrom app:ledger-apirunning

sbx-7f3e9a10c2d4from app:checkout-webrunning

Volumes

ledger-datavolume, 20 GB

Your database,
as it was yesterday.

Fork any moment of its history into a database of its own, or restore the original in place.

Asleep, memory and CPU stop counting.

Give an app a sleep rule. An idle machine up to 2 GB sleeps with its memory, and the next request wakes it.

runningMemory while awake, CPU while it computes
sleepingMemory kept as a snapshot, billed at the snapshot rate
runningThe first request brought it back in 211 to 255 ms

$ ry machine suspend 1595c340
✓ 1595c340 ● suspended
...
x-rytiv-wake-ms: 240

A real capture, 1 August 2026. The 211 to 255 ms above is the first request against a sleeping machine, end to end, a machine up to 2 GB whose host has room.

A drawing of a cage of four disks. One disk, in orange, is pulled out of the cage.

Volumes outlive machines.

Stop the app, deploy it, replace its machine: the data on the volume stays.

A drawing of a long row of disks on a line. The line splits at a junction. Its branch, in orange, feeds a second row that holds only the few disks it wrote; dashed lines from the empty bays read through to the row behind.

to branch, copy-on-write: seconds
of history by default, 1 to 30 per database: 7 days
autoscaling by default: 0.25 to 2 CU
storage limit: 4 to 500 GB

ry postgres branch appdb appdb-try --expires-in 1d

Test the migrationon a copy of production.

A branch is ready in seconds and stores only what it writes. Over MCP, your agent writes on a copy, never on the original.

Its own password.A branch is a database of its own. Its writes never reach the source.
Read-only otherwise.Without a branch, the agent's SQL runs read-only, and the database refuses the write.
Expires on its own.Set an expiry from 60 seconds to 30 days.

Serverless Postgres in detail

A drawing of a single computer with its lid open. The processor and one bank of memory, what is running right now, are orange. A disk of its own sits at the front in white.

ry computer create dev-1 --size base

One computer per agent.Its work is still there tomorrow.

Work kept in /data outlives the machine. Your agent drives; you watch the desktop or take the keyboard.

small: 1 vCPU, 2048 MB, 50 GB home
base (default): 2 vCPU, 4096 MB, 100 GB home
large: 4 vCPU, 8192 MB, 128 GB home
Idle shutdown: after 10 minutes without activity
Installed: Node.js, Codex, OpenCode, git

Computers in detail For coding agents

api.rytiv.com/v1/mcp

Limits in the key.Not in the prompt.

Give each agent its own key. A production key reads and changes nothing, whatever the prompt says.

sandbox: Everything an API key may do, inside the apps on its list.
twin: The same, for a copy of production.
production: Reads. Any change is refused.

For coding agents For developers

Connect your agent One hosted MCP server, 24 tools

https://api.rytiv.com/v1/mcp

Add a custom connector with this address. You sign in and approve it once in the console. No key to paste.

With a key

claude mcp add --transport http rytiv https://api.rytiv.com/v1/mcp --header "Authorization: Bearer <your key>"

Your key in place of <your key>. Add --scope user to use it in all your projects.

With a key

codex mcp add rytiv --url https://api.rytiv.com/v1/mcp --bearer-token-env-var RYTIV_TOKEN

Set RYTIV_TOKEN in the environment Codex starts from.

With a key

ry mcp install --cursor

Writes the entry for you. It reads your key from RYTIV_TOKEN and never contains it.

With a key

{
  "mcpServers": {
    "rytiv": {
      "type": "http",
      "url": "https://api.rytiv.com/v1/mcp",
      "headers": { "Authorization": "Bearer ${RYTIV_TOKEN}" }
    }
  }
}

Any MCP client that speaks Streamable HTTP with a bearer header.

Give it a key with limitsfor every client that takes a key

# for trying things out, limited to two apps
ry keys create claude-code --agent sandbox --app web --app web-try
# for production: it reads, and changes nothing
ry keys create claude-code-prod --agent production --read-prod-data

curl -X POST "https://api.rytiv.com/v1/tokens" \
  -H "Authorization: Bearer $RYTIV_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"name": "claude-code", "agent": {"class": "sandbox", "apps": ["web", "web-try"]}}'

const res = await fetch("https://api.rytiv.com/v1/tokens", {
  method: "POST",
  headers: { Authorization: `Bearer ${process.env.RYTIV_TOKEN}`, "Content-Type": "application/json" },
  body: JSON.stringify({ name: "claude-code", agent: { class: "sandbox", apps: ["web", "web-try"] } }),
});
const { token } = await res.json(); // shown in this answer only

import os, requests

res = requests.post(
    "https://api.rytiv.com/v1/tokens",
    headers={"Authorization": f"Bearer {os.environ['RYTIV_TOKEN']}"},
    json={"name": "claude-code", "agent": {"class": "sandbox", "apps": ["web", "web-try"]}},
)
token = res.json()["token"]  # shown in this answer only

fetch and requests call the plain REST API: a few lines, nothing to install.

ry usage

Billed by the second.Idle CPU is free.

Memory only while a machine is awake, storage by the gigabyte. No plans, no seats.

Memory	€0.0076 per GB-hour
CPU	€0.035 per vCPU-hour
Disk (volumes)	€0.10 per GB-month
Object storage	€0.022 per GB-month
Snapshots and templates	€0.08 per GB-month
Builds, TLS, custom domains, outbound transfer	Included

A drawing of nine machines on a shelf. Two of them, awake, are orange. The others sleep as faint outlines.

€100 starting credit, valid for 90 days, with a GitHub account at least 30 days old or a saved card.

For businesses and freelancers. All prices excluding VAT.

Introductory pricing until 31 January 2027. Any increase is announced at least 30 days in advance.

See all prices

A drawing of a long row of server cabinets running off the page. A few units in each are orange, awake.

ry deploy web --source .

Folder in.URL out.

Run ry in your project directory: it signs you in, shows what it detected, asks for a name and deploys.

Join the waitlist Quickstart

claude mcp add --transport http rytiv https://api.rytiv.com/v1/mcp --header "Authorization: Bearer <your key>"

One cloud for apps,data and agents.

Stop stitchingproviders together.

Deploy on a Friday.Roll back without a rebuild.

Connect GitHub once.

Prefer to click?It is all here too.

Your database,as it was yesterday.

Asleep, memory and CPU stop counting.

Volumes outlive machines.

Test the migrationon a copy of production.

One computer per agent.Its work is still there tomorrow.

Limits in the key.Not in the prompt.

Billed by the second.Idle CPU is free.

Folder in.URL out.

Your database,
as it was yesterday.