Skip to main content
  • Free ($0): a shared PostgreSQL database for development and testing. 2 GB storage, 15 connections, no backups, deleted after 30 days of inactivity.
  • Solo ($29/mo): your own single-tenant VM (1 vCPU · 2 GB RAM · 30 GB NVMe) with daily backups, point-in-time recovery, and monitoring. Single node, so no automatic failover, but never deleted. Ideal for small production apps.
  • HA Cluster (from $49/node/mo): dedicated infrastructure with 1 to 3 nodes. Choose at least 2 nodes for automatic failover; applications must retry connections during a failover.
Open the free database in your dashboard and click Upgrade. We provision your dedicated Solo VM and migrate your data across automatically (typically ~3 minutes). Your free database stays online and untouched until you delete it, so you can verify everything first, then just point your app at the new host and credentials.
Rivestack supports PostgreSQL 16, 17, and 18. You choose your major version when creating a cluster.
Rivestack enables the following extensions by default on new databases:
  • pgvector: Vector similarity search for AI/ML embeddings
  • pgvectorscale (vectorscale): StreamingDiskANN indexes and scalable vector search
  • uuid-ossp: UUID generation
  • pg_stat_statements: SQL execution statistics tracking
  • pgcrypto: Cryptographic functions
  • pg_trgm: Trigram matching for similarity searches
Other supported extensions can be selected when creating or configuring a database. The dashboard shows the current list.
Yes. All managed endpoints require TLS and use publicly trusted Let’s Encrypt certificates. Use sslmode=verify-full so your client both encrypts the connection and verifies the database hostname. sslmode=require encrypts traffic but does not securely authenticate the server. No custom CA download is needed.
On HA clusters with 2 or more nodes, Patroni can promote a healthy replica and the load balancer keeps the same connection endpoint. Existing sessions disconnect, so applications must reconnect with bounded retries and backoff. Detection and promotion time depends on cluster and network conditions; Rivestack does not currently promise a fixed failover SLA. Because replication is asynchronous, a failure can also lose transactions that had not reached a replica.Single-node clusters do not have automatic failover. We recommend at least 2 nodes for production.
Solo and HA clusters include automated daily backups via pgBackRest, stored in S3-compatible object storage. Retention is 7 days on Solo and 14 days on HA clusters. You can also trigger manual backups and restore to any point in time within the retention window. Free tier databases are not backed up. See the Backups & Restore guide for details.
Yes. Rivestack supports point-in-time recovery (PITR) on Solo and HA clusters. Continuous WAL archiving lets you restore to any second within your backup retention window. Initiate a restore from the Backup tab in the dashboard.
  • EU Central: Falkenstein, Germany
  • US East: Virginia, USA
  • Asia Pacific: Singapore (Solo plan only)
Free and Solo are available in all regions. The HA tiers (Starter/Growth/Scale) are available in EU Central and US East only, so Singapore offers the Solo plan only. Pricing is set per region, and EU Central is the cheapest. See Pricing.
Yes. You can add or remove nodes (between 1 and 3) from the Management tab. Adding a node provisions a new replica that joins your cluster automatically. See the Scaling guide.Vertical scaling (changing server type) is not yet supported. To upgrade, create a new cluster with the desired server type and migrate your data.
  • Free: 15 direct PostgreSQL connections per database
  • Solo: 500 pooled client connections, 20 transaction slots per database
  • Starter: 2,000 pooled client connections, 25 transaction slots
  • Growth: 5,000 pooled client connections, 30 transaction slots
  • Scale: 10,000 pooled client connections, 40 transaction slots
Dedicated plans connect through PgBouncer in transaction-pooling mode, so clients beyond the slot count queue briefly instead of failing. Adding HA nodes improves availability, not connection capacity. See Limits for the full explanation.
Solo is a flat 29/month.HAclustersarebilledmonthlypernode(from29/month. HA clusters are billed monthly per node (from 49/node). Payment is processed via credit card through our payment provider. Scaling changes (adding/removing nodes) are prorated within your billing cycle. You can cancel anytime from the Billing page.
Yes. Cancel anytime from the Billing page in the dashboard. Your cluster remains active until the end of the current billing period.
Dedicated-plan data is stored on servers in the region you selected (EU, US, or Singapore), and backup traffic is sent to S3-compatible object storage over TLS. Database connections are encrypted in transit. Rivestack does not currently advertise application-level, customer-managed, or pgBackRest repository encryption at rest; contact us before relying on a specific at-rest encryption or compliance requirement.
Not as read-serving replicas yet. HA clusters with 2 or more nodes run streaming-replication standbys for automatic failover. All connections go through port 6432, and the load balancer routes every query (reads included) to the primary. A separate read-only replica endpoint that lets you offload reads is on our roadmap.
There is no free trial for HA clusters, but the Free tier lets you explore Rivestack at no cost with a shared PostgreSQL database (2 GB storage, 15 connections).
The dashboard provides real-time metrics including TPS, connections, CPU, memory, disk I/O, cache hit ratio, and replication lag. View historical data over 1 hour, 24 hours, or 7 days. See the Monitoring guide.