Managed PostgreSQL, MySQL, Valkey, MongoDB, Kafka and ClickHouse. Backups with point-in-time recovery, pooling and private networking in the plan price, HA from a flat +70%, and we migrate you off RDS free, with zero downtime.
Either you run it yourself and it pages you at night, or you pay someone and the managed bill arrives with ten line items you didn't order. Raff was built against both.
Every row on the left is a page you won't get. You keep the schema; we keep the pager.
One line. Backups, PITR, pooling, private networking and egress are in the price, not on the bill, and HA is a flat +70%, not a silent second instance.
Relational, cache, documents, streams and analytics: same console, same flat pricing, same private fabric. No second vendor for Kafka, no third for ClickHouse.
Eight things that show up as extra line items, paid tiers or surprise multipliers elsewhere. Here they're just how a database ships.
Use it from any host over TLS with IP allowlists. And if your app runs on Raff Apps, one click creates a virtual link: a private, encrypted wire straight from the service to the cluster. No connection strings pasted around, no public hop, $0 egress.
Pick a plan and watch the same cluster priced on Raff, AWS RDS and DigitalOcean, HA multipliers and typical extras included.
Competitor figures are modeled on each provider's published pricing (compute, storage, HA multipliers, typical egress and IOPS extras), gathered Jul 2026. Re-verify before relying on them.
Where each provider lands on the parts of managed that usually cost extra. Supabase is Postgres-only by design.
| Raff DBBest | AWS RDS | DigitalOcean | Supabase | |
|---|---|---|---|---|
| Engines under one roof | All 6 | Relational only | 5 engines | Postgres only |
| HA standby + failover | From +70% | 2× compute | 2× compute | Higher tiers |
| PITR (restore to any minute) | Included | Storage billed | Included | Paid add-on |
| Connection pooling | Built-in | RDS Proxy $$ | PgBouncer incl. | Included |
| Egress to your Raff app | $0 | $0.09/GB | Metered | 250 GB then paid |
| Private link to your app | 1 click | VPC setup | VPC setup | N/A |
| Query insights | Included | Paid tier | Basic | Included |
| Billing dimensions | 1–2 | 6–10 | 2 | 4+ |
| Spend cap on by default | Yes | No | Alerts only | Partial |
| Zero-downtime migration help | Free | DMS (DIY) | Self-serve | Self-serve |
| Runs on own cloud | Yes | Yes | Yes | Resells AWS |
| Starts at | $7.99/mo | ~$25/mo | $15/mo | $25/mo |
Competitor rows reflect each provider's published pricing, docs and default plan limits, gathered Jul 2026. Re-verify before relying on them.
Continuous logical replication keeps Raff in sync with your source while it stays live. When lag reads zero, you cut over: in seconds, not a weekend.
Point Raff at your RDS, DigitalOcean, Supabase or self-hosted instance with a read-only replication user. Nothing changes on your side.
Logical replication streams every write to your new Raff cluster while the source stays live. Watch the lag counter fall to zero.
Flip the connection string, or the virtual link if your app is on Raff. Writes land on Raff; the old bill stops.
Query insights, live metrics and log tails are in the console and the CLI, not a paid observability tier. One command provisions, one shows you exactly which query is eating the CPU.
A public status page for the database fleet, an SLA with credits, and restores we actually test, because a backup you've never restored is a rumor.
Managed Databases run on the same first-party cloud as the rest of Raff, and everything below connects over the private fabric.
Yes. pgvector, PostGIS and 60+ other extensions are available on every plan at no extra cost. Enable them from the console or with a single SQL command.
Yes. It speaks the standard MySQL wire protocol on port 3306, so existing connection strings, ORMs, WordPress and phpMyAdmin work unchanged. Point them at the new host and go.
Yes. Valkey forked from Redis 7.2 and keeps the RESP protocol and command set, so redis-py, ioredis, Jedis, go-redis and the rest connect with no code changes. Point them at the Valkey host and go.
Reach for ClickHouse when you run analytical queries, counts, sums and group-bys over very large, append-heavy tables like events, logs and metrics. For transactional app data with lots of small reads and writes, Postgres or MySQL is the better fit. Many teams run both.
Yes, open-source Apache Kafka 4.3 running in KRaft mode, speaking the standard Kafka protocol. Your existing producers, consumers and CLI tools work unchanged.
Postgres 14, 15 and 16. Minor version upgrades are applied automatically with zero downtime; major upgrades are a guided operation you trigger when ready.
Valkey is the Linux Foundation fork created when Redis changed its licence. It keeps the same protocol, commands and performance profile, but stays BSD-licensed and community-governed. For your app it behaves like Redis; for your legal team it stays open source.
HA plans run a three-node Galera cluster: every node holds the full dataset synchronously, and HAProxy routes writes to a healthy node. If a node fails, traffic moves automatically with no data loss, no ticket and no manual step.
No. Pricing is flat per cluster size, like every other Raff engine, and backups are included. A growing query volume never grows the bill.
We bill a flat plan price per cluster instead of metering ingress, egress and storage separately. You size the cluster, you see one line on the bill, and throughput within it does not generate surprise charges.
Postgres clusters archive WAL continuously, so you can restore to any minute in the retention window. Restores spin up as a new cluster, so you can inspect the data before promoting it.
Yes. MySQL 8 with InnoDB is the database WordPress is built for. Create the cluster, point wp-config.php at the private endpoint (or the public one with an IP allowlist), and daily backups cover the rest.
HA adds a synchronous standby with automatic failover for a flat percentage of the plan price, from +70% depending on the engine, shown upfront on the same single bill line. On RDS and DigitalOcean, enabling HA silently provisions a second instance billed at full rate.
HA adds a synchronous standby with automatic failover for a flat percentage of the plan price, from +70% depending on the engine, shown upfront on the same single bill line. On RDS and DigitalOcean, enabling HA silently provisions a second instance billed at full rate.
You can. RDB persistence means your data survives restarts and failovers, and nightly plus on-demand snapshots cover recovery, restored as a new instance or in place. For strictly ephemeral caching, use it purely as a cache with eviction policies.
HA adds a synchronous standby with automatic failover for a flat percentage of the plan price, from +70% depending on the engine, shown upfront on the same single bill line. On RDS and DigitalOcean, enabling HA silently provisions a second instance billed at full rate.
HA adds a synchronous standby with automatic failover for a flat percentage of the plan price, from +70% depending on the engine, shown upfront on the same single bill line. On RDS and DigitalOcean, enabling HA silently provisions a second instance billed at full rate.
HA adds a synchronous standby with automatic failover for a flat percentage of the plan price, from +70% depending on the engine, shown upfront on the same single bill line. On RDS and DigitalOcean, enabling HA silently provisions a second instance billed at full rate.
One line per cluster: engine plus size, with the HA percentage folded in if you enabled it. The engine’s protection features, private networking, metrics and fabric egress are inside the plan. The only possible second line is overage storage at a flat per-GB rate.
One line per cluster: engine plus size, with the HA percentage folded in if you enabled it. The engine’s protection features, private networking, metrics and fabric egress are inside the plan. The only possible second line is overage storage at a flat per-GB rate.
Yes, it is a standalone product. Connect from anywhere over TLS with IP allowlists and scoped credentials. If your app runs on Raff Apps, a one-click private link adds a private wire with $0 egress on top.
Kafka is private-network only by design: clients connect over the private fabric or a one-click private link from your Raff services, never the open internet. Exposing Kafka brokers publicly is an anti-pattern, so unlike our other engines there is no public endpoint. Producers and consumers authenticate with SCRAM credentials over TLS.
One line per cluster: engine plus size, with the HA percentage folded in if you enabled it. The engine’s protection features, private networking, metrics and fabric egress are inside the plan. The only possible second line is overage storage at a flat per-GB rate.
One line per cluster: engine plus size, with the HA percentage folded in if you enabled it. The engine’s protection features, private networking, metrics and fabric egress are inside the plan. The only possible second line is overage storage at a flat per-GB rate.
One line per cluster: engine plus size, with the HA percentage folded in if you enabled it. The engine’s protection features, private networking, metrics and fabric egress are inside the plan. The only possible second line is overage storage at a flat per-GB rate.
Yes, it is a standalone product. Connect from anywhere over TLS with IP allowlists and scoped credentials. If your app runs on Raff Apps, a one-click private link adds a private wire with $0 egress on top.
Yes, it is a standalone product. Connect from anywhere over TLS with IP allowlists and scoped credentials. If your app runs on Raff Apps, a one-click private link adds a private wire with $0 egress on top.
Yes, it is a standalone product. Connect from anywhere over TLS with IP allowlists and scoped credentials. If your app runs on Raff Apps, a one-click private link adds a private wire with $0 egress on top.
Six engines, backups and pooling in the price, a bill you can read in one line. Provision a cluster in 60 seconds, or let us migrate yours for free.