Skip to content
dbturbine.A TurbineWeb Company
PlatformPricingDocumentationSign in
dbturbine.A TurbineWeb Company

For the data behind what you’re building.

ExplorePlans & pricingDocumentation
The TurbineWeb familyTurbineWeb TurbinePress StaticWeb.site

PostgreSQL, MySQL & Valkey.
A dedicated instance.
Room to build.

Start with the basics
© 2026 TurbineWeb. DBTurbine is a TurbineWeb service.
TermsPrivacy
All database engines
YugabyteDBManaged YugabyteDB

SQL that can grow across nodes.

YugabyteDB combines a PostgreSQL-compatible SQL interface with distributed storage. Tables are split into tablets and replicated across nodes, so capacity and availability are properties of the cluster rather than one machine.

Configure your databaseConnection guide
YugabyteDBYugabyteDB / a familiar starting point
CREATE TABLE orders (
  account_id UUID, order_id UUID,
  total NUMERIC(12,2),
  PRIMARY KEY (account_id, order_id)
);
Illustrative query · use your own schema and access rules

Working with YugabyteDB

Choose it for the work
it does well.

01

A familiar SQL connection

Use PostgreSQL-compatible clients and drivers through YSQL. Check application features and extensions before migration; compatibility is not identical to PostgreSQL.

Read the official guide
02

Replication at the storage layer

With replication factor three, data is stored on three tablet servers. A healthy majority participates in consensus before writes are acknowledged.

Read the official guide
03

Add capacity without a second database

Additional tablet servers join the same cluster. Data placement can rebalance, while applications retain their connection endpoint.

Read the official guide

Where it fits.

Applications that need relational SQL, transactions and a path to distributing data across multiple nodes.

Before you choose

DBTurbine supports clusters of at least three nodes in one region, or synchronous RF3 across three live regions when enabled. Node counts are configurable by region. Full cloud backups are consistent per database; PostgreSQL WAL recovery and all PostgreSQL extensions are not included. Regional failover interrupts connections and requires a surviving majority.

Your database.
The server work, covered.

The workspace brings connections, access and recovery together. Your application keeps its standard database client.

Connect with confidence

Find your endpoint, port, credentials and certificate together, with examples for standard clients.

Control who gets in

Set allowed IPs and give applications separate users. Review permissions before opening access.

Keep recovery separate

Full cloud backups provide restore points away from the live database server.

YugabyteDB

Give YugabyteDB its own workspace.

Choose a published node type, region and storage. Review your monthly total before checkout.

See configurations