Skip to content

Run AI agents on infrastructure you control.

Orchestrator Zero (oz0) runs AI jobs across your own machines. For platform and IT teams that need control of tools, model spending and the work that reaches their systems.

The agent runs on the laptop node. Management and Edge are roles of the oz0 server. Edge connects the node to Temporal for workflow history and, in this example, to your chosen model. The agent uses allowed tools to read a web page and write a summary. Temporal can run with the server or externally.

From observations to a decision.

Agents gather evidence and propose an action. Your rules decide what can run and when a person must approve it.

From an alert to a reviewed actionIllustrative workflow · integrations required
Your systemsAI agentPeople

01 The problem

Service alert

“Checkout is slow.”

02 The agent investigates

AI agent on your node

Uses permitted tools to check the evidence

Read permitted logs

Find the failing service.

Check its health

Compare errors and responses.

The agent proposes a restart

Your Ask rule holds the tool call.

03 People decide

A person reviews the call

oz0 Console → Approvals

04 The outcome

Approved

Restart, then recheck

Runs after remaining checks pass.

Agent reports health; oz0 records results and cost.

Denied

No restart

The agent reports its findings.

Timeout also denies the call.

Both possible outcomes are shown. No real actions run.

Example: add restart tools and approval rules to host-health.

Follow an IT incident More tasks: networks, code reviews and evidence

Why oz0 matters

Useful work, with limits you set.

oz0 runs your agents with compatible hosted or self-hosted models. Keep jobs, rules and history together as models change. You choose the task, tools and access.

  1. How it works

    One server process runs management, the edge and embedded Temporal by default. Nodes run the agents. You can separate the server roles or use an external Temporal backend.

    oz0Node

    Your machines run the agents

    A node is a machine that runs your agents. Laptops, GPU workstations and cloud VMs join with one command and connect out to your server.

  2. oz0Edge

    Check actions before they run

    oz0 checks supported tool calls against your rules. The edge role, the server’s gateway, holds model-provider keys and checks configured budgets before model calls leave.

    node-7f3acalls the model gateway

    1. Certificate is validmTLS
    2. Node is allowedregistry
    3. Job is within budget$1.62 left

    passed toModel gateway

    Example model call. The server checks the node’s identity, access and configured budget.

  3. Temporal

    Keep completed work when a run is interrupted

    Temporal saves completed workflow steps and waits. Recovery of an interrupted step depends on how it runs.

    node-7f3anode-21c9planmodel_callnode lostretryreviewdone
    Example run. Completed workflow steps come from history. Recovery of the interrupted operation depends on how it runs.

  4. oz0Management

    Manage the work from one place

    The management role serves oz0 Console for jobs, approvals and spending. With roles running separately, runtime work can continue through a management outage within cache and buffer limits.

    Cost by agent, last 7 days

    Example data

    pr-reviewer
    $41.80
    test-runner
    $23.15
    code-explainer
    $9.40
    triage-bot
    $6.25
    $80.60 across 4 agents this week.

Built on Temporal. Connect the tools your team uses.

  • Docker
  • Kubernetes
  • Prometheus
  • Grafana Tempo
  • SQLite
  • Model Context Protocol
  • Ollama
  • Pydantic
  • PostgreSQL
  • OpenTelemetry
  • GitHub
  • uv

Start with one useful task.

Explore the docs and choose a first task. Try the local demo when the software is released.

Docs

  1. Choose a small problem

    Start by investigating one failed connection. Decide what evidence the person on call needs to see.

    See the example task

  2. Define its boundaries

    Choose tools and a model. Set access, approval rules and a budget before using real data.

    Understand the controls

  3. Check that it helps

    Compare the answer with the source observations. Check cost, human effort and recovery before repeating the task.

    Plan your first test

Apache 2.0 core. Your infrastructure.

The core is Apache 2.0 licensed. Public source access is coming soon. You operate the deployment and pay for your infrastructure and model services.

What’s included hello@oz0.ai

Built in Sweden, under Swedish and EU law. For everyone.

Meet Rev

Our arctic fox brings the journey to life. The name comes from revontulet, the Finnish word for the northern lights: fox fires.

The northern lights over northern Europe at night, seen from the International Space Station, with city lights below.

What would you give an agent first?

Explore a task your team already does, then decide what access, evidence and review it needs.

Find a first taskContact us