Frequently asked questions about RYNO

Yes. The RYNO desktop app is free on your Mac and needs no account, no seat and nothing to host. Your requests live in a folder next to your code, and your run history stays on your Mac. A company pays only when it shares a catalog with the Team or Business plan.

The .ryno folder is where RYNO keeps your work, inside your own repository. Each deep link request is a JSON file in it, next to your environments and flows, so your team reviews a change with the rest of your code. Local secrets stay in *.env.local.json files, which Git ignores and RYNO never uploads.

RYNO is published for macOS only, on Macs with Apple Silicon and Macs with an Intel processor. There is no RYNO build for Windows or Linux. For Android, adb ships inside RYNO; for iOS simulators and iPhones, RYNO needs the Xcode command line tools. The minimum macOS version is not published yet.

RYNO sends a deep link to an Android phone or emulator through adb, which ships inside the app. RYNO listens to adb, so a phone appears as soon as it is plugged in, and RYNO escapes the link before the shell of the phone reads it, so characters such as & reach the app intact.

Not on a physical device. On an iPhone or iPad connected by cable, RYNO sends the link through devicectl and cannot confirm that the device received it, so RYNO reports the link as sent, never as a success. On an iOS simulator, RYNO sends the link through simctl, with the Xcode command line tools.

The RYNO MCP server lets an AI assistant on your Mac list your collections, environments, devices and flows, and run a deep link. RYNO keeps the server off until you turn it on, listens only on your own machine, and keeps changing files and running links off until you allow them.

The RYNO shared catalog is what your company's pipeline publishes from a repository: shared collections and shared environments, stored as dated versions and never edited. Members of your company see it in RYNO after signing in. Flows and local secrets are not published, and your local requests stay in your repository.

People sign in to RYNO with the Google or Microsoft account their company gave them, and there is no RYNO password. Single sign-on that your company configures itself, with SAML or OIDC, and automatic provisioning with SCIM are not available. The desktop app alone needs no sign-in at all.

RYNO has two roles, administrator and member, and no third. Only administrators manage members, remove a project or remove someone's access. Removing access cuts every session that person has, on every computer, and refuses their next sign-in. The governance log records who did what, on what, and when.

On Team, RYNO keeps 90 days of publication history and shows the last 90 days of the governance log. On Business, both windows are 365 days, and the log exports in CSV and JSON. On every plan, RYNO keeps a governance log line 365 days; the plan decides how far back administrators read.

The RYNO company service, its databases and their backups are hosted in France, on OVHcloud. The shared catalog, accounts and members, and the governance log live there. Team uses the shared service database, filtered by company; Business gets a database of its own on the same server in France.

Only the data of the RYNO company service stays in France, on OVHcloud. Stripe handles payment and invoicing, and Google or Microsoft confirm identity at sign-in: they are subprocessors, each outside the OVHcloud hosting. Requests and local secrets in the RYNO desktop app stay on your Mac and never reach the service.

The RYNO desktop app keeps requests, environments, local secrets and run history on your Mac. RYNO asks whether a newer version exists, unless you turn Updates off, and sends anonymous usage data only if you turn it on, to Mixpanel in its EU region. That data never holds a URL, a name or a secret.

RYNO sales answer them. Write to bonjour@isee-u.fr with the questions your security review, your data protection officer or your purchasing team need answered, including how your company's data is processed. The RYNO security page describes what stays on the Mac, what the service stores in France, and each subprocessor.