Pricing
Self-hosting is free. The hosted service is cheap on purpose: a free tier with no card, then $1 a month for each step you add.
Self-hosted
$0
Run the open-source CLI and MCP server against your own S3-compatible bucket, with your own credentials.
Hosted
$0 a month to start
- 1 space
- 100 MB of storage
- 250,000 requests a month
- No card needed
Hosted, more
Add as many of each as you need, at $1 a month each.
| Add | Price |
|---|---|
| 1 more space | $1 a month |
| 100 MB more storage | $1 a month |
| 250,000 more requests a month | $1 a month |
| 1 opt-in featureThe first, a browser editor, is coming soon. | $1 a month |
How billing works
- Monthly only.
- You choose fixed caps; nothing is metered. You are never billed more than you picked.
- Your account page marks a limit at 80% and shows a banner once it is reached.
- When storage is full, new commits are refused and pulls keep working.
- Over the request limit, commits are refused and reads continue, slowly, until the month resets.
- A token reaches one space only.
- Text files only.
Connect the CLI or MCP server
Sign in, create a space and a token on your account page, then point the CLI or MCP server at it: set SLIVINGDOC_TOKEN to the token, the bucket to your space (SLIVINGDOC_BUCKET, or --bucket), and the endpoint to https://api.slivingdoc.dev (--endpoint).
Questions
What counts as a request?
Every call your tools make to the hosted API counts; one pull or commit makes several.
What happens at the limit?
Your account page shows when you are close. At the storage limit, new commits are refused and pulls keep working. At the request limit, commits are refused and reads continue, slowly, until the month resets. You are never billed for going over.
Can I lower my caps?
Yes, down to what you use.
Can I self-host instead?
Yes, and it is free: the same CLI and MCP server, against your own bucket. See Set up a bucket and the Quickstart.