Skip to content

Supported databases and features

Last updated View as Markdown Agent setup

Database support

The following table shows which database engines and/or specific database providers are supported.

Database Engine Supported Known supported versions Details
PostgreSQL ✅ 9.0 to 17.x Both self-hosted and managed (AWS, Azure, Google Cloud, Oracle) instances are supported.
MySQL ✅ 5.7 to 8.x Both self-hosted and managed (AWS, Azure, Google Cloud, Oracle) instances are supported. MariaDB is also supported.
SQL Server Not currently supported.
MongoDB Not currently supported.

Supported database providers

Hyperdrive supports managed Postgres and MySQL databases provided by various providers, including AWS, Azure, and GCP. Refer to Examples to see how to connect to various database providers.

Hyperdrive also supports databases that are compatible with the Postgres or MySQL protocol. The following is a non-exhaustive list of Postgres or MySQL-compatible database providers:

Database Engine Supported Known supported versions Details
AWS Aurora ✅ All Postgres-compatible and MySQL-compatible. Refer to AWS Aurora examples for MySQL and Postgres.
Neon ✅ All Neon currently runs Postgres 15.x
Supabase ✅ All Supabase currently runs Postgres 15.x
Timescale ✅ All See the Timescale guide to connect.
Materialize ✅ All Postgres-compatible. Refer to the Materialize guide to connect.
CockroachDB ✅ All Postgres-compatible. Refer to the CockroachDB guide to connect.
PlanetScale ✅ All PlanetScale provides MySQL-compatible and PostgreSQL databases
MariaDB ✅ All MySQL-compatible.

Supported TLS (SSL) modes

PostgreSQL

Hyperdrive supports the following PostgreSQL TLS (SSL) ↗ connection modes when connecting to your origin database:

Mode Supported Details
none No Hyperdrive does not support insecure plain text connections.
prefer No (use require) Hyperdrive will always use TLS.
require Yes (default) TLS is required, and server certificates are validated (based on WebPKI).
verify-ca Yes Verifies the server's TLS certificate is signed by a root CA on the client. This ensures the server has a certificate the client trusts.
verify-full Yes Identical to verify-ca, but also requires the database hostname must match a Subject Alternative Name (SAN) present on the certificate.

MySQL

Hyperdrive supports the following MySQL TLS (SSL) ↗ connection modes when connecting to your origin database:

Mode Supported Details
DISABLED No Hyperdrive does not support insecure plain text connections.
PREFERRED No (use REQUIRED) Hyperdrive will always use TLS.
REQUIRED Yes (default) TLS is required, and server certificates are validated (based on WebPKI).
VERIFY_CA Yes Verifies the server's TLS certificate is signed by a root CA on the client. This ensures the server has a certificate the client trusts.
VERIFY_IDENTITY Yes In addition to VERIFY_CA checks, Hyperdrive requires the database hostname to match a Subject Alternative Name (SAN) or Common Name (CN) on the certificate.

Refer to SSL/TLS certificates documentation for details on how to configure these TLS (SSL) modes for Hyperdrive.

Supported PostgreSQL authentication modes

Hyperdrive supports the following authentication modes ↗ for connecting to PostgreSQL databases:

  • Password Authentication (md5)
  • Password Authentication (password) (clear-text password)
  • SASL Authentication (SCRAM-SHA-256)

Unsupported PostgreSQL features:

Hyperdrive does not support the following PostgreSQL features:

  • SQL-level management of prepared statements, such as using PREPARE, DISCARD, DEALLOCATE, or EXECUTE.
  • Advisory locks (PostgreSQL documentation ↗).
  • LISTEN and NOTIFY.
  • PREPARE and DEALLOCATE.
  • Any modification to per-session state not explicitly documented as supported elsewhere.

Unsupported MySQL features:

Hyperdrive does not support the following MySQL features:

In cases where you need to issue these unsupported statements from your application, the Hyperdrive team recommends setting up a second, direct client without Hyperdrive.

Was this helpful?