We currently offer 5 different database types to fulfill various data storage needs:

  • Redis 5.0, 6.x and 7.x
  • MariaDB 10.4, 10.5, 10.6, 10.11, 11.0 and 11.1
  • PostgreSQL 9.6, 10, 11, 12, 13, 14, 15, 16, and 17
  • MySQL 8.0 and 9.0
  • Valkey 7.2

You can attach databases to applications or run databases by themselves.

It’s also possible to utilize a Dockerfile and persistent storage to deploy other types of databases on Application Hosting.

​
Add a database

Only Company Owners and Company Administrators can add a new database. For more information about user roles and permissions, refer to User Management.

To add a database, within Databases click Add database.

Add a new database.

  • Type and version: The database software and version you want to use. Currently, we support:
    • Redis 5.0, 6.x and 7.x
    • MariaDB 10.4, 10.5, 10.6, 11.0 and 11.1
    • PostgreSQL 9.6, 10, 11, 12, 13, 14, 15, 16, and 17
    • MySQL 8.0
    • Valkey 7.2
  • Enable pgvector extension: This option is only available for new databases on PostgreSQL version 11 and above. This extension enables fast vector similarity search, making it easy to store and query high-dimensional vectors. Commonly used in AI, machine learning, and recommendation systems, it helps compare vector embeddings efficiently.
  • Enable PostGIS extension: This option is only available for new databases on PostgreSQL version 13 and above. This adds support for geographic and spatial data types, enabling advanced location-based queries and operations. It allows PostgreSQL to store, query, and analyze geographic objects such as points, lines, and polygons. It adds the following extensions to your database:
    • postgis
    • postgis_topology
    • postgis_tiger_geocoder
    • fuzzystrmatch
    • address_standardizer
    • address_standardizer_data_us
  • Database name: The name of the database that you will use to connect to it. By default, this is populated with three random words. Some database names are restricted for security reasons. The full list of invalid database names is shown below.
  • Database user: This only applies to PostgreSQL, MySQL, and MariaDB. This is the username you want to use to connect to the database. By default, this is populated with a random word. Once tied to an application, we can auto-populate your environment variables with this data. Some database usernames are restricted for security reasons. The full list of invalid database usernames is shown below.
  • Database password: The password you want to use to connect to the database. We recommend leaving this as-is. Once tied to an application, we can auto-populate your environment variables with this data.
  • Name: The name that will be shown in Sevalla. By default, this is populated with the same three random words as the Database name.
  • Location: Choose the data center you want to use for this database. By default, this is populated with the location closest to you.

Currently, internal connections are only supported between applications and databases in the same region. If you’d like to use a database with your application, you can create the database at Sevalla and use an internal connection between the two (on the application’s Settings page or the database’s Info page).

  • Resources: Choose the resources you will need for this database. If you have not added a payment method, you can only select DB1. If you need to increase the size in the future, you can do so within Settings > Edit details.

Relational databases such as MariaDB and MySQL organize data in predefined relationships where data is stored in tables (or “relations”) of columns and rows to make it easy to see and understand how different data structures relate to each other. This means the database size includes these relations and, therefore, will always be larger than the actual data in the database.

The Overview panel allows you to review your database’s costs. In the Payment method panel, you can confirm your payment method or add a new one if necessary. To create the database, click Create.

​
Invalid MySQL database names and usernames:

  • mysql
  • information_schema
  • performance_schema
  • sys

​
Invalid PostgreSQL database names usernames:

  • postgres
  • template0
  • template1
  • information_schema
  • performance_schema
  • sys