Login sessions
Session data read on every request, held in memory rather than fetched from your database each time. This is the job most stacks reach for first, and the one that pays back immediately.
Databases
Managed Redis. Hosted in India.
A Redis-compatible key value store that keeps small pieces of data in memory, so the reads your app makes on every request never wait on a disk.
Free size included · Paid sizes from ₹425/mo
- Redis-compatible
- Free size to start
- Nightly snapshots
- 2,000+Developers
- 24,100+Deploys
- MumbaiWhere your app runs
What every key value store comes with
- Its own container, its own memory and its own password
- Redis-compatible, so your existing client library works
- Reachable from your services by name
- A TLS endpoint when you turn on external access
- Nightly snapshots, so a restart does not start from empty
- Password rotation from your dashboard
- One bill, in rupees, with a GST invoice
- Runs in Mumbai (IN)
What people keep in a key value store
Anything that has to be read often, and that you could rebuild if you lost it.
Cached query results
The expensive report, the API response you paid for, the page fragment that takes a second to build. Compute it once, keep it for as long as it stays true, and serve it from memory after that.
Rate limits and counters
Counters that move constantly and do not belong in a database - requests per minute, attempts per user, how many of something is left. Atomic increments are what the engine is good at.
Job queues and locks
A simple queue your background worker reads from, and locks that stop two processes doing the same work at once. Pair it with a background worker and the two are one platform, one region, one bill.
Fast memory beside your database, not instead of it
An in-memory store is a poor place for anything you cannot afford to lose. Voroa writes your data to disk and takes a nightly snapshot, so a restart does not start from empty - but between writes, a crash can lose the most recent moments.
That is the nature of the engine rather than a gap in ours, and it decides how to use it: keep what you can rebuild here, and keep what you cannot in PostgreSQL. Most applications run both, which is why a Voroa workspace can hold both beside the service that uses them.
One platform
One URL, and your existing client connects
Your store is created beside the service that uses it and hands you one connection URL to paste. Any Redis client library understands it, so nothing in your code changes beyond the environment variable.
View documentationBilling
One rupee bill, itemised, with GST
Your key value stores and every service and database beside them land on a single monthly invoice, paid over UPI-Autopay or an Indian card. Each line names what it is for, and the tax is split out the way your accountant needs it for input tax credit.
View documentationKey Value stores
per storeStart free, move up a size when the service needs it. Every size is billed per service, per month.
- Redis-compatible
- Reachable from your services
- Cache pages, results and sessions
| Plan | CPU / RAM / Storage | Price | Action |
|---|---|---|---|
Cache Nanokv_nano |
0.05 CPU · 128 MB RAM | ₹0/month+18% GST | Get started |
Cache Starterkv_starter |
0.1 CPU · 256 MB RAM | ₹425/month+18% GST | Get started |
Cache Starter Pluskv_starter_plus |
0.2 CPU · 512 MB RAM | ₹749/month+18% GST | Get started |
Cache Standardkv_standard |
0.25 CPU · 1 GB RAM | ₹1,349/month+18% GST | Get started |
Cache Standard Pluskv_standard_plus |
0.4 CPU · 2 GB RAM | ₹2,499/month+18% GST | Get started |
Cache Prokv_pro |
0.5 CPU · 5 GB RAM | ₹5,699/month+18% GST | Get started |
Cache Pro Pluskv_pro_plus |
1 CPU · 10 GB RAM | ₹10,499/month+18% GST | Get started |
Your bill is one workspace plan plus a compute size for each service you run; the pricing page lists the workspace plans. All prices in INR and exclude 18% GST; a GST tax invoice is issued on every payment. No foreign currency payments, no forex markup.
How it works
From signup to a running store
- 01
Create your Voroa account. Email and a password, or sign in with GitHub.
- 02
Open Databases, choose Key Value, and pick a size. The free size costs nothing and needs no card.
- 03
Copy the connection URL shown at create time - it is shown once.
- 04
Paste it into your service's environment variables.
- 05
Point your existing Redis client at it. No code change beyond the URL.
- 06
Move up a size when your working set outgrows the one you picked.
Is this actually Redis?
It is a Redis-compatible in-memory store, so the client library you already use connects to it without a code change. Point your client at the connection URL and carry on.
How much memory do I get?
From 128 MB on the free size up to 10 GB. Pick the one that holds your working set; the sizes and what each one costs are listed above.
Can I reach it from outside Voroa?
Yes. Turn on external access and you get a TLS endpoint on its own port, protected by your instance password. A per-source IP allow list is not available for key value stores yet, so if you need source restrictions today, leave external access off and connect through your Voroa services.
What happens to my data if it restarts?
Voroa writes your data to disk and takes a nightly snapshot, so a restart does not start from empty. Between writes, a crash can still lose the most recent moments - so keep anything you cannot afford to lose in a database instead.
Can I change the size later?
Yes. Upgrading rebuilds the instance with the new memory, which is a brief restart. Your data, address and password stay as they are.
Where does it run, and how am I billed?
In Mumbai (IN). Billing is in rupees, and every charge comes with a GST invoice you can hand to your accountant.
Put your sessions and cache in memory
Create one on the free size, paste the URL into your service, and move up when your working set asks for it.
Free size, no card needed.