LangGraph Checkpoint Aerospike
Store LangGraph checkpoints in Aerospike using the provided AerospikeSaver.
Installation
pip install -U langgraph-checkpoint-aerospike
Usage
- Bring up Aerospike locally using prebuilt Aerospike Docker Image:
docker run -d --name aerospike -p 3000-3002:3000-3002 container.aerospike.com/aerospike/aerospike-server
-
Point the saver at your cluster (Default):
AEROSPIKE_HOST=127.0.0.1AEROSPIKE_PORT=3000AEROSPIKE_NAMESPACE=test
-
Build a LangGraph graph and compile it with the saver as the checkpointer. Passing the same
thread_idon a later run resumes from the persisted state:from typing import Annotated, TypedDict import aerospike from langgraph.graph import START, END, StateGraph from langgraph.graph.message import add_messages from langchain_core.messages import HumanMessage from langgraph.checkpoint.aerospike import AerospikeSaver # 1. Connect to Aerospike and build the checkpointer. client = aerospike.client({"hosts": [("127.0.0.1", 3000)]}).connect() checkpointer = AerospikeSaver(client=client, namespace="test") # 2. Define a minimal LangGraph graph. class State(TypedDict): messages: Annotated[list, add_messages] def chatbot(state: State) -> State: last = state["messages"][-1].content return {"messages": [("assistant", f"You said: {last}")]} builder = StateGraph(State) builder.add_node("chatbot", chatbot) builder.add_edge(START, "chatbot") builder.add_edge("chatbot", END) # 3. Compile with the Aerospike checkpointer. graph = builder.compile(checkpointer=checkpointer) # 4. Each thread_id is a separate, persisted conversation. config = {"configurable": {"thread_id": "demo"}} graph.invoke({"messages": [HumanMessage("hello")]}, config) # 5. A later call with the same thread_id resumes from the saved state, # even in a brand-new process — the history lives in Aerospike. result = graph.invoke({"messages": [HumanMessage("are you still there?")]}, config) for message in result["messages"]: message.pretty_print()
You can also inspect persisted checkpoints directly through the saver, e.g.
checkpointer.get_tuple(config) for the latest checkpoint or
checkpointer.list(config) to walk a thread's history.
Metadata
Release files for langgraph-checkpoint-aerospike 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| langgraph_checkpoint_aerospike-0.3.0.tar.gz | 21.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| langgraph_checkpoint_aerospike-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 33.6 kB
Release files / langgraph_checkpoint_aerospike-0.3.0.tar.gz
| Download URL | langgraph_checkpoint_aerospike-0.3.0.tar.gz |
|---|---|
| Size | 21.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d3308f398329793b2634fea7a4c9a16404a21ba3d0b8ba3a162e4dd3bacf871c
|
|
BLAKE2b-256 checksum How to use checksums |
522c014e61d563f5badd5dcc5f13d6f0c37a859980ed3d42cd9a03a0b4b12117
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 8, 2026.
Transparency logRelease files / langgraph_checkpoint_aerospike-0.3.0-py3-none-any.whl
| Download URL | langgraph_checkpoint_aerospike-0.3.0-py3-none-any.whl |
|---|---|
| Size | 11.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
69e45b7498e1d8ed083477b193d04640047376695e914174eb42378147ef06f8
|
|
BLAKE2b-256 checksum How to use checksums |
127d162e110dad18385fe11842496c1b2e2835bfc8fbf8e23804b9f9313a973d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 8, 2026.
Transparency log