For freelancers, startups and product teams

Ship the product. Skip the platform team.

Push to GitHub and the app is live with TLS. Postgres, buckets, cron and your domain sit next to it, on one API and one bill. Pay for memory while a machine is awake and CPU while it computes. Nothing to migrate to when you grow.

Your job
Get a product in front of users this week, and keep shipping every day after.
What gets in the way
Five services, five bills, five sets of keys, and a migration project when it works.
What Rytiv does
One platform for the whole backend, at the same price per gigabyte at every size. No company name or VAT ID needed to sign up.
What you get

Six things that do the job.

01

Every push deploys

Connect the repository once. Every push to the branch builds on Rytiv's builders and rolls out one machine at a time; a new machine must answer before an old one leaves traffic.

02

A preview per branch

Each preview is an app of its own, protected by a link and closed when the branch or pull request closes. Show the work before it merges.

03

Rollback without a rebuild

Every deploy is a release. If the error rate is clearly worse in the five minutes after a deploy, Rytiv rolls it back on its own. Or run ry rollback.

04

Postgres that branches

PostgreSQL with copy-on-write branches ready in seconds, forks from any moment in its history and point-in-time restore in place.

7 days of history by default Docs: Postgres that branches →
05

The rest of the backend

S3-compatible buckets with presigned URLs, cron that calls a path or runs a command, custom domains with certificates that renew themselves.

06

Costs that follow usage

Give an app a sleep rule and it sleeps when idle. Memory while awake, CPU while it computes, storage by the gigabyte. No plans and no seats.

€0.0076 per GB-hour of memory Docs: Costs that follow usage →
A typical setup

From a folder to a product, in five commands.

The same steps work in the console, or through your coding agent in plain words.

  1. ry deploy shop --source .

    Detects the framework, builds, answers on https://shop.rytiv.app

  2. ry postgres create appdb
    ry attach appdb --to shop

    DATABASE_URL arrives as a managed secret

  3. ry bucket create shop-uploads
    ry bucket attach shop-uploads --to shop

    S3_* variables with a key for exactly this bucket

  4. ry git connect shop --repo acme/shop --branch main

    Every push to main deploys from now on

  5. ry domains add shop shop.example.com

    Set the records it prints; the certificate follows

Why one platform

The same primitives on day one and at scale.

One bill in euro

Prepaid credit, drawn as it runs. At zero, machines stop and nothing is deleted.

One set of keys

The console, the ry CLI, the REST API and the MCP server see the same apps and use the same keys.

Room to grow

1 to 20 machines per app, up to 16 GB and 16 vCPUs each, and Postgres that stores every commit on more than one storage node.

Ship it this week.

No plans, no seats.

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

For businesses and freelancers, from a solo developer to a team. Pricing