For enterprises and agencies in Europe

A cloud your security review can check, line by line.

A German company. Your apps, databases and files are stored and run only in the EU, and a machine never leaves its region. The security page answers your review, line by line. Agencies can run an organization per client, with its own keys and its own bill.

Join the waitlist Security and data
Your job
Ship client and company projects on infrastructure that passes procurement and the data protection review.
What gets in the way
Providers under another jurisdiction, and a questionnaire nobody answers plainly.
What Rytiv does
Stores and runs your workloads in the EU as a property of the platform, and answers the questionnaire line by line.
What you get

Six things that do the job.

01

Residency by design

A machine is placed in its region when it is created and stays there: a host move, a host failure or a deploy never takes it out.

One EU region Docs: Residency by design →
02

An organization per client

Once we enable you as a partner, your organization can create organizations it manages, act inside one with a header, and hand it over to the client when the project ends. Your keys stop acting in it.

X-Rytiv-Org Docs: An organization per client →
03

Previews behind a door

A password, or a share link per client with a label and an expiry. Revoke one link without touching the others.

ry protect link Docs: Previews behind a door →
04

Keys per job

A deploy key for one app for CI, a read key for a status page, an expiry on every key. Keys are stored as a hash and shown once.

Up to 365 days expiry Docs: Keys per job →
05

Isolation

Every machine, including a database's compute, runs in its own virtual machine with its own kernel. A database answers only the apps attached to it, over TLS.

One kernel per machine Docs: Isolation →
06

Accounts without passwords

Sign in with a passkey, a one-time code by e-mail, or GitHub where it is switched on. Every account enrols a second factor. Team members cost nothing.

Members included Docs: Accounts without passwords →
A typical setup

A client project, set up the way a review expects it.

A managed organization for the client, keys narrowed per job, a preview only the client can open.

  1. curl -X POST https://api.rytiv.com/v1/orgs/managed \
  -H "Authorization: Bearer $RYTIV_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"name":"client-smith"}'

    An organization of its own for the client, once you are enabled as a partner

  2. ry keys create ci-shop --deploy shop --expires-in 30d

    CI may deploy one app, for 30 days

  3. ry protect link shop-preview --label "client Smith" --expires 30d

    One address for the client, revocable

  4. ry postgres branch appdb appdb-review --expires-in 1d

    Review against real data on a copy that expires

Why Europe

Where your workloads run is a property of the platform, not a setting.

Jurisdiction

Rytiv is run by a German company. Account data and the platform database are held in the EU. The privacy notice names every recipient.

No card numbers

Payment pages are served by the payment provider, and card numbers never reach Rytiv.

Documented answers

Keys, secrets, isolation, TLS, durability and sign-in are on one page, in the terms a questionnaire asks for.

The full answers, item by item: Security and data. Who receives what: Privacy.

Building blocks

Everything on one API.

AppsFrom GitHub, a folder or an image. Rolling deploys, previews, rollbacks. Static sites without a machine.Serverless PostgresBranch in seconds, fork or restore from any moment in its history. Private, TLS only.ComputersA machine per coding agent, a home disk that stays, a desktop you can watch or take over.SandboxesMachines with a deadline from your app's image. Egress allowlist. 100 at a time.StorageS3 buckets with presigned URLs and CORS. Volumes that outlive machines, resizable.MailTransactional mail from your domains, inbound, a delivery log. No advertising or newsletters. Private beta.Cron and jobsCall a path on a schedule or run a command on its own machine. Exit code and output kept.Domains and TLSSet the records the answer names; certificates issue and renew themselves. Included.Network and protectionPrivate app links, password or share-link previews, signed access, egress caps.
Also for Freelancers, startups and product teams →Teams building with agents →

Bring it to your next review.

Read the security page. Questions: write to us.

Join the waitlist Quickstart 
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