Polyer

MySQL

Deploy MySQL on Polyer for applications that need relational data, transactions and SQL. The built-in template creates a private mysql:8.4 service with persistent storage at /var/lib/mysql, a generated root password and a database named app. Review the connection URL and whether you need the optional TCP proxy.

DatabasesPolyer built-in

What you can use it for

  • Application databases for web services, CMSs and frameworks that expect MySQL.
  • Relational data with transactions and SQL, shared by several services over the private network.

What this template creates

mysqlmysql:8.4
Private service Persistent volume

Configuration to review

This template has no additional declared inputs. Review the generated variables, endpoints and resource settings in the deployment form.

How to deploy

  1. Select Configure deployment and sign in or create an account.
  2. Choose a new or existing project and select an available region.
  3. Review services, required inputs, storage and compatibility warnings. Submit the deployment only when the configuration is ready.
  4. Inspect deployment logs, complete the application's setup and test its endpoints before production use.

Operating this application

  • Connect your services with MYSQL_URL over the private network, and turn on the TCP proxy only when you need MYSQL_PUBLIC_URL from outside. Both URLs sign in as root, so consider creating a dedicated user with limited privileges for each application.
  • Changing MYSQL_ROOT_PASSWORD later does not change the actual root password, because MySQL applies it only when /var/lib/mysql is first initialized. Check the selected region's backup and recovery capabilities and test restoration before relying on a backup.
  • The mysql:8.4 tag follows 8.4 patch releases. Review storage use and major-version upgrade requirements before changing the image or version.

Hosting costs

CPU, memory, storage and network usage contribute to your bill. The selected region affects resource prices. A multi-service template incurs usage for each service; external APIs and software licenses are separate.

Review prices and estimate resource costs

Source and validation

This is a Polyer built-in database template.

Static compatibility analysis is not a live application verification. Test your chosen configuration and recovery workflow before using it for production.

Editorial content reviewed: 2026-10-10

Choose your next step