A little clarity
for your next build.
Choose the room your data needs. Full backups, recovery logs,
and the controls that make day-to-day work easier.
PostgreSQL
MySQL
Valkey
ClickHouseBuild your configuration
Your regions. Your node counts.
One clear monthly total.
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 →
A few useful answers.
Can I use my existing application?+
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.
Where do backups go?+
Backups and recovery logs are stored off-server in S3-compatible cloud storage. They are separate from your live database.
Will restoring overwrite my 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.
Is there automatic failover?+
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.