About

About Ablo

We make it possible for agents and people to work on the same data. Ablo coordinates their changes and keeps track of who did what.

The company behind the engine

Ablo Inc., a Delaware corporation, is the company that publishes Ablo. It operates from Stockholm through our Swedish subsidiary, and its place of business, and the address for notice under the terms, is Eriksbergsgatan 10, 114 56 Stockholm, Sweden.

What we build

Ablo connects to your existing Postgres database. Agents and people can work in parallel, reserve a record when they need to take turns, and see what changed. An agent can check that the data behind its decision is still current before saving an update. Ablo records every accepted change and who made it.

The engine ships as three things a developer touches directly: a typed TypeScript SDK, a command line for setting up and evolving a schema, and hosted Model Context Protocol servers that put the same surface in front of a coding assistant. A Python client and a plain REST API cover runtimes the SDK does not reach.

Where your data lives

Your rows stay in your database. Ablo reads them by tailing the logical replication stream your Postgres already produces, and writes land back in that same database through a role you scope. What Ablo hosts is the transaction log and the coordination state, never your application tables. The shape is closer to a payments processor than to a backend as a service: the system of record does not move.

The client libraries are published under the Apache License 2.0 and are readable before you commit to anything. The coordination service is managed, and the data it coordinates remains yours throughout.

Who we are

We are a small engineering team. The people who answer support are the people who write the engine, and a question about behaviour usually comes back with the reasoning rather than a ticket number. If you are evaluating Ablo for production, write to us and ask the hard version of the question.