A shared enterprise deep link catalog, published directly from your CI
RYNO's paid web service lets your CI pipeline publish each project's deep links to a shared company catalog. Members sign in with Google or Microsoft, bound to your domain. The owner and administrators invite, remove access and read a governance log: 90 days on Team, 365 days with CSV and JSON export on Business.
Keep the whole organization on the latest routes
- Your CI pipeline
A job publishes the
.ryno/requests of the project on every pipeline of your default branch. - RYNO service
Keeps the published versions and their history. Its data is hosted in France on OVHcloud.
- Members' RYNO apps
Open the catalog and run the same links, with their own devices.
Publication history
Read back what each publication contained: 90 days on Team, 365 days on Business.
Publication history in the docsProject tokens
Each project publishes with its own token, which you can regenerate at any time.
Attach a project in the docsLocal values stay behind
The job sends shared requests and environments. Values you marked as local never leave the runner.
Enterprise governance and access control
| Action | Owner | Administrators | Members |
|---|---|---|---|
| Open the shared catalog in RYNO | Yes | Yes | Yes |
| Attach and publish a project | Yes | Yes | Yes |
| Invite people | Yes | Yes | — |
| Make an administrator, remove a member's access | Yes | Yes | — |
| Remove an administrator | Yes | — | — |
| Transfer ownership | Yes | — | — |
| Read the governance log | Yes | Yes | — |
- Removing access takes effect right away, on every computer where the person was signed in
- Personal addresses, such as Gmail, only join when invited, and are marked External
- The governance log records who did what, to whom, and when
- Team: the governance log reads the last 90 days
- Business: the last 365 days, exportable as CSV and JSON
- Sign in with a Google or Microsoft work account, bound to your domain
On your own, or on a paid plan
.ryno/ alone to a shared catalog.Individual (.ryno/ in Git) | Team — paid plan | Business — paid plan | |
|---|---|---|---|
| Shared catalog from CI | — | 3 projects | Unlimited projects |
| Publication history | Your Git history | 90 days | 365 days |
| Governance log | — | 90 days | 365 days, CSV and JSON export |
| Database | None | Shared service database | Dedicated database |
| Service data hosting | Your Mac | OVHcloud, France | OVHcloud, France |
Questions about the catalog
How does the RYNO catalog get updated?
A job in your CI pipeline publishes the requests and shared environments of a project to the RYNO service with a project token, on every pipeline of your default branch. Every member then opens that version in the RYNO desktop app.
Who can manage members in RYNO?
The owner and administrators invite people and remove access. Only the owner removes an administrator or transfers ownership; members read the catalog, attach and publish projects.
Which accounts can sign in to a RYNO company workspace?
Work accounts from Google or Microsoft, bound to your company domain. A personal address joins only when invited, and RYNO marks it External.
Where is the catalog stored?
The RYNO service stores catalogs, members and the governance log in France, on OVHcloud. Business customers get a dedicated database. Payment, Google and Microsoft sign-in are handled by subprocessors, listed on the security page.