Pricing and limits

Four plans for the hosted service — Free, Starter, Team and Business — and Limma inside your own network (On-prem). You sign up and pay through Stripe, monthly, in US dollars; Stripe's checkout page shows the price again before you pay. Free costs nothing and asks for no card.

	Free	Starter	Team	Business
Price per month	$0	$49	$199	$799
Documents held	50	2,000	20,000	100,000
Pages per month	250	2,500	12,000	60,000
API calls per month	10,000	100,000	1,000,000	5,000,000
Workspaces	1	3	25	100
Largest file	10 MB	50 MB	100 MB	100 MB
	Start free	Subscribe	Subscribe	Subscribe

The Free plan

Free is a plan of its own, for as long as you use it — not a trial. Signing up is the same checkout as any plan, at $0: Stripe asks for no card and charges nothing, and the welcome page shows your key once. Its limits are in the table: 50 documents, 250 pages and 10,000 API calls a month, one workspace, files up to 10 MB.

• To move to a paid plan, open Stripe's customer portal (POST /v1/billing/portal with your admin key answers with its link), add a card first, then switch plan. The move is in place: the same organization, its key, its workspace and its documents — never a second sign-up.
• A paid plan's limits apply from its first successful payment. Until the new plan is paid for — a switch made with no card, a payment that has not gone through — your organization keeps the Free plan's limits; once the payment succeeds, the plan's own apply at once. GET /v1/public/usage says which are in force.
• Limma may change or end the Free plan on notice (Terms of Service).

Starter, Team and Business have no trial, and take a card at checkout: their limits apply from the moment the checkout's payment succeeds.

What each limit counts

• Documents held — every document in your workspaces now: a file, or a text your agent sent. A document you delete stops counting.
• Pages per month — what Limma read or loaded for you this month, counted when it happens:
  • a document read by the model that has pages (a PDF, a PowerPoint deck, an image) counts its pages — a deck its slides;
  • a document read by the model without pages (Word, text, Markdown, HTML, e-mail, RTF, XML, JSON) counts one page for every 3,000 characters of its text;
  • records loaded without a model (an export or a table connected through a mapping: its rows and fields) and texts kept unread (read: "defer") count one page for every 30,000 characters, added up over the whole load — 40,000 short bios kept unread count their characters, about 1,300 pages, not 40,000;
  • when you connect a source again, only the records it added or changed count (matched by the mapping's key; a changed record counts all its characters), and only the texts that are new or changed. Unchanged and deleted records count nothing. A table connected with no key columns cannot be compared, so each load of it counts all of it;
  • a document read by the model counts at least one page, and so does a load that added or changed anything; a load that changed nothing counts none. A document read again (a retry, a re-extraction) is counted again; limma sync sends only what changed, so an unchanged file never counts again.
• API calls per month — every request to the API that reads or loads data; each tool call your agent makes is one. Reading your usage, deleting, and the MCP connection's own messages are not counted.
• Workspaces — the workspaces your organization holds. You never need more than the default one; more keep documents apart.
• Largest file — the largest single file you can load.

At a limit

A call that would go over a limit is refused with 402 quota_exceeded. The reply names the limit, your count, and how to move to a larger plan (the customer portal); over pages it says how pages are counted. Nothing is dropped without being said, and when only a loading limit is reached, every read keeps working.

GET /v1/public/usage tells your key what your organization holds and may do: its plan and the limits in force with every count — your pages split into read by the model and loaded without one — and each workspace's documents (by status), the reasons any failed to be read, and its facts and records (your usage).

Changing or cancelling

Upgrade, downgrade, change your card or cancel in Stripe's customer portal: POST /v1/billing/portal with your admin key answers with its link. Every change is in place, on the same organization; from Free, add a card before switching to a paid plan. A cancelled subscription runs to the end of the period you paid for. What happens to your data after it ends is in the Terms of Service.

On-prem: inside your own network

Limma also runs inside your own network, with your own model, under a licence instead of these plans: install Limma inside your network, or write to contact@limma.ai.