Limits

What Marfa doesn't do, and the limits an instance holds to, in one place.

What Marfa doesn't do

  • One person. An instance has one owner, and holds one person's things. There are no accounts for other people, nothing shared and no teams. Every app, agent and key acts for you.
  • No hosted service. Marfa doesn't run instances for anyone. You run your own, on your own computer or on a host you choose, such as Railway, as the Quickstart shows.
  • No pages of your data. In a browser, your instance shows only a page that says it's running and the pages for setting it up, signing in, approving an app or the CLI, recovering your password and managing your passkeys. It never shows your files, notes or other items: you see them through an app, an agent, the CLI or a synced folder.
  • No connectors inside the server. The server never reads another service itself. A connector is a program you build from source and run, with a key of its own.
  • No Intel Macs and no Windows. Marfa runs on Macs with Apple silicon and on Linux, x86_64 or arm64.
  • One Google account for each instance. Google connectors keep the account they first ran with, as Create a Google Cloud project explains.

Limits on what you store

LimitValue
A note's body, or another type's main text1,000,000 characters
Any other text field100,000 characters, unless its type sets its own length
Tags on one item100
One tag128 characters
One write1 MiB, or 16 MiB for bulk operations
A fileNo fixed size. Marfa refuses a file that would leave less than 128 MiB free on its disk

A type can set a shorter or longer length for its own fields: its page in the Catalog shows it.

Limits on how you ask

LimitValue
Requests from one app or key4,000 a minute, and 200 a minute to the key operations
Items moved to the bin in one command20, as Move items to the bin shows
Items in one page of a list500
A search500 characters, and at most 16 words outside quotes
A filter2,048 characters, and at most 10 conditions
Types or tags named in one filter10 types, 100 tags

When an app or a key goes over its requests, your instance asks it to wait. A synced folder waits and carries on by itself, as Fix a folder shows.

How long things are kept

WhatKept for
An item in the bin60 days, then deleted for good
Earlier versions of an itemEvery version for 30 days, one a day to 90 days, and one a week to a year, up to 500 for each item
The audit log90 days

Change a limit

Most of these are settings you can change, such as keeping the bin for a year:

marfa config set trash_retention_days 365

marfa config settings lists every setting with its value, its default and the values it takes. Change an instance's settings explains them. The limits on text, tags, searches and filters are fixed.

On this page