Security
What the connection allows
Idlerate is designed so a remote agent or bot can run inference on models you already installed — and nothing else on the host.
- Outbound only
- Models only
- No code execution
Outbound only
The Idlerate client on your PC opens an outbound connection to relay.idlerate.dev. It does not listen for inbound connections. You do not need to open ports on your router.
Inference on installed models only
A job that arrives through the relay can call your local Ollama to generate text (or embeddings) on a model that is already on the machine. Idlerate never asks Ollama to pull models during a job. The client does not create model files, delete models, or run arbitrary Ollama admin commands on behalf of a job.
Nothing can start processes or run code
The client accepts a fixed set of message types from the relay. A job cannot open a shell, start an executable, write files outside the result path the client controls, or update Idlerate itself. There is no remote desktop and no file browser.
Keys you control
Agents and bots authenticate with API keys you create in the dashboard. You can revoke a key at any time. Scope keys to the tools you want them to use. A key can use every machine on your account.
Pause or disconnect
- Pause from the system tray when you are gaming or need the GPU. Queued jobs wait.
- Disconnect a machine from the dashboard to stop it accepting work.
- Revoke a key if you no longer trust that client.
- Quit the Idlerate app to close the outbound connection entirely.
When your PC is off
If the machine is asleep, powered off, or offline, jobs sit in the queue until it reconnects or they time out. Nothing runs on a machine that is not connected.
This page describes how the product is built. It is not a guarantee against every possible risk. Keep Ollama and Idlerate updated, and treat API keys like passwords.