What is shipped, what is next, and what we will not build.Documentation Index
Fetch the complete documentation index at: https://docs.abloatai.com/llms.txt
Use this file to discover all available pages before exploring further.
Shipped
- Resources, intents, commits — the core API.
- Capability tokens — Biscuit-signed, scoped, attenuable, hot-revocable.
- Audit log — hash-chained per principal, with
delegationChainRoot. - MCP transport — HTTP server at
/api/mcp. - TypeScript SDK —
@abloatai/ablo, with React bindings. - Dashboard — keys, audit, metrics, allowed origins.
In flight
- Real-time presence — see who else is viewing/editing a resource.
- Cross-instance fan-out via Redis — pub/sub deltas at scale.
- Hot capability revocation UI — in the dashboard, today via API only.
On deck
- Schema migrations — declarative resource schema changes.
- Field-level subscriptions — subscribe to one path, not the whole row.
- Bulk import/export — CSV/JSON round-trip with chain verification.
Maybe, if demand
- Python SDK — when a customer is shipping a Python-only product.
- Go SDK — same.
- Multi-region replication — when latency requirements force it.
We will not build
- A general-purpose Postgres wrapper — Ablo Sync is for state with concurrency semantics, not for storing every table.
- Server-side compute — no triggers, no stored procedures. Compute belongs in your application code.
- A document database UI — your data lives in Ablo Sync; the UI is your product, not ours.