Opereo AI

Introduction

Opereo AI is a control plane for deploying company AI brains and managing your agent fleet.

Introduction

Opereo AI is a control plane for deploying your company's AI brains and managing the fleet of agents that run them — from one place.

Each project gets its own isolated machine running a real agent runtime. Opereo AI provisions it, configures it, and gives you one UI over the whole fleet instead of a dashboard per agent.

What Opereo AI does

  • Deploy brains — stand up a project on managed infrastructure, no DevOps.
  • Manage the fleet — every agent across every project on one canvas.
  • Connect tools — hundreds of third-party services through one-click connectors.
  • Automate — scheduled tasks and messaging channels per agent.
  • Control access — organizations, members, roles, and API keys.
  • Build on it — the full REST API behind the UI, for platforms that provision and manage agents for their own users.

How it fits together

An organization owns projects. A project runs one or more engines — agent runtimes, each kind on its own substrate — and each engine hosts agents, each with its own instructions, skills, tools, channels, and schedules.

organization
└── project
    └── engine  (an agent runtime — Hermes today, more kinds to come)
        └── agent  (instructions, skills, tools, channels, automations)

Built for platforms

The UI is a client of the REST API — everything you can click, you can call. If you're building a product that deploys and manages agents for your own users, Opereo AI is the control plane behind it. One org-scoped API key drives the whole lifecycle: create a project per customer, provision an engine per seat, install an agent from a template, hand out a WhatsApp link. Your users never need to see opereo.

Open source

Opereo AI is MIT licensed and self-hostable — see Self-hosting to run it on your own infrastructure. Source: github.com/genlabs-ai/opereo-ai.

Next steps

  • Quickstart — create your workspace and your first agent
  • Concepts — projects, engines, agents, and connectors
  • Engines — the engine contract, and Hermes
  • Architecture — how provisioning and the control plane work
  • Self-hosting — run your own Opereo AI
  • API — drive all of it over HTTP

On this page