Introduction
Coordination infrastructure for agents, applications, services, and people working on shared state
Ablo is a framework-agnostic coordination layer for agents, applications, services, and people working on shared state. It provides claims, waiting, participant identity, stale-work rejection, confirmed writes, and live updates through one typed interface. Whether you are adding agents to an existing application or building a new multi-user system, Ablo lets you focus on your product instead of rebuilding coordination infrastructure.
Ablo works with your existing database, API, authorization, and business logic, while providing a common coordination model across runtimes and frameworks.
Features
Ablo provides a comprehensive set of coordination capabilities and a shared model that can be used across agents, services, applications, and human interfaces.
Claims and waiting
Let one participant perform contested work while others wait, skip, or fail according to an explicit policy.
Existing PostgreSQL
Keep the authoritative transaction, locks, constraints, and direct SQL paths your application already owns.
Groups and shared context
Structure which state reaches each participant, from membership and access to loading, updates and removal.
Participant identity
Give agents, people, and services distinct scoped credentials instead of treating every worker as the same caller.
Crash recovery
Expiring leases and heartbeats let later participants proceed when an owner disappears.
Stale-work rejection
Carry the rows behind a decision into its write and reject the result when those premises changed.
Atomic commits
Apply several Ablo writes together, with their captured premises, or apply none of them.
Confirmed writes
Know when a write reached the authoritative database and why a rejected write did not land.
Humans and agents
Coordinate stateless HTTP workers with live human interfaces over the same shared state.
Audit and visibility
Inspect ownership, contention, and committed changes with the responsible participant attached.
…and more.
Get started
- Installation — install Ablo, declare the shared models, and create a client.
- Basic usage — read, write, and coordinate one operation.
- Comparison — see how Ablo relates to PostgreSQL locks, Redis reservations, queues, workflow engines, and rolling your own.
- Choose the Ablo operation — route an existing use case to the smallest correct implementation.
AI resources
Ablo is designed to be implemented by agents as well as people. Use
llms.txt for the public documentation
index, or connect an assistant to the documentation MCP server. The
coordination MCP package also ships its agent-facing skill as
@abloatai/mcp/skill.md.
For a complete human-and-agent application, follow the account multiplayer reference.