Skip to content
Orquestio Docs

Introduction to Orquestio

Orquestio is a SaaS platform that deploys and manages autonomous AI agents, fully isolated per customer. Each tenant gets its own compute instance running inside a Docker container — no shared resources, no noisy neighbors.

The first product deployed through Orquestio is OpenClaw, but the platform is blueprint-driven: any containerized AI agent can be packaged and offered as a managed service.

Core concepts

Section titled “Core concepts”

Tenants

Section titled “Tenants”

A tenant is a customer. Each tenant owns one or more instances — isolated EC2 machines running their AI agent. Tenants never share compute, storage, or network with each other.

Blueprints

Section titled “Blueprints”

A blueprint is a template that defines what gets deployed. It specifies the Docker image, configuration, resource sizing, and any post-provisioning tasks. For example, the openclaw blueprint deploys an OpenClaw container with the correct environment variables and health checks.

When you create an instance, you reference a blueprint by name. The orchestrator handles the rest.

Orchestrator (Control Plane)

Section titled “Orchestrator (Control Plane)”

The orchestrator is a FastAPI service that exposes the Orquestio API at https://api.orquestio.com. It is responsible for:

  • Provisioning — spinning up tenant infrastructure via Terraform and AWS
  • Lifecycle management — starting, stopping, upgrading, and destroying instances
  • Health monitoring — proxying health checks to each tenant’s instance
  • Task dispatch — sending shell operations to instances via AWS SSM (custom domains, upgrades, etc.)

All operations are API-driven. The orchestrator never requires SSH access to tenant machines.

Instances

Section titled “Instances”

An instance is the running environment for a single tenant. Each instance:

  • Runs on its own EC2 machine
  • Has a dedicated Docker container with the AI agent
  • Gets a unique access_url once provisioned
  • Transitions through well-defined states: provisioning → running → stopped / destroying / destroyed

Portal

Section titled “Portal”

The portal is an Odoo-based customer-facing application where tenants can manage their instances, view usage, and configure settings. Under the hood, the portal calls the same orchestrator API documented here.

Architecture overview

Section titled “Architecture overview”
┌─────────────┐       HTTPS        ┌──────────────────┐
│   Portal    │ ──────────────────▸ │                  │
│  (Odoo)     │                     │   Orchestrator   │
└─────────────┘                     │   (FastAPI)      │
                                    │                  │
┌─────────────┐       HTTPS        │  Terraform + AWS │
│  Your code  │ ──────────────────▸ │  SSM dispatch    │
│  (API call) │                     └────────┬─────────┘
└─────────────┘                              │
                                             │ provisions & manages
                              ┌──────────────┼──────────────┐
                              ▼              ▼              ▼
                        ┌──────────┐  ┌──────────┐  ┌──────────┐
                        │ Tenant A │  │ Tenant B │  │ Tenant C │
                        │  EC2 +   │  │  EC2 +   │  │  EC2 +   │
                        │  Docker  │  │  Docker  │  │  Docker  │
                        └──────────┘  └──────────┘  └──────────┘

Authentication

Section titled “Authentication”

All API requests (except GET /health) require a Bearer token:

Terminal window
curl -H "Authorization: Bearer <API_KEY>" https://api.orquestio.com/instances

API keys are provisioned by your Orquestio administrator.

Next steps

Section titled “Next steps”

Ready to deploy your first instance? Head to the Quickstart.