---
title: Access
description: How to get an organization and an API key while access to Docsary is limited, that the product is free while it grows, and the exact ceilings your organization runs under.
order: 8
---

# Access

Access to Docsary is currently limited. Organizations and API keys are provisioned by us rather than through self-service signup. If you would like to evaluate Docsary for your product documentation, get in touch at [hello@robota.us](mailto:hello@robota.us) and describe what you are documenting and roughly how large it is.

Once your organization exists, everything else is yours to drive: your key creates sites, pushes content, attaches and verifies domains, and manages versions, with no further involvement from us. Ask for one key per consumer — a write-capable key for CI, a read-only one for anything that only inspects. See the [Quickstart](/quickstart).

## Docsary is free

The whole product is free while it grows. There is no paid tier to be upgraded to, no feature held behind one, and nothing watermarked or degraded to make a point. Sites, versions, pages, search, the `.md` and `llms.txt` surfaces, offline mode, redirects, the automatic `docsary.com` address every site is given at creation, and **custom domains on hostnames you own** — all of it, on every organization.

If that changes, it will change for new organizations first and with notice, not by quietly switching something off underneath you.

## The ceilings

Free does not mean unbounded. Every organization runs under a set of limits, and it is worth being plain about what they are for: they exist so that one runaway script, or one organization behaving badly, cannot exhaust the capacity everyone else is sharing. They are **abuse ceilings, not price tiers** — there is nothing on the other side of them to buy.

| Limit | Ceiling | Scope |
| --- | --- | --- |
| Sites | 5 | per organization |
| Versions | 20 | per site |
| Pages | 2,000 | per version |
| Redirects | 500 | per site |
| Custom domains | 3 | per organization |
| Asset storage | 1 GB | per organization |

The `docsary.com` address every site is given at creation is **not** one of the custom domains — it arrives with the site and counts against nothing.

Two more ceilings are about rate rather than count:

| Limit | Ceiling | Scope |
| --- | --- | --- |
| Write requests | 240 per minute | per organization |
| Reports filed | 20 per hour | per organization |

Reads are not rate limited. A full push of a two-thousand-page manual runs at roughly six files per request, so it fits inside the write ceiling without pausing; a script in a loop does not. See [Conventions](/api/conventions#rate-limits).

## When you hit one

A call refused for being over a limit says which limit and what the number is, so you never have to guess what you ran into:

```json
{
  "error": "quota exceeded: sites limit is 5 on plan 'free'",
  "quota": "sites",
  "limit": 5,
  "plan": "free"
}
```

Read `limit` from the response rather than from this page: any of these can be lifted for your organization individually, and when it has been, the response is what tells you so. `GET /v1/whoami` reports which plan you are on.

**If a ceiling is in your way, ask.** Lifting one for a real project is a change we make on our side, it takes one request, and it needs nothing from you beyond saying what you are running into.

## Reporting problems

Anything that looks like a bug, and anything you wish Docsary did, goes through the API rather than through us by hand: `POST /v1/reports` files it against your organization, and `GET /v1/reports` shows you where your reports stand. Any key can file, including a read-only one. See [Support](/support).