Get a machine online in two minutes
ollalink is a self-hosted control plane for remote access. Install a lightweight agent on any machine, claim it into your workspace, and connect from your browser. This guide is the fast path.
Quickstart — one-line install (Windows)
The fastest way to add a machine. The agent installs, points itself at ollalink, and joins your workspace automatically.
- In the dashboard, open Devices → + Add device → Generate install command.
- Copy the command and run it in PowerShell on the machine you want to control (run as the logged-in user, not an elevated/SSH shell):
$env:OLLALINK_ENROLL='et_…'; irm https://ollalink.com/install.ps1 | iexThat's it. The machine appears in Devices — online — within about 30 seconds. The enrollment token is one-time and scoped to your workspace; you can revoke it anytime.
Manual install (advanced)
If you'd rather not run a script, install the branded agent yourself and claim the device by hand.
- Download the branded Windows agent from
downloads.ollalink.com(also linked from the dashboard's Add device panel). It ships pre-pointed at ollalink — no network settings to change. (macOS build: coming soon.) - Run the installer, open ollalink, and note the Device ID and Access Code it shows.
- Enter both in the dashboard's Add device → Claim form. The device joins your workspace.
The agent connects to wss://signaling.ollalink.com out of the box. The current build is unsigned, so Windows SmartScreen may warn — choose "Run anyway".
Connecting from your browser
Remote control happens entirely in your browser — there's nothing to install on the machine you're connecting from. Only the target machine runs the ollalink agent.
- Open
Devicesand click Connect on any online machine. - The session opens right in the dashboard over WebRTC — full keyboard and mouse, adaptive quality, with relay fallback for tricky networks.
One click, already signed in. For machines added with the one-line installer, Connect is fully automatic: you're signed into the session and connected with no access code to type (the installer seeds a managed, workspace-scoped access code). Machines claimed by hand will ask for their access code once.
Prefer a dedicated window? The same browser client is available standalone at web.ollalink.com.
Core concepts
A tenant. Devices, members, sessions, API keys, enrollment tokens, and usage are all scoped to a workspace.
The agent is the app on a host machine. Once it registers and is claimed, it's a device in your fleet with live online status.
A revocable, workspace-scoped secret (et_…) used by the one-line installer to auto-join a device. Generate and revoke them from Add device.
A brokered remote-control connection. Its duration is metered into the workspace's session_minutes.
The operator side runs entirely in the browser — embedded in the dashboard's Connect view, or standalone at web.ollalink.com. No install on the machine you connect from.
The one-line installer seeds a fixed, workspace-scoped access code on the agent and stores it with the device, so the dashboard can broker a one-click connection with nothing to type.
Workspaces & invites
Invite teammates by email from Platform → Members with a role of owner, admin, or member. Once they accept, they see the same fleet and can connect to any device. Removing a member revokes access immediately.
Usage & billing
Each completed session adds to session_minutes; online devices feed active_devices. See both under Settings → Plan & Usage. Plan limits are enforced in-app; metered usage can be pushed to a payment processor or kept internal.
Troubleshooting
Open the agent so it finishes registering, then use Add device → Claim with the Device ID + Access Code it shows. Make sure you ran the command as the logged-in user, not over SSH.
The signaling/WebRTC link is up but the host has no active desktop to capture — the machine must have an interactive session (logged-in screen) for frames to flow.
Confirm the agent is running and the machine can reach signaling.ollalink.com (outbound 443). Relays handle NAT automatically.
The current agent build isn't code-signed yet; choose "Run anyway". Signed builds are on the roadmap.
The REST API covers devices, sessions, members, and usage.