Your app needs MySQL, but installing it by hand means choosing a server, installing packages, creating users, and hoping you can repeat the same setup when you need another environment.
This guide shows how to deploy MySQL to your own cloud without doing that server work from scratch each time.
Run MySQL without repeating the manual setup
MySQL fits dev, test, staging, internal tools, and private apps where you want a database you control.
Running it on a cloud computer you rent from a provider still means installing the database, opening the right port, creating users and passwords, and making sure the database comes back the same way after you deploy again. Devopness handles those repetitive parts on Ubuntu servers so you can focus on using the database.
Ask your AI assistant to deploy MySQL
If you use Cursor, Claude Code, Codex, or another AI coding tool, you can deploy MySQL from the same conversation. Devopness connects to these tools through MCP, which lets an AI assistant perform approved actions in other products.
- Create a free Devopness account
- Connect the Devopness MCP server to your AI assistant
- Tell your AI assistant:
Use Devopness to deploy MySQL to my cloud account.
Guide me through the missing details, one step at a time.
Deploy the database and verify that it is running.
Your assistant will ask which cloud account to use and guide you through the remaining choices. If Devopness needs permission to access your cloud provider, the assistant will tell you how to connect the account rather than guessing.
Devopness keeps the setup visible. The assistant performs the steps, and you can review what it created in the web app without sharing your cloud keys in the chat.
Use the browser in the web app
You can also deploy in the Devopness web app:
- Open Services and select add service
- On Building, select MySQL and Version
8.0 - Select Confirm
Devopness creates the service and opens its details page. MySQL is a service in Devopness, not an application.
Next, link the cloud computer where MySQL will run:
- Open the Servers tab
- Select link server
- Choose an existing server, or select Create a new server and follow the guided setup
When the service is ready to deploy:
- Select deploy
- On the Servers step, confirm the target server or servers
- Review your choices and select Deploy
If you do not have a server yet, Devopness guides you through adding one on AWS, Azure, GCP, DigitalOcean, Hetzner, or another supported provider.
After you select Deploy, Devopness opens the action page with deployment logs. You can follow every step from a desktop or mobile browser, wherever you are, without connecting through SSH or using Linux commands.
If a step fails, ask your AI assistant to read the logs, explain what went wrong, and guide you through the fix before deploying again.
What Devopness sets up for you
The MySQL service handles these parts:
- installs MySQL on the server you selected
- creates the database users and passwords
- configures the service to start with the server
- keeps the setup visible and editable in Devopness
MySQL runs in your cloud account, so you can use any eligible startup or trial credits available from your provider. You choose the server and version. Everything Devopness creates remains visible in the web app.
Once MySQL is configured, you can reuse that setup to deploy it again on another server across AWS, Azure, GCP, DigitalOcean, and Hetzner. If you change cloud providers later, you can reuse the setup instead of starting again.
Confirm MySQL is ready
When the deployment finishes, check your email for Details of your service: MySQL:8.0. Devopness sends the connection details once, including the server address, port, usernames, passwords, and default database name. Save that email in a safe place.
To verify the database is working:
- confirm the deployment action completed successfully in Devopness
- open the email and note the host, port, and credentials
- connect from your app or a database tool using those details
That is the fastest way to confirm MySQL is running and ready for your project.
When a managed database is the better fit
Use this setup when you want control and repeatability without repeating manual server work.
If you are choosing a primary production database, a managed service like Amazon RDS, Neon, or Supabase may still be the better fit. Those services handle backups, patching, and recovery for you.
Create a free Devopness account and choose the path you prefer: send the prompt above to your AI assistant, or select add service under Services in the web app.
Less setup. More time for the work that matters.
Save time. Keep control.
Happy deploying!