GraphorinStop demoing. Ship assistants that earn their keep.

Your competitors are still tuning vanity metrics. You are here to sell outcomes. Graphorin stacks tiered memory, checkpointed workflows, typed tools, MCP, OpenTelemetry for every model and tool call, and secret handling that does not flinch. Follow the guides, paste the examples, embed in Node now, turn on the standalone server when load spikes, and push nothing across the wire unless you choose.

Get started

What is Graphorin?

View on GitHub

Private by default

No hidden analytics or version checks. Your process only talks to the network when your code does. CI blocks accidental "phone home" changes so the default stays honest.

Read the promise

Six memory layers

Working, session, episodic, semantic, procedural, and shared tiers—each tuned for how fast it changes, how it is searched, and who may read or write it—not a single lump of "context."

Memory system

Workflows that keep going

Checkpointed steps, pause and resume across restarts, human approvals, and parallelism when you need it. A run can stop on Friday and continue on another machine on Monday.

Workflow engine

One API, many models

Switch between cloud SDKs, local Ollama, OpenAI-compatible servers, llama.cpp, or GGUF without rewriting your agent—the same provider surface everywhere.

Providers

Observability built in

OpenTelemetry-friendly traces for models, tools, memory, and workflows, with redaction so sensitive fields are less likely to leak to your exporter by mistake.

Observability

Tools, Skills, and MCP

Typed tools, standard Agent Skills packs, and a built-in MCP client for stdio and Streamable HTTP—so your assistant can reach the systems you already rely on.

External surface

Embed or run a server

Use Graphorin inside your Node.js app today, then add the standalone server when you want REST, WebSocket, SSE, triggers, and replay without a rewrite.

Standalone server

Safer secrets and audit trail

`SecretValue` and `SecretRef` keep credentials out of logs, keychain-friendly resolution, optional encryption at rest, OAuth with PKCE, and a tamper-evident audit chain.

Secrets

Strict TypeScript end to end

Public APIs avoid `any`; schemas line up across tools, memory, and outputs; streaming events stay typed so large teams catch mistakes early.

API reference

v0.1.0MIT