Your first database
What to choose, what happens during setup, and what you receive.
Choose the engine your application expects
Use PostgreSQL if your application already uses PostgreSQL, MySQL if it expects MySQL, and Valkey for Redis-compatible caches, sessions and key-value workloads. These are different engines: changing between them usually requires an application migration. Choose a supported version and a location close to your application, rather than close to your laptop.
Choose a plan with room to grow
Compare usable storage, connection limits, database and user limits, and the recovery window. Each deployment has its own instance. Multiple databases inside that deployment share its storage and connection allowance.
Wait for setup to finish
After a confirmed payment, your workspace will show setup progress. Connection details become available after installation, security configuration, and health checks finish. A checkout success page alone is not proof that payment or deployment has completed.
DBTurbine is currently being built. Public checkout remains closed until provisioning and recovery are verified.
Make the first connection
Add your application's public egress IP to the allowlist, create a database and a scoped user, then use the connection details and CA certificate. Keep passwords on your application's server, never in browser code.