Account
Plans and limits
What the free plan includes, what counts against it, and how sleeping databases wake.
SoonThese pages describe Chronos Cloud, which opens from the waitlist. Running Chronos yourself? Self-host docs
The free plan
Every feature, on a database sized for building and trying agents on real data. No card.
| Limit | Free |
|---|---|
| Projects (each with one database) | 2 |
| Storage per database | 512 MB |
| Worlds open at once | 100 |
| History to go back through | 1 hour |
| Backups kept | 7 days |
| Connections | 50 |
| Compute | ¼ vCPU, 512 MB memory |
| Awake time a month | 100 hours |
| Data out a month | 5 GB |
| Sleeps when idle | after 5 minutes |
Included: worlds, merge policies and checks, reviews, history and undo, vectors, Auth for your app, and teams.
What counts
- Storage: the database’s files:
main, what every open world changed, and the history kept for the window. A world costs only what it changed. - Worlds: open worlds,
mainnot included. A merged or discarded world stops counting. - Data out: bytes sent to clients over Postgres and HTTP. Data in is free.
- Awake time: time the database is running, from the first connection after it sleeps to when it sleeps again.
Reaching a limit
| Limit | What happens |
|---|---|
| projects | a new project is refused (409 plan_limit): delete one you no longer need |
| storage | writes are refused (53100) until there’s room: reads go on. Drop worlds you’re done with, delete data, or wait for history to age out |
| worlds | a new fork is refused (53400): merge or discard worlds |
| connections | a new connection beyond it is refused: use a pool |
| awake time, data out | shown against the plan on the Usage page and in chronos cloud usage |
Sleeping and waking
A database with no connections for 5 minutes sleeps; the next connection, MCP call or dashboard visit wakes it, and that one takes a moment longer. A sleeping database keeps all its data, worlds and history, and doesn’t count toward awake time.
Seeing your usage
The dashboard’s Usage page, chronos cloud usage in a project folder, or the MCP tool usage show storage, open worlds, data out and awake time this month against the plan.
Paid plans
Paid plans are coming, for databases real users rely on: never sleeping, history you can go back through for days, more storage, worlds and connections, longer backups. Free stays free when they come.