Acme Corp
inst_2f91
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.
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
Agent invocations
Run history with live filters and status. Click a row to open the waterfall; retry and cancel actions respect terminal states.
| Run | Agent / Workflow | Trigger | Started | Duration | Tokens | Status | Actions |
|---|---|---|---|---|---|---|---|
| support-bot | chat | just now | — | — | running | ||
| support-bot | webhook | 6 m ago | 1.24 s | 3,418 | done | ||
| triage-workflow | workflow | 12 m ago | 4.81 s | — | done | ||
| — | manual | 24 m ago | 3 ms | — | failed | ||
| digest-cron | cron | 1 h ago | 0.76 s | 1,902 | done | ||
| support-bot | webhook | 1 h 12 m | 612 ms | — | failed | ||
| triage-workflow | event | 1 h 47 m | 2.40 s | 5,204 | interrupted | ||
| support-bot | job | 2 h 30 m | 0.94 s | 2,773 | done | ||
| — | manual | 4 h ago | 6 ms | — | failed |
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 SDKLocal development
Run and hot-reload your agent against a control plane identical to production — zero infra to stand up.
Open CLI & emulatorStudio
A visual console for every run: trace waterfalls, logs, data explorers — same UI local and cloud.
Open StudioHuman-in-the-Loop
Pause a run for a human decision in one call; approvals land in an inbox and resume the run.
Open HITLProvisioning
Declare what resources and events your agent needs; the platform provisions them and injects the credentials.
Open provisioningManaged runtime
Every install runs isolated in its own micro-VM with scale-to-zero. You only ship a Dockerfile.
Open runtimeEval
Declare a quality suite and run it locally today against real provisioned resources; publish gating lands in V1.
Open evalPublish & monetize
Package once, install many. Deploy today; the public catalog with payouts comes next.
Open publish Build flow
Four commands, start to ship.
step1/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
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 /schema. 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.
$npx @stackbone/cli login
✓ Logged in as hello@stackbone.ai
$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
$