Deploy Your Omnigent

Everything in the previous sections runs on your laptop. That's the fastest way to get started, but when you want your omnigent accessible from your phone, shareable with teammates, or running while your laptop sleeps, you need to deploy.

This section covers Omnigent's architecture and the deployment options for each component.

Architecture

Omnigent has three components:

Server

The server is the central coordinator. It manages:

• Session history. Every conversation, message, and tool call is persisted in a database (Postgres or SQLite).
• Artifacts. Files, omnigent bundles, and uploads.
• Catalog. Registered omnigent specs and built-in omnigent.
• MCP proxy & policies. Proxies MCP tool calls with server-side policy enforcement.
• Skills. Skill definitions that omnigent can load.
• Auth & accounts. User authentication (built-in accounts or OIDC/SSO).

Runner

The runner executes omnigent loops. It manages the harness (Claude Code, Codex, Claude SDK, etc.), runs tools, and streams events back to the server over WebSocket.

By default, the runner is a process on your laptop:

omni host <server-url>

This is why your local Claude Code or Codex installation "just works." The runner has direct access to your machine's tools, files, and credentials.

The runner can also be hosted in the cloud as a cloud runner, so your omnigent executes in a cloud container instead of on your local machine. Supported hosting platforms:

• Modal
• Daytona

More platforms are on the way.

UI

The web UI, terminal UI, and mobile UI all talk to the server. They never talk to the runner directly. This means:

• If the server is on your laptop, UI access is local only
• If the server is deployed to the cloud, any device can reach it, including your phone

Deploy the server to the cloud

The server and runner deploy independently. Moving the server to a cloud host gives you:

• Mobile & remote access. The web UI is reachable from any device, anywhere.
• Shared history. Teammates can see and continue each other's sessions (see Team collaboration).
• Always-on availability. The server stays up even when your laptop is closed.
• Multi-user auth. Built-in accounts or SSO for your team.

See Cloud platforms and Docker for ways to host it.

Host the runner in the cloud

Moving the runner to a cloud runner gives you:

• No laptop dependency. Your omnigent runs even when your machine is off.
• Cloud-native tooling. Your omnigent can access cloud resources directly.
• Isolation. Each omnigent runs in its own container, separate from your local environment.
• Scalability. Run many omnigent in parallel without taxing your machine.