We install it and tune it to the machine
Postgres or MySQL, configured for the RAM it actually has rather than left on the defaults, which assume a machine about a tenth of this size.
Cloud · Managed Databases
The database, run by someone.
PostgreSQL and MySQL on a machine sized for you, from ₹389 a month. We install it, tune it to the hardware, back it up off the machine every night, test the restore, and pick up the phone when something is wrong.
- 2
- Engines — Postgres, MySQL
- Nightly
- Backups, off the machine
- 16 GB
- Largest size listed
- ₹389
- A month, to start
What “managed” actually means.
Every host uses the word. Here is the list of things a person actually does, so you can hold us to them rather than to an adjective.
We back it up nightly, off the machine
A backup on the same server as the database is not a backup. Yours go to object storage on a different box, and we keep enough history to go back past the day you noticed.
We test the restore
The only backup that counts is one that has been restored. We do a real restore periodically and tell you the result, because an untested backup is a guess with a filename.
We watch it, and we tell you first
Disk filling, connections climbing, replication falling behind. You should hear about it from us before you hear about it from a customer.
We do the version upgrades
Out of hours, with a rollback ready, and we stay up while it happens. Major versions are agreed with you first rather than done to you.
We move you in
Migration from whatever you are on now — another host, a laptop, a shared plan that has run out of room. We do it out of hours and stay on the line until your application is talking to the new one.
Pick by how hard it gets worked.
A database is not sized by how much data you have — it is sized by how much of that data it has to hold in memory at once. These are the four machines we put databases on most often, in Mumbai, with the management included in the price.
2 GB
RAM · 1 vCPU · 20 GB SSD · Mumbai
₹389/mo
includes ₹100 management
A first production database. A site, a small shop, an internal tool — roughly up to a few hundred thousand rows before it wants more memory.
4 GB
RAM · 2 vCPU · 40 GB SSD · Mumbai
₹749/mo
includes ₹200 management
The size most small businesses settle on. Comfortable for a busy shop or a SaaS with real customers on it, and the usual starting point if you are migrating something that already exists.
8 GB
RAM · 2 vCPU · 80 GB SSD · Mumbai
₹1,349/mo
includes ₹300 management
When the working set stops fitting in memory and queries start touching disk. Also the first size worth considering if you are running reporting against the same database you serve from.
16 GB
RAM · 4 vCPU · 160 GB SSD · Mumbai
₹2,449/mo
includes ₹400 management
Heavy read traffic, large joins, or several databases sharing one machine. Past this we stop guessing and measure your actual workload first.
Prices are per month with no GST added, and each one is the machine plus the management described above — ₹100 a month at the smallest size, rising to ₹400 at the largest, because a bigger database is more data to back up, a longer restore and more that can go wrong. Bigger than 16 GB, or you need more than one machine, replication or a read replica? That is a conversation rather than a card — tell us the workload and we will come back with a real figure.
Four things we are not going to pretend about.
- This is our own service, not a product we resell. Most of what is on this site is infrastructure we buy and pass on with our own margin. A managed database is not: nobody sells us a “managed database” SKU, so what you are buying is a machine plus the VyomAnanta team doing the work on it. That is worth knowing because it changes who you are relying on — for this one, it is us, not a datacentre.
- There is no automatic failover on these sizes. A single machine is a single machine: if it goes down, the database is down until it comes back or we restore it elsewhere. Real high-availability needs a second machine and a failover mechanism, which we can build and which costs more than one machine does. Any page telling you a single node is highly available is selling you a word.
- The sizing above is guidance, not a guarantee. How much database a machine can carry depends on the shape of your data and the queries you run against it, and no table on any website knows either. Treat these as sensible starting points. We would rather move you up a size two weeks in than have you buy the biggest one today.
- We will not be the fastest quote you get. Sizing a database properly means asking about your workload first, which takes a conversation. If you want a number in ten seconds, the ladder above is honest and you can start there — but for anything that matters, we will want to talk first.
Tell us what it has to hold.
Roughly how much data, roughly how busy, and what it is running now. That is enough for us to size it, quote it and tell you what the migration would look like. Already have a machine with us? We can put the database on it instead of adding another.