← All use cases

Remote Agents

Remote should mean you can reach it from anywhere — not that it lives somewhere you can’t see. Most setups host the agent in a vendor cloud and punch holes back to your systems, putting your most privileged automation as far from your data as possible. Flip it: trigger from anywhere, run on hardware you own, discover services over a network only your agents can see.

“Remote” got the wrong end of the stick

The usual answer to “trigger an agent from anywhere” is to park it in someone else’s cloud and open a path back to your real systems. Now the thing with the most access lives furthest from your data, on a network you don’t run.

The trigger should be remote. The compute should be yours. Those two things were never supposed to be the same decision.

Remote trigger, local compute

01

Trigger anywhere

Fire an agent from a webhook, a cron schedule, an external service, or the desktop app on a phone.

02

Discover services

Agents find your databases, tools, and APIs by name on the intranet — no brittle wiring, nothing exposed publicly.

03

You hold the keys

Register machines across metal and cloud into one private network and set exactly what each agent can reach.

# Register a machine into your private network
heyvm net join worker-01

# Expose a service to agents on the intranet — not the internet
heyvm bind worker-01 5432 --network internal
→ postgres.worker-01.heyo.internal

# A remote trigger lands; the agent runs on your hardware
heyvm trigger nightly-report --on schedule "0 6 * * *"

Hosted in their cloud vs. triggered into yours

This is the layer nobody else sells. Sandboxes give you isolation. Vibe-coding tools own distribution. Databases rent you a data plane. None of them give you a network where agents discover services and you keep control. That’s the whole point of Heyo.

Hosted in a vendor cloud

  • Compute sits outside your perimeter
  • Holes punched back to your real systems
  • Discovery and access wired by hand
  • Bound to one app’s runtime

heyo Remote Agents

  • Triggered remotely, run on your hardware
  • Services stay on a private hosted intranet
  • Agents discover services on their own
  • One network across metal and cloud

Reach your agents from anywhere

Remote triggers, private discovery, compute that never leaves your control.