skeino¶
Why skeino¶
-
Studio-compatible
Implements the v1 HTTP surface — threads, runs, streaming/SSE, assistants, health/info — that LangGraph SDK clients and Studio already speak.
-
Modular by design
api,ops,persistence,streaming, andserializationare separate concerns with explicit dependencies — easy to read, easy to extend. -
Pluggable persistence
Checkpointers register through a small decorator-based registry. Postgres and in-memory ship in the box; add Redis or Mongo without touching core.
-
Typed & documented
Strict mypy and enforced docstrings across the package — so the Python API reference comes straight from source.
Two ways in¶
Then serve it like any ASGI app:
Your graph is now reachable over the LangGraph HTTP API, with interactive
OpenAPI docs at /docs — and an always-current API explorer
right here in these docs.
Explore the docs¶
-
Install skeino and stand up a server — programmatically or from
langgraph.json. -
The thread/run/checkpoint model, streaming semantics, and persistence.
-
Every v1 HTTP endpoint, the interactive explorer, and the generated Python API.
-
Embed in an existing app, configure Postgres, write a checkpointer, deploy.
Status¶
skeino is stable (1.x, semver). The supported public surface is
create_app, from_langgraph_json,
SkeinoSettings, and GraphRegistry.
Sub-modules are importable for advanced use but aren't part of the stability
contract. See the changelog for release history.
Some langgraph dev features are intentionally out of scope for v1: no
bundled web UI, no cron/webhook scheduling, no built-in auth, and no /store/*
endpoints. skeino focuses on the core threads/runs/streaming/assistants surface
that SDK clients depend on.