Database deployments

Managed PostgreSQL and MySQL, with automatic failover

Production databases without the database administration. Automatic failover, scheduled backups, an IP allow-list and TLS on every plan. From ₹781 a month.

  • PostgreSQL 16 and 17
  • MySQL 8.0 and 8.4
  • Backups on a schedule

Plans

Database hosting plans

A plan sets the CPU, memory, storage and connection limit of a database.

PlanvCPUMemoryStorageBandwidth / monthConnectionsCredits / hourPer month
MicroDevelopment and evaluation.0.25512 MB5 GB1 TB251.07₹781
StarterPopularSmall production workloads.0.51 GB10 GB2 TB502.14₹1,562
StandardProduction workloads with moderate data.12 GB25 GB4 TB1004.74₹3,460
ProfessionalHigh-throughput production.24 GB50 GB6 TB2009.47₹6,913

Prices are per database, charged by the minute at the hourly rate. A month is 730 hours.

Included

What every deployment gets

Automatic failover

If the primary fails, a standby takes over and your connection address stays the same.

Read replica

Send read-only queries to a replica to take reporting and heavy SELECT traffic off the primary.

Scheduled and on-demand backups

Choose how often backups run, from every hour to once a day, and how many to keep. Take one by hand at any time.

Restore

Restore the database from any kept backup in the dashboard.

IP allow-list

Nothing can connect until you add the addresses or ranges that should reach the database.

TLS

Connections are encrypted. Download the platform certificate authority to verify the server from your application.

Query console

Run queries from the dashboard without opening the database to your own machine.

Data import

Bring an existing database in from a dump.

Optional Redis cache

Add an in-memory cache beside the database for fast reads and sessions. Charged at its own plan rate.

Works with

Engines and versions

Connect from any language with a standard driver. An API hosted on MultiConnect links to a database with one switch.

Read the Database hosting guide
  • MySQL 8.0 and 8.4
  • PostgreSQL 16 and 17

Good to know

  • Deleting a database deletes its data and backups. Before deletion a final backup is taken and a download link is emailed, valid for a limited time.
  • A zero balance deletes databases too, like every other deployment. Top up before then; balance alerts are sent.
  • Keep your own copies of important data. Platform backups are for recovery inside the platform.
  • A plan change interrupts writes briefly, for under a minute, while the switch-over happens.
  • Backup storage beyond the plan amount is charged per GB from your balance.

Questions

Which database engines are supported?

PostgreSQL 16 and 17, and MySQL 8.0 and 8.4.

Is failover automatic?

Yes. If the primary fails, a standby is promoted and connections are routed to it. The connection address does not change; applications should reconnect after a brief interruption.

Can I send read queries somewhere other than the primary?

Yes. A read replica accepts read-only queries, which moves reporting and heavy SELECT traffic off the primary.

How do I connect from my application?

The dashboard shows the host, port and a ready connection string for your framework. Add your application's IP addresses to the allow-list first; connections from anywhere else are refused.

How often are backups taken?

You choose: every 1, 2, 4, 6, 12 or 24 hours, and how many recent backups to keep.

Do databases autoscale?

No. A database has the size its plan sets. Change plan from the dashboard when you need more.

Try it with 500 free credits

Create an account and you get 500 credits to deploy with. No credit card required. There is no free hosting tier; the credits are the trial.