Xtrape CapsuleA lightweight control plane for AI-era Capsule Services.

What is Xtrape Capsule? ​

Xtrape Capsule is an open governance system for the long tail of small services that power modern AI products — integration adapters, automation workers, background jobs, private tools, and AI Agent runtimes.

Instead of stitching together a service mesh, a config center, a monitoring stack, and a backstage, you get one lightweight control plane that speaks to your services through an embedded Agent.

Capsule Service  ──[Agent SDK]──▶  Opstage Backend  ◀──  Opstage UI

Why Capsule Services? ​

Most "services" in an AI product are not classic microservices. They are:

• short-lived workers
• automation scripts
• integration adapters
• private tool runtimes
• experimental connectors

These deserve runtime governance, not heavy platform engineering. Capsule Services are designed to be registered, observed, configured, operated, and audited — without giving up their lightweight nature.

What is Opstage? ​

Opstage is an agent-based runtime governance control plane for Capsule Services.

Opstage 是面向 Capsule Service 的 Agent-based 运行态治理控制面。

Opstage gives you a clear, single-pane view of every Capsule Service across your fleet — what's online, what's healthy, what config it's running with, what actions it exposes, and what commands have been executed against it.

How it works ​

+---------------------+
|     Opstage UI      |   ← human operator
+----------+----------+
           |
           v
+---------------------+
|  Opstage Backend    |   ← control plane
+----------+----------+
           ^
           |  outbound only
           |
+----------+----------+
|  Embedded Agent     |   ← data-plane agent
+----------+----------+
           |
           v
+---------------------+
|  Capsule Service    |   ← the thing being governed
+---------------------+

1. The administrator creates a registration token in Opstage.
2. The Capsule Service starts with an embedded Agent SDK and registers using that token.
3. The Agent receives a long-lived agent token, sends heartbeats, and reports its services.
4. Opstage tracks inventory, health, configs, and actions through the contract.
5. Operators trigger actions from the UI; Opstage queues commands; the Agent polls and executes them.
6. Every meaningful event lands in the audit log.

The Backend never opens a socket to your services. All connections are initiated outbound by the Agent, which is what makes Opstage runnable behind NAT, on a laptop, or inside customer environments.

Quick Start ​

git clone https://github.com/xtrape-com/xtrape-capsule-ce.git
cd xtrape-capsule-ce
docker compose -f deploy/compose/docker-compose.yml up --build -d

Open http://localhost:8080 and sign in with the bootstrap admin account.

→ Full Quick Start guide

Developer SDK ​

import { CapsuleAgent } from "@xtrape/capsule-agent-node";

const agent = new CapsuleAgent({
  backendUrl: process.env.OPSTAGE_BACKEND_URL!,
  registrationToken: process.env.OPSTAGE_REGISTRATION_TOKEN,
  tokenStore: { file: "./data/agent-token.txt" },
  service: {
    code: "my-capsule",
    name: "My Capsule Service",
    version: "0.1.0",
    runtime: "nodejs",
  },
});

await agent.start();

→ Build your first Capsule Service

Editions ​

→ Compare editions

Use Cases ​

• Integration Services
• Playwright Workers
• Account Pool
• AI Agent Runtime

Roadmap ​

Xtrape Capsule is currently in Public Review before the v0.1.0 Public Preview release. See the full roadmap for what's planned next.

Repositories ​

• xtrape-capsule-ce — Opstage CE backend, UI, deploy
• xtrape-capsule-agent-node — Node.js embedded Agent SDK
• xtrape-capsule-contracts-node — Shared contracts & Zod schemas
• xtrape-capsule-site — This site