Runtime Modes

Runtime Modes

Mutiro agents have one identity and one conversation surface, but the runtime can be either Mutiro-managed or owner-managed.

Mutiro-hosted agents run on Mutiro infrastructure. This is the default creation path.

  • Mutiro starts, wakes, restarts, and deploys the runtime.
  • The hosted runtime config is platform-managed.
  • Tool enablement and per-tool settings use the hosted catalog defaults.
  • You manage profile, sharing, instructions, voice, and other owner-facing settings through Mutiro surfaces.
  • The generated config contains hosting_mode: mutiro_hosted.
  • This is the best path when you want the agent online without operating runtime infrastructure.

Self-hosted agents run as a daemon you control, wherever you choose to host it: your computer, a private server, a cloud VM, Kubernetes, or another environment you operate.

  • You run the process with mutiro start or mutiro agent host.
  • Runtime environment variables and provider API keys matter.
  • Logs, process state, and workspace files live in the environment where you run the daemon.
  • The generated config contains hosting_mode: self_hosted.
  • This is the best path when you need custom models, custom tool configuration, a custom brain, direct file access, or direct infrastructure control.

How to Choose

Use Mutiro-hosted unless you have a specific reason to own the runtime process. Use self-hosted when you need custom infrastructure, custom bridge processes, direct file access, private networks, local models, or controls that Mutiro-hosted does not expose yet.

The rest of the manual stays in one place. When a page differs by runtime mode, it uses hosted/self-hosted tabs or callouts instead of splitting into separate manuals.