The platform for agent developers

Write the agent. Skip the plumbing.

Your agent gets a database, RAG, object storage, queues, secrets and an LLM gateway in seconds — through an SDK built for Claude Code, Codex and Cursor to drive.

$ npx@stackbone/cliinit
Read the docs

Works perfectly with

default.workflow.ts SDK
import { sb } from '@stackbone/sdk' export default sb.agent({ on: 'lead.created', run: async (e) => { const ctx = await sb.rag.search(e.body) return sb.ai.complete({ ctx }) },})
stackbone.config.ts declare
runtime: node20database: postgresrag: index: leadsapproval: hitlguardrails: strictevents: - lead.created# one recipe, many installs
Stackbone control plane ready
Autonomous agents
Workflows
Database
RAG index · leads
HITL inbox
Guardrails
micro-VMs
Event routing
LLM gateway
Object storage
Queues
Secrets
Observability
Automations
/Stackbone DemoProsupport-botStudio
support-bot

bystackbone-demorunningv2.14.3created2026-08-19 10:04 active

datapath reachable p95 142 ms · checked 2 min ago
region eu-west-1 aws · byoc
connectors 5 linked Gmail expiring · Notion broken
secrets 6 stored oldest rotated 2026-08-09
agents
64 healthy
workflows
75 with schema
rag
540 documents · 2 collections · 22,530 chunks last ingest 2026-09-07 14:32
approvals
4waiting for a decision
last 20 runs
13 done · 3 failed · 2 in flight · 2 interrupted
7b13d630…c4e failed
Agent / Workflow
invoice-parser
Trigger
job
Started
14:18:40
Duration
612 ms
Tokens
—

note input rejected: invoice_id missing from the job payload

The platform

Everything an agent needs,
and the loop to ship it.

SDK

A typed client over your whole agent stack — plus control-plane facades that exist nowhere else.

Open SDK

Local development

Run and hot-reload your agent against a control plane identical to production — zero infra to stand up.

Open CLI & emulator

Studio

A visual console for every run: trace waterfalls, logs, data explorers — same UI local and cloud.

Open Studio

Human-in-the-Loop

Pause a run for a human decision in one call; approvals land in an inbox and resume the run.

Open HITL

Provisioning

Declare what resources and events your agent needs; the platform provisions them and injects the credentials.

Open provisioning

Managed runtime

Every install runs isolated in its own micro-VM with scale-to-zero. You only ship a Dockerfile.

Open runtime

Eval

Declare a quality suite and run it locally today against real provisioned resources; publish gating lands in V1.

Open eval

Publish & monetize

Package once, install many. Deploy today; the public catalog with payouts comes next.

Open publish
Build flow

Four commands, start to ship.

step4/4
01
@stackbone/cli init
  • add

Scaffold agent.yaml, Dockerfile and HTTP-contract handlers — your coding agent takes it from there.

02
@stackbone/cli dev

Hot-reload against the embedded emulator — a control plane identical to production.

03
@stackbone/cli eval

Run the quality suite against real provisioned resources. No fresh report, no publish.

04
@stackbone/cli publish

Build, sign, version and deploy. Each install gets its own isolated instance.

Agent/Workflow in Production
Control plane

Publish a template once. Run it inside every organization.

A Template is the published recipe. Each Installation runs it inside one organization — its own secrets, config and runs. Promote a new build and every new install boots from it; existing ones stay pinned until each operator chooses to update.

Workspace template · published
lead-triage 3 agents · 2 workflows
Agents
  • triageclassifies inbound leads
  • enricherpulls CRM + firmographics
  • routerassigns the right owner
Workflows
  • on-new-leadevent
  • nightly-resynccron
bld_2f91a7c0 · 1 publish
Acme Corp
inst_2f91
Northwind Logistics
inst_4d18
Bytehouse
inst_c012
Meridian Health
inst_6c2e
Helios Energy
inst_9f3a
Vela Labs
inst_3b71
Triggers

Every event lifts the right workflow or agent.

Connect the platforms your work already lives in. Each event runs the workflow or agent it's wired to — Stackbone handles the routing, retries and signing in between.

Compare

They host your code.
Stackbone hosts your product.

Hosting platforms
Your agent stays a deployment.
  • You run the code; the unit of work stays one-off, per client.
  • No packaging — every customer is a fresh setup you maintain.
  • No per-install provisioning, no billing — that's still your plumbing.
e.g. Modal · Railway · Vercel · LangGraph Platform
Stackbone
Your agent becomes an asset.
  • Package once as a versioned template — one recipe, many installs.
  • Each install is provisioned whole and billed — distribution built in.
  • Open HTTP contract — /invoke /health. You can always leave.
pricing Pricing today: one-time fee per install · subscription & pay-per-invocation on the roadmap
Quickstart

From nothing to a
running agent.

3 commands. Nothing else to install or configure.
Start building Read the docs
stackbone-cli
$npx @stackbone/cli login
✓ Logged in as [email protected]
$stackbone init support-triage
✓ Agent support-triage created · starter hello-world
agent.yaml · Dockerfile · src/index.ts · src/schema.ts
$stackbone dev
✓ Docker services ready
✓ Agent migrations applied
✓ Emulator listening
✓ Tunnel ready
Open Studioapp.stackbone.ai/acme/installations/inst_8f2a
Tunnelquiet-pine-42.tun.stackbone.ai
Locallocalhost:4242
Protocolv12 · 9 capabilities
agent live · watching for changes
$