ONE INSTANCE. A CLEAR MONTHLY PLAN.

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
GETTING THE DETAILS RIGHT

Plans are being finalized.

We’ll publish monthly prices and clear limits before opening checkout. You can explore the workspace and read how the service works today.

Explore the workspace How billing works

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 or MySQL 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?+

No. These are single-instance deployments. Restarts, maintenance and recovery can cause downtime; a high-availability offering is outside the initial scope.