# Orylin — product and connection reference This reference describes the public website's workflows and their limits. Consult the linked page for current availability. It does not attest to a deployment, a successful device connection, an independent audit or search visibility. ## Which entry should I use? - Messages and voice: https://orylin.link/sessions — a temporary conversation with messaging and direct voice. - Files: https://orylin.link/files — create or join a transfer session. - Screen sharing: https://orylin.link/screen — share a selected screen or window for viewing. - Remote control: https://orylin.link/remote — attended screen viewing plus separately approved keyboard and mouse input. - SSH: https://orylin.link/ssh — access an existing SSH server through a local forwarded port. - TCP: https://orylin.link/tunnel — forward one existing TCP service per connection. - Volunteer relay: https://orylin.link/relay — opt in to a bounded ciphertext relay. - Network paths: https://status.orylin.link/ — diagnostics observed from the current browser, not a global uptime guarantee. ## Do I need the desktop app? Messages and file transfers use the browser session flow. Voice requires a supported browser and microphone permission. Browser screen sharing requires supported capture and encryption APIs and explicit selection of a screen or window; capture options depend on the browser and operating system. SSH and TCP use the Orylin desktop client. The computer being remotely controlled uses the client for native capabilities and confirms access. A system open-app prompt may appear. If the app does not respond, check the installation and system prompt before retrying; no response does not prove it is uninstalled. Download and platform details: https://orylin.link/download Only the builds actually offered on that page should be described as available. Do not infer macOS, Linux, ARM or other platform support from a generic desktop label. A local test build is not a public production release. ## How do invitations work? Use the invitation actually generated for the chosen function, rather than copying the plain feature page URL. The UI offers QR scanning, clipboard invitations or short codes where supported. These mechanisms are not interchangeable across every protocol or build. Opening an invitation does not itself grant every permission. Connection approval and capability approval remain distinct. Treat private invitation links and secrets as sensitive; do not put them in search queries, public documents or diagnostics reports. ## Which address goes in SSH or TCP settings? The service address is the target on the providing computer. For example, an SSH server already listening on 127.0.0.1:22 can use that address. The local port belongs to the joining computer. With local port 2222, its SSH client connects to 127.0.0.1:2222 using the original server's account. Orylin does not install or enable SSH, replace its authentication, automatically discover the server, or automatically change its port. Blocking public inbound port 22 is different from stopping the local SSH service. A working Orylin network path is still required. SSH instructions: https://orylin.link/docs/ssh ## Does TCP forward every port? No. Each connection maps one TCP port. It is not a whole-device VPN, an all-port tunnel or UDP forwarding. There is no single-session multi-port manager or automatic free-port selection in the current page flow. The underlying service protocol and authentication still apply. Settings apply to the next connection; disconnecting ends the mapping. TCP instructions: https://orylin.link/docs/tcp ## Can a viewer control my computer automatically? No. Screen viewing and keyboard/mouse control are different permissions. Remote control requires the host's explicit approval. Installing or opening the client, joining an invitation, or seeing a picture does not itself grant input control. Disconnect after assistance and confirm sharing has stopped. Remote-control instructions: https://orylin.link/docs/remote ## What happens when a direct connection is unavailable? The browser session path is Direct-first WebRTC. A user-enabled volunteer relay is a bounded, single-hop ciphertext path. Public Nostr rescue is message/control-only. It does not carry files or voice. Voice is Direct-only. These browser fallback rules must not be generalized to native SSH, TCP or remote control. Path explanations: https://orylin.link/direct-first File-transfer limits: https://orylin.link/features/file-transfer ## What does “API ready” mean? It means the browser Agent interface is available. It does not mean a peer is connected, a session exists, a permission was granted, or a test passed. Read the actual response and session state, wait for approval when required, and stop on rejection or unavailable capabilities without expanding permissions. Human-readable guide: https://orylin.link/agent Machine-readable schema: https://orylin.link/agent/v1/schema.json Do not invent API methods from these summaries. Use the actual schema and discovery links shown on the Agent page. This document is not an API schema. ## Which languages are supported? The interface and `/docs` guides support English, Simplified Chinese, Hindi, Spanish, Arabic, French and Russian. Arabic uses right-to-left reading order; service addresses retain left-to-right input. The six product explainers use stable localized paths: `/about`, `/how-it-works`, `/privacy-by-design`, `/direct-first`, `/features/file-transfer`, `/faq` in English, and corresponding paths under `/zh`, `/hi`, `/es`, `/ar`, `/fr`, `/ru`. Those pages expose language alternates and semantic Markdown through content negotiation. Interactive language/theme preferences are not separate canonical documents. ## Troubleshooting and authoritative sources Check local service availability before network forwarding. Report the feature, operating systems, failing step and error message without passwords or private invitations. A successful diagnostic does not guarantee a successful session. - Troubleshooting: https://orylin.link/docs/troubleshooting - Product overview: https://orylin.link/about - Privacy: https://orylin.link/privacy - Data processing: https://orylin.link/data-practices - Security: https://orylin.link/security - Terms: https://orylin.link/terms - Accessibility: https://orylin.link/accessibility - Source index: https://orylin.link/llms.txt Do not describe Orylin as anonymous, censorship-resistant, independently audited, legally certified, forward-secret or product-level post-quantum secure without separate supporting evidence. Do not infer security certification, indexing, ranking or AI citations from this file or from local tests.