Skip to content

Pricing

Metered from the first call. Billed from none of them, yet.

Usage is measured and quotas are enforced, because both have to be correct before money is involved. What does not exist is a payment flow — so these are shapes we can agree to, not products you can buy on this page.

Talk to usSee what it does

Plans

Three shapes, one boundary each

A workspace is the unit in every one of them: one per customer, one per environment, or one per project — whichever line you actually need to keep your data behind.

Evaluation

No charge

while you are working out whether this fits

One workspace, quotas sized for a prototype, and the whole API rather than a crippled subset of it.

  • One workspace
  • The full memory API and the CLI
  • Quotas sized for a prototype
  • Email support, answered when we can
Talk to us

Team

Most teams start here

By agreement

sized to what you actually send

Separate workspaces for staging and production, quotas agreed in advance, and your own model provider key if you would rather the calls went out under your account.

  • A workspace per environment or project
  • Quotas agreed up front, not discovered at a 429
  • Your own model provider key, stored encrypted
  • A named contact, answering within a working day
Talk to us

Isolated

By agreement

with a data processing agreement

A workspace for each of your own customers, and the paperwork that comes with holding data on someone else's behalf.

  • A workspace per end customer
  • Data processing agreement and subprocessor list
  • Erasure on request, one workspace at a time
  • A security review before you sign anything
Talk to us

Metering

What is actually counted

Four things, all of them countable, and none of them a surprise at the end of a month.

Conversations sent

Each accepted call counts once, at the point we accept it. The extraction that happens afterwards is not charged again.

Facts held

What is currently held in a workspace, not what has ever passed through it. Deleting memories brings the number down.

Retrievals served

Every search and every fetch by id, whether it came from the CLI, your own code, or an assistant acting for you.

Workspaces created

Each separate space. Suspending one stops its traffic without destroying anything, and a suspended workspace is not a deleted one.

At a quota
429

returned with the limit and the time it resets

Billed to date
Nothing

metering runs; billing is not built

Customers per space
One

separation is not a paid upgrade

Questions

The ones worth answering before you write

How do I upgrade?
You send an email and a person changes your quotas. There is no upgrade button, because there is nothing behind one — and a button that opened a support form dressed as a purchase would be worse than none.
What happens when I reach a quota?
The API returns 429, along with the limit and when it resets. Nothing already stored is affected and nothing is silently truncated; the call is refused and you can see why.
Is it free forever, then?
We are not going to say that. Nothing is billed today, and if that changes you would hear it from us with enough notice to decide what you want to do about it.
What if I want my data out?
Every memory is readable through the API and the CLI, and deleting a workspace removes everything in it — not hidden, not flagged, gone. A single call that exports everything at once is not built yet, which we would rather tell you here than later.
Do you train anything on what I store?
No. Your conversations are held to answer your own queries and nothing else. Extraction does call a model, and you can supply your own provider key so that call goes out under your account rather than ours.

Tell us what you are building

What you want to store, and roughly how much of it. That is usually enough for us to come back with a number and a quota rather than a discovery call.

Contact usRead the product page