Small data your apps read often
Not everything belongs in a database table. Feature flags, user sessions, rate-limit counters, settings and the answer to a slow API call are easier as a key and a value.
KV storage gives each workspace namespaces of keys, reachable from any app, script or function over HTTPS with a token. There is nothing to run or connect.
Three steps
- 1
Create a namespace in the dashboard.
- 2
Create a KV token and add it to your project as a secret variable.
- 3
PUT a value to /values/{key}, GET it back, list keys by prefix, or send many writes at once to /bulk.
Search keys by prefix, read values as text, JSON or hex, edit small values and set when they expire, without writing code.
Limits by plan
| Plan | Namespaces | Reads a day | Writes a day |
|---|---|---|---|
| Free | 1 | 100,000 | 1,000 |
| Launch | 10 | 1 million | 1 million |
| Pro | 50 | 10 million | 10 million |
| Scale | 200 | 100 million | 100 million |
Safe by default
- Tokens are shown once. Rimbra keeps only a hash and the last few characters.
- The API answers only on api.rimbra.app, never on your sites’ own addresses.
- Bulk writes land all at once or not at all.
Questions
Is it eventually consistent?
No. KV runs in the same region as your apps, and a read right after a write sees the new value.
What happens when a key expires?
It reads as missing straight away and is cleared from storage within minutes.
Does it count toward my storage?
Yes. Keys, values and metadata count toward the one storage allowance on your plan, together with project files and databases.