XOPC Gateway · Local gateway service

Make your local runtimea connected service.

XOPC Gateway brings the agents, state, and workflows running in your environment to web, mobile, messaging channels, and APIs. It is a unified entry point—not another isolated backend.

Start with Gateway

Start with Gateway

Run your local runtime as a service.

Install xopc, start Gateway, then hand it to your operating system when it should run continuously.

  1. 01 · Install

    Install xopc

    The cross-platform installer prepares the dependencies required to run it.

    curl -fsSL https://xopc.ai/install.sh | bash
  2. 02 · Start

    Start Gateway

    Start the web server and local React console.

    xopc gateway
  3. 03 · Serve

    Install the system service

    Let Gateway run continuously through the operating system service lifecycle.

    xopc gateway service install

From local runtime to service entry point

Run once. Connect from many places.

Gateway exposes a running xopc instance as a controlled entry point, so clients and channels share the same state and execution capability.

01

Run the runtime

Start xopc in an environment you own, retaining local configuration, data, and provider choices.

02

Connect surfaces

Configure web, mobile, messaging channels, or other enabled client entry points.

03

Serve clients

Use Gateway APIs and streaming connections for clients to access sessions, tasks, and runtime status.

04

Operate continuously

Observe service and channel status so the local runtime can operate as a durable service.

One runtime, one service boundary

Put connection capability in one place.

Gateway provides a unified service layer for xopc clients, channels, and integrations, avoiding separate state and auth maintenance for every surface.

One service entry point

Let web, mobile, and other clients connect to one local runtime instead of duplicating agent state.

Gateway APIs and streams

Expose service interfaces for sessions, tasks, state, and real-time updates.

Channel runtimes

Load and manage messaging channel runtimes while keeping those conversation surfaces connected to core agent capability.

Service lifecycle

Manage the local Gateway around start, status, restart, and system-service operation.

Start with a connection need

Ways to use Gateway.

Multi-device

Bring one runtime to more devices

Let web, mobile, desktop, and other surfaces see the same sessions, projects, and execution state.

Channels

Connect agents to messaging surfaces

Let people start and receive the same agent work through connected messaging channels.

Integration

Provide a backend for custom clients

Use APIs and streaming interfaces to bring xopc capability into existing products or internal tools.

Operations

Run continuously as a service

Keep a local AI runtime available over a manageable service lifecycle.

The service remains in your control

Connect more surfaces without giving up the boundary.

Local operation: start Gateway around your own device, configuration, and runtime environment.

Unified state: clients and channels connect to one runtime instead of scattered copies.

Operability: inspect service and channel status, then manage the lifecycle when needed.

The same xopc runtime

Need an agent to complete a concrete computer task?

XOPC Worker brings the runtime behind Gateway into everyday work that can be delegated and confirmed.

Explore XOPC Worker