Skip to content
Databases

Databases you don’t have to babysit

PostgreSQL, MySQL and Valkey (Redis-compatible), installed from official images, connected over TLS and backed up on your schedule — with metrics, slow queries and logs on one page.

  • Official images
  • TLS connections
  • Daily backups, kept 7 days
  • Billed by the hour
Choose an engine
  • PostgreSQLRecommended17 · 18
  • MySQL8.4 LTS
  • Valkey9.0 · 9.1 · Redis-compatible
  • MongoDBComing soon
  • OpenSearchComing soon
Example screen.
Choose your engine

Which database should I use?

Three engines, each from its official image. Pick by what you’re storing.

PostgreSQL

17 · 18

The default for new apps

Use it for
  • Relational data with complex queries
  • Django, Rails, Node.js and Go apps
  • JSON alongside tables

Restore into a new database

Explore PostgreSQL

MySQL

8.4 LTS

When your software expects MySQL

Use it for
  • WordPress, Laravel and PHP apps
  • Existing MySQL schemas
  • Read-heavy websites

Backed up daily; restore coming soon

Explore MySQL

Valkey

9.0 · 9.1 · Redis-compatible

For speed, not for records

Use it for
  • Sessions and caches
  • Queues and rate limits
  • Leaderboards and counters

Durable mode: restore into a new database

Explore Valkey

Coming next: MongoDB for documents and OpenSearch for search — marked ‘Coming soon’ in the console.

Coming soon
Why databases

The parts of running a database nobody signed up for

Your problem

Keeping the database patched and running is a second job.

On Drasken Cloud

We install it from the engine’s official image, keep it running and show its health in plain words.

Your problem

Backups are something you’ll set up next week.

On Drasken Cloud

Every database that keeps data on disk is backed up daily and each backup is kept 7 days, unless you change it. PostgreSQL and Valkey restore into a new database.

Your problem

You find out the disk is full when writes start failing.

On Drasken Cloud

Storage, metrics, slow queries and logs sit on the database’s page, and you can set alerts for when it needs attention.

What's included

Everything a production database needs

Backups on your schedule

Every 6 or 12 hours, daily or weekly; keep each one 1 to 35 days.

Restore into a new database

Check the copy, then switch. PostgreSQL and Valkey today; MySQL soon.

Private by default

Apps and jobs in the same project connect over TLS.

Ready-made connection strings

URI and command line, JDBC for PostgreSQL and MySQL, plus the CA certificate.

Clear version labels

Recommended, Supported, Deprecated or End of life — no guessing.

Metrics and slow queries

CPU, memory, storage, connections and the slowest queries.

How it works

Ready in a few minutes

Step 1: Choose engine and version

The create page picks the recommended version for you.

Step 2: Pick a size

Plans up to 4 vCPU and 16 GB of memory.

Step 3: Connect from your app

Copy the URI into a secret such as DATABASE_URL and deploy.

Details

Specifications

Engines
PostgreSQL 17, 18 · MySQL 8.4 · Valkey 9.0, 9.1
Size
Up to 4 vCPU and 16 GB of memory
Availability
One instance; high availability is coming soon
Access
Private to apps and jobs in the same project, over TLS
Backups
Daily, kept 7 days by default; every 6 h to weekly, 1–35 days
Restore
Into a new database (PostgreSQL, Valkey); MySQL coming soon
Region
Mumbai, India
Pricing

A monthly price per plan, charged by the hour

A month is 730 hours and never costs more than its monthly price.

How pricing works
PostgreSQLGeneral · 1 GB · 1 vCPU · 10 GB storage
₹1,450 /mo
MySQLGeneral · 1 GB · 1 vCPU · 10 GB storage
₹1,450 /mo
ValkeyGeneral · 1 GB · 1 vCPU · 2 GB storage
₹1,370 /mo
Questions

Questions about databases

  • Standard databases run on one instance. High availability is coming soon; backups protect your data today.

Spend this week on your product, not your servers.

Create an account, add a project and deploy your first app.

  • Billed by the hour in rupees
  • Cancel any time
  • One GST invoice a month