A cross-OS agent that registers a computer with your Ocalt account and gives it a name. From then on any Ocalt service can address it, via shell execution, tunnelling, peer-to-peer networks, self-hosted websites on your own hardware, file transfers, content serving, and streaming a local port to a web-accessible endpoint. No static IP address and no firewall limitations.
Windows · Linux · Android · free on every plan
Nothing is installed beyond the agent itself. It holds an outbound connection to Ocalt and does what your scripts ask of it.
EXEC runs a command and hands back stdout, stderr and the exit code. KILL stops one that is still running.
UPLOAD, DOWNLOAD, READ, WRITE, and LIST FROM to browse the machine's folders and drives.
Expose a local port at a public HTTPS URL. No static IP, no port forwarding, no router configuration.
SERVE puts one file behind a public URL with its extension intact, straight off the machine's disk.
SCREENSHOT, VIEW, SCREEN for display geometry, and mouse, keyboard and pointer control.
Point the agent at a folder and a port and your own hardware serves the site — your disk, your machine, your bandwidth. .oql files still execute on Ocalt, so the same script runs identically here and on a subdomain.
WAKE sends a magic packet to another machine on the same network. STATUS reports online state and approximate location.
Stream a camera or a file out as RTSP, with QUALITY and TIME controlling resolution and start point.
POLL sets how often a machine looks for work — one second by default, up to sixty minutes for a metered or battery-powered link.
Name two or more machines and get back a network value you can address as a whole.
Move a file straight from one peer to another. Non-blocking — you get a status anchor and poll it.
Expose one peer’s port on every other peer’s localhost. Nothing is published to the internet.
Group several of your machines into one network and they can reach each other directly — the bytes travel between them, not up through Ocalt and back down.
One binary. It opens its own interface at localhost:12345.
Your Ocalt identity and API key, plus whatever you want to call this machine. The alias is the name your scripts will use.
Any OcaltQL script & service on your account can now reach it — from the console, a scheduled job, or a site you host.
The agent dials out to Ocalt and holds the connection. Nothing listens on a public port, nothing needs forwarding, and no inbound firewall rule is required. A machine on a phone tether is as reachable as one in a rack.
A machine is bound to the Ocalt account whose credentials it holds. No other account can address it.
The same on every plan, including Free. Register as many as you have.
Commands reach the machine within a second by default, adjustable per machine up to sixty minutes.
Downloading the client is half of it. The device still has to be registered to your account before anything can reach it, and that is the step that turns a program running on a machine into a machine you can use from anywhere.
Have the client running and the device online, then register it under the alias you gave it. The device answers for itself, so nothing is taken on trust.