Private systems and network reach
Work that cannot leave your infrastructure runs on your infrastructure, with planning and inference still in Opulent's cloud.
Connected Workspaces run Opulent commands on infrastructure you control: virtual machines, containers, Kubernetes clusters, specialized hardware, or a local Mac.
Planning and model inference remain in Opulent's cloud. Commands, file edits, and repository operations run on your workers. Workers connect outbound over HTTPS, so they do not need inbound ports, public IP addresses, or a VPN tunnel.
Use a Connected Workspace when the environment or the data cannot live in a managed cloud workspace. It changes where commands run, not who plans them.
Network policy on a run
Automations and scheduled work carry an explicit network policy alongside their tool allowlist. That policy controls what the run may reach, which matters most for unattended work where nobody is watching the first request go out.
Systems with no API
Some systems the business depends on have no usable API, and replacing them is not on the table. Computer Use covers that case: the run drives the interface the way a person would, under the same boundaries as any other tool.
State which sites are in scope, what the agent may change, whether files may move in or out, and which actions require approval. If a site blocks the managed browser, the run should stop and route the exception rather than imply the action succeeded.