Add a machine
Connect a machine to your server and install the plugins it needs. Nodes connect out, so you do not need an inbound port on each one.
Read the docsRun the work where your systems are.
A node is a machine connected to oz0. Use laptops, servers and GPU machines, then send each job to a node with the right tools and access.
Example fleet. Choose work to see where it belongs.
Your oz0 server
Matches the job to a suitable node
Office node
Can reach the private network
Selected for this job
Build server
Has the repository and test tools
Other node
GPU machine
Has a compatible local model
Other node
Check the office network → Office node. The example assumes the needed plugin is installed there.
Keep network checks near the network, repository work near the code and model work near the GPU.
What you can do
Job placement
Label machines by site or purpose. oz0 uses the job’s requirements and available capacity to choose a suitable node.
Read the docsSandboxes
Run supported workloads with limits on files, processes and network access. Check the isolation your operating system and execution mode actually provide.
Read the docsLocal models
Use a compatible model on your own hardware, served by separate inference software. Supported agent types can share model services across the fleet.
Read the docs