---
title: "Roadmap"
description: "What is not built yet, and when it is expected."
canonical: https://past.dev/docs/memory-api/roadmap
last-updated: 2026-08-26
---
# Roadmap

> What is not built yet, and when it is expected.

Product: past.dev Memory API. Source: https://past.dev/docs/memory-api/roadmap

Dated items are committed and will ship through the API. The rest have no date yet.

| What | Status today |
| --- | --- |
| **Per-end-user privacy** | **Live** `POST /api/v1/ingest` takes an `audience` list (integer ids) and retrieval is filtered by audience inside the engine. Audiences themselves are configured with past.dev during early access; self-serve audience management arrives with the configuration endpoint below. |
| **Published rate limits and SLA** | **End of August 2026** No documented limits and no uptime commitment during early access. Tell us the expected volume and we will say whether it is workable. |
| **Self-serve keys** | **End of August 2026** Keys are issued by hand during early access. Programmatic issuance, scoping and rotation are not built. |
| **Self-serve provisioning** | **End of August 2026** Projects are created by us on request. There is no API to create one. This ships together with self-serve keys. |
| **Agent mode on /answer** | **No date yet** A retrieval loop that can refine its own searches before committing to an answer. `mode: "agent"` is refused today rather than silently ignored. |
| **Direct graph endpoints** | **No date yet** Search and CRUD on entities, their memories, their relationships and traversal by hops. The API reference lists the intended routes. Until they ship, `/api/v1/recall` returns the same evidence with its sources. |
| **Configuration endpoint** | **No date yet** Custom ontology, audiences and ingestion defaults through the API. We apply the same configuration by hand during early access, so ask and it gets done. |
| **Versioned routes** | **Live** Every route lives under `/api/v1`. A breaking change gets a new version prefix; design partners are warned first. |
| **Self-hosting** | **Live** A Docker Compose bundle runs the API, console, Postgres, Redis and optional Temporal on your infrastructure, from pinned public release images, with local accounts and no third-party services. See Self-hosting above. |

> **If a gap blocks an integration**
>
> If one of these is a condition of an integration rather than a nice-to-have, tell us. It affects what we build next.