NewTruo Deploy and DBaaS PostgreSQL, live in the TruoCloud panelSee the catalog
PostgreSQL in production · MySQL and Valkey in beta

DBaaS

three engines managed end to end

Pick the engine, the size and the version. You get a dedicated endpoint over an encrypted connection, and you manage databases, users and backups from the panel. You build; we run the engine.

$ psql "postgresql://app@db-a1b2.node3.pg.truo.cloud:25432/app?sslmode=verify-ca"
✓ connected, TLS verify-ca

CONNECTION

Dedicated endpoint

Host and port exclusive to your service, reachable from any network.

ENCRYPTION

Encrypted connection

TLS on all three engines, with a per-service certificate you download from the panel.

RESOURCES

One VM per service

Your database shares no compute with other customers: performance doesn't depend on your neighbors.

OPERATIONS

Zero administration

Provisioning, engine patching, certificates and monitoring are on us.

ENGINES

Pick your engine

Each one has its own page: versions, plans, limits and frequently asked questions.

PostgreSQL

Available

A general-purpose relational database for most applications. It's the most mature engine of the family and the only one with managed backups.

From
$14.99/mo
Versions
17, 16, 15, 14 and 13
  • Full, differential and incremental on-demand backups
  • 7-day retention, stored off the server
  • TLS verify-ca with a per-service CA
See managed PostgreSQL

MySQL

Beta

For the applications that already speak MySQL and aren't going to move. Same control plane, same panel and the same price as PostgreSQL.

From
$14.99/mo
Versions
8.4 and 8.0
  • No managed backups yet: you handle your own
  • Outside the availability commitment while in beta
  • TLS verify-ca with a per-service CA
See managed MySQL

Valkey

Beta

Redis-protocol compatible in-memory cache, for sessions, queues, rate limiting and anything your application can rebuild.

From
$8.99/mo
Versions
Redis protocol
  • Your existing Redis clients work with no code changes
  • It's a cache, not primary storage: data can be lost
  • TLS-encrypted connection (rediss://)
See managed Valkey

COMPARISON

The differences, in one table

The same thing each engine page says, side by side and unvarnished.

PostgreSQLMySQLValkey
What it's forGeneral-purpose relational databaseApplications already on MySQLIn-memory cache
Versions13 to 178.0 and 8.4Redis protocol
From$14.99/mo$14.99/mo$8.99/mo
RAM ladder2 to 24 GB2 to 24 GB1 to 16 GB
Managed backupsYes, on-demand with 7-day retentionNot yetNo: it's a cache
Dedicated endpointYesYesYes
Encrypted connectionTLS verify-caTLS verify-caTLS (rediss://)
StatusAvailableBetaBeta
Availability commitmentIncludedOutside while in betaOutside while in beta

The high-availability tier for PostgreSQL and MySQL is in preparation and has no published price yet. Valkey has no high-availability tier and none is planned.

WHAT WE MANAGE

You build, we operate

You never see a server. Just your endpoint, your databases and your users.

  • Provisioning

    Your database is ready in minutes, with dedicated RAM and CPU from the start.

  • Databases and users

    Create databases and credentials from the panel, no ticket required.

  • Backups and restore

    On PostgreSQL, on-demand copies and restores with no tickets. Not on MySQL or Valkey yet.

  • Engine updates

    We apply the engine's patches and maintenance for you.

  • Monitoring

    Your service's state and metrics stay visible in the panel at all times.

  • Certificates

    We issue and renew your service's TLS identity automatically.

BACKUPS AND RESTORE

What gets backed up on each engine, no fine print

Managed backup isn't the same across the three engines, and saying so matters more than ticking a box. Today PostgreSQL is the only one with copies we manage; the other two are in beta and don't have them yet.

PostgreSQL

Managed backups included

Full, differential and incremental copies you trigger on demand from the panel. They travel encrypted to external storage, separate from your database's server, with seven days of retention.

MySQL

No managed backups

While it's in beta we don't manage the copies. If you use it today, logical backup is on you, from your own routine. When the engine leaves beta this changes and the page will say so.

Valkey

No managed backups

It's cache, not your primary store. We don't back it up, and the correct design is one where you can lose all of it without losing data: whatever lives only there is gone.

The high-availability tier — with longer retention and point-in-time recovery — can't be ordered yet. When it's available it will show up here with measured numbers, not before.

SECURITY

Your data, encrypted and isolated

Every service has its own cryptographic identity and its own exclusive resources.

  • Per-service private CA

    Your certificate is yours alone: the client verifies the server on every connection.

  • Backups off the server

    On PostgreSQL, copies travel encrypted to external storage, separate from your service.

  • Exclusive resources

    Your database shares no compute with other customers: performance doesn't depend on your neighbors.

Frequently asked questions

Your database, without running it.