Stigmer
The open-source backend for the agents in your product. It runs behind
your app, the way your database does. Each of your customers gets an agent with
its own computer, one that works on a job for hours, asks before acting and
keeps their data apart from every other customer's.
Run it yourself on a laptop, one server or Kubernetes, or use Stigmer Cloud.
Agents run on your own model provider key.

Quick start
An accounting product's customer uploads a ledger, and an agent hands back a
variance report as a file:
brew install stigmer/tap/stigmer
export ANTHROPIC_API_KEY=<your Anthropic API key>
stigmer up
curl -fsSLO https://raw.githubusercontent.com/stigmer/stigmer/main/examples/variance-report/variance-reporter.yaml
curl -fsSLO https://raw.githubusercontent.com/stigmer/stigmer/main/examples/variance-report/ledger.csv
stigmer apply -f variance-reporter.yaml
stigmer run variance-reporter --attach ledger.csv --download ./out --until turn -m "Review this quarter's ledger."
cat out/variance-report.md
The customer's ledger went in, and their report came back as a file in ./out,
written by the agent. Your first agent job
walks through each step, and
Do the same job from your app
starts it from your own code.
Other install methods
# Shell script (macOS/Linux) — no prerequisites, bundles its own Node.js runtime
curl -fsSL https://stigmer.ai/install.sh | sh
# npm (requires Node.js >= 22.13)
npm install -g @stigmer/cli
# From source
git clone https://github.com/stigmer/stigmer.git
cd stigmer && make setup && npm install && make local
What is Stigmer?
Your app calls Stigmer, and Stigmer runs the agent on your model provider. Each
of your customers gets an agent that takes what they hand it, works through it
on a computer of its own, and hands back the result. You build the feature, not
the machinery.
Bring the plugins you already have: install the Claude Code, Cursor or Codex
plugins your team uses, and a plugin carries skills, hooks, subagents and the
MCP servers that connect agents to your
systems. Agents discover the tools and Stigmer handles execution sandboxing.
Core concepts
Stigmer also ships its own MCP server, which exposes Stigmer's resources to
AI-powered IDEs:
stigmer mcp-server
See mcp-server/README.md for IDE configuration (Cursor, Claude Desktop, VS Code, Windsurf).
SDKs
| SDK |
Install |
Reference |
| Go |
go get go.stigmer.ai/sdk |
Reference |
| TypeScript |
npm install @stigmer/client |
Reference |
| Python |
pip install stigmer-sdk |
Reference |
| Java |
Maven: ai.stigmer:stigmer-sdk |
Reference |
| React |
npm install @stigmer/react-sdk |
Reference |
| Ink |
npm install @stigmer/ink-ui |
Reference |
The Go, TypeScript, Python, and Java SDKs provide typed API clients for every Stigmer resource. The React SDK renders agent UIs — session composers, message threads, and approval views. The Ink SDK brings the same components to the terminal.
Put the agent in your app
The React SDK ships the same chat surface the Stigmer Console uses, as one
drop-in component. A provider, a token your backend mints, and AgentChat put
the variance reporter in front of your users:
import { Stigmer, createTokenCache } from "@stigmer/client";
import { AgentChat, StigmerProvider } from "@stigmer/react-sdk/chat";
import "@stigmer/react-sdk/styles.css";
const org = import.meta.env.VITE_STIGMER_ORG;
const tokens = createTokenCache(async () => {
const res = await fetch("/api/stigmer-token");
return res.json();
});
// …
export default function App() {
return (
<StigmerProvider client={stigmer}>
<main style={{ height: "100vh" }}>
<AgentChat agent={`${org}/variance-reporter`} />
</main>
</StigmerProvider>
);
}
variant="panel" docks the same chat beside your page, and variant="popup"
puts it behind a button in the corner.
Every component is themeable with design tokens, and the hooks underneath are exported for fully custom UIs. Put the agent in your app is the complete walkthrough, with the backend route that hands the page its token.
Open source, Enterprise and Cloud
|
Stigmer open source |
Stigmer Enterprise |
Stigmer Cloud |
| Start with |
stigmer up, Docker Compose or the Helm chart |
The Helm chart with a license key Secret |
stigmer config backend set cloud |
| Storage |
SQLite (~/.stigmer/stigmer.db) or your Postgres |
Your Postgres |
Managed |
| Users |
One organization, with sign-in, roles and service accounts |
Many organizations, teams, invitations and federation |
The same, hosted |
| LLM |
Your key, held by the runner (Anthropic) |
Your key, held by the runner (Anthropic) |
Your organization's keys (Anthropic, OpenAI, compatible endpoints) |
| Best for |
Development, personal projects, one team, full data ownership |
Companies that must keep many teams on their own infrastructure |
Teams that want a managed platform |
Stigmer runs no model of its own: every edition runs your agents on your own provider key. Stigmer Enterprise is licensed annually; compare the editions or see pricing.
Resource definitions are portable across all three. The CLI talks to the same gRPC service interfaces regardless of backend.
Brand assets
The brand folder contains the current logo and ready-to-upload
profile images. Use brand/avatar.png for GitHub and other profile uploads.
Documentation
- Getting Started — Give an agent a job and get its report back, on your machine or on Stigmer Cloud
- Try it in one container —
docker run ghcr.io/stigmer/stigmer for evaluation (not for production)
- Self-hosting — Run the full stack on your own machine with Docker Compose
- Kubernetes — The same stack on a cluster with the Helm chart (
oci://ghcr.io/stigmer/charts/stigmer)
- CLI Reference — Commands, flags, and examples
- SDK Reference — Go, TypeScript, Python, Java, React, and Ink
- What is Stigmer? — What each customer's agent has, and how one job runs end to end
- Examples — The variance report job, as files to run
Development
Prerequisites
- Node.js 22+ (22.13 or newer; the server needs
node:sqlite with FTS5)
- Go 1.25+ (for the Go SDK, codegen tools, and integration harnesses)
- Git, Make
Building from Source
git clone https://github.com/stigmer/stigmer.git
cd stigmer
make setup # Install Go and Python dependencies
npm install # Install Node.js dependencies
make local # Build the local server and runner (the CLI runs from @stigmer/cli)
make test # Run tests
Contributing
We welcome contributions. See CONTRIBUTING.md for guidelines.
License
Stigmer is open source under the Apache License 2.0, with one
exception: the ee/ directory, Stigmer Enterprise, is under the
Stigmer Enterprise License. The Enterprise code is public and
readable; running it in production needs a license key. Without a key, the
Enterprise server behaves exactly as the open-source server and runs no
Enterprise code. Everything outside ee/ stays Apache 2.0 and never depends
on it.
The licenses grant rights in the code, not in the Stigmer names or logo; see
TRADEMARKS.md.