Choose an engine, node type and region. Compare resources, cloud backup allowances and recovery options before checkout.
Choose a node type and the quantity in each region. See node charges and regional load balancers separately.
Live storage and cloud backup storage are separate allowances. All databases on one deployment share its limits. Single-instance deployments do not include automatic failover.
Payments are processed through Polar under the TurbineWeb billing identity. Your statement may include TURBINEWEB or Polar. Read billing details →
Yes. Use your existing PostgreSQL, MySQL, Redis-compatible or ClickHouse HTTPS client and update its server-side connection settings. Your application's engine/version must be compatible.
Backups and recovery logs are stored off-server in S3-compatible cloud storage. They are separate from your live database.
The default restore creates a separate server. You can test the recovered copy before switching your application. Additional instance costs must be confirmed before restoring.
Choose node quantities for each region. HA requires at least three primary-region nodes for automatic writer failover; a single instance has one node. Remote PostgreSQL readers are asynchronous and do not automatically become writers; Valkey failover can lose recent writes.