Developers

Deploy and operate, programmatically.

Everything the dashboard does is intended to be available through an API — so agencies and platform teams can manage many instances from their own tooling.

API design preview · illustrative

Interface

A single surface for instances.

The deployment state machine is explicit, so your automation can react to each transition instead of polling a boolean.

qioi api · example

# Create an instance from a tested template
POST /v1/instances
{
  "application": "openwebui",
  "plan": "standard",
  "region": "yyz1",
  "domain": "chat.acme.qioi.app",
  "update_channel": "tested"
}

# → deployment transitions through:
#   queued → provisioning_server → configuring_network
#   → installing_application → issuing_ssl
#   → running_health_checks → ready

Capabilities

What you can build on

Deployment API

Create, resize, restart, snapshot, and delete instances through a single API surface.

Scoped API keys

Per-organization keys with least-privilege scopes and usage logging.

Deployment webhooks

Subscribe to state-machine transitions from queued through ready, failed, or rolling_back.

Application templates

Structured template metadata — images, resources, ports, volumes, health checks, backup policy.

The API is described here as a design direction; endpoints are not yet live in this demonstration.

Manage many instances from your own tooling.

Agencies and platform teams: reusable templates, client separation, and central management are core to the QIOI model.

Read the docs Contact QIOI