Skip to content
EN
Русский English
Connect a server

Databases without the command line.

Create databases, manage users and access permissions right from the panel. phpMyAdmin in one click.

Connect a server All features
  • 7 days free
  • No card required
  • Payment in rubles
Process listsped up
Connections 44/ 500
Queries / sec 312
Buffer pool 67%
ID Query > 5 s> 30 s
Process #4821 killed · list refreshed prod-01 · MySQL 8.0
0
SQL commands to create a database and a user and grant privileges
1click
to phpMyAdmin — password-free login right from the database list
5min
between refreshes of MySQL stats and database sizes
4
dump formats for import: .sql, .sql.gz, .sql.zst and .zip

Access

Users and permissions. Without a single SQL command.

What you would normally open the mysql console for — users, privileges, dump import, credentials in .env — takes a form and a button in the panel.

New databaseA database and its user — in one form

Enter the database name — the username follows it, and a button generates the password. Deploykin creates the database, sets up the user and grants the privileges itself.

  • A new user, an existing one, or a database with no user
  • Read-only and remote access — in the same form
  • utf8mb4 character set — by default
New databaseprod-01 · MySQL 8.0
Created
Databaseutf8mb4
Name
blog

UserGenerate password

Username
blog
Password
Qm7kT2xVw9LrB4nZc8HsY3pD
Read-only
Remote access

Deploykin runs this for you

CREATE DATABASE blog
done
CREATE USER 'blog'@'localhost'
done
GRANT ALL PRIVILEGES ON blog.*
done
Database, user and privileges are readyCreate

Users and permissionsGranular access permissions

Create database users, set passwords, configure full access or read-only. Manage remote access for each user.

  • Create users with secure passwords
  • Full access or read-only (SELECT only)
  • Grant and revoke privileges from the panel
  • Remote access: a cluster server, a custom IP or any host
  • System schemas mysql, sys and performance_schema — behind a separate checkbox
Usersprod-01 · MySQL 8.0
Add
UserAccess
shopshop · localhost
Full access
shop_roshop · localhost
Read-only
analyticsshop, app · 10.0.0.7
Read-only
SELECT granted on shop and app

phpMyAdminphpMyAdmin in one click

Install phpMyAdmin as a site template and log in without a password — with the button next to the user in the database list. Basic Auth puts a second password in front of the login page.

  • Install as a 1-click site template
  • Auto-login integration with Deploykin
  • Basic Auth protection against unauthorized access
  • SSL certificate — in one click, as for any site
  • Auto-login is available only to those who manage the team's servers
phpMyAdminpma.example.com
Basic Auth
DatabaseLog in as
shop1,2 GB
shop
app640 MB
app

Auto-login

pma.example.comlogged in as shop · no password

ImportSQL file import

Upload a dump through the panel — Deploykin imports it into the chosen database with no console.

  • .sql, .sql.gz, .sql.zst and .zip formats — unpacked on the server
  • Up to 100 MB — uploaded straight from the browser
  • Large dumps — by the file path on the server
  • The import itself runs on the server as a background task
Dump importprod-01 · MySQL 8.0
Done
Upload fileServer path
Fileshop.sql.zst
Target databaseshop

Imported into shop84 / 84 MB

Formats .sql .sql.gz .sql.zst .zip

Site integrationAutomatic .env updates

When you create a Laravel site, Deploykin sets up the database and its user and writes the credentials to .env itself. Change the user's password — it is updated in the .env of every site that connects with it.

  • A database user's new password is carried into the site's .env
  • The file is locked to mode 600 and owned by the site's user
  • No manual config edits
.envshop.example.com
Updated 
DB_CONNECTION=mysql
DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=shop
DB_USERNAME=shopDB_PASSWORD=x2Rt••••••••••••
.env updated automatically

MySQL dashboard

A stuck query — find it and kill it.

No more connecting over SSH and running KILL manually. Find the slow query in the process list and terminate it in one click.

  • Connections, queries per second, buffer pool and slow queries — on one screen
  • List filters: all, active, sleeping and slower than 5 seconds
  • Queries running longer than 30 seconds are highlighted in red
  • Data refreshes every 5 minutes and right after a process is killed
  • No SSH, no console, no KILL commands

Server and site monitoring

MySQLprod-01 · 8.0 · uptime 42 days
running
Connections44 / 500
Queries / sec312
Buffer pool67%
Slow queries0

Process listTime

SELECT p.*, c.name FROM products p JOIN…#4821 · shop_ro @ 10.0.0.7 · shop
killed
Sleep#4873 · app @ localhost · app
12 s
UPDATE carts SET updated_at = NOW()…#4907 · shop @ localhost · shop
0 s
SELECT * FROM orders WHERE status…#4911 · shop @ localhost · shop
0 s
Process #4821 killed · list refreshed

MySQL settings

MySQL tuning — without editing my.cnf.

The connection limit, InnoDB buffer pool, character set, slow query log and binary logs are changed in the package settings. Next to the field the panel suggests a value for your server's memory.

  • max_connections and innodb_buffer_pool_size — with a recommendation for your server
  • Slow query log with a long_query_time threshold
  • Remote connections: bind-address and the firewall rule for port 3306 — with one switch
  • Binary logs are off by default so they do not fill the disk
  • If MySQL fails to start with the new config, the previous one is restored

How auto-tuning works

MySQL settingsprod-01 · 8 GB RAM
Applied
ParameterValue
max_connectionsrecommended: 500
500
innodb_buffer_pool_sizerecommended: 3200M
3200M

Slow query log

Log slow queries
long_query_time
2 s
Log file
mysql-slow.log
Settings applied · MySQL restartedSave

Cluster

A dedicated database server. Access for your servers only.

Inside a cluster the MySQL and Redis ports are open only to neighboring servers, not to the whole internet. Deploykin writes the database address into the site's .env itself.

Database on a separate server

Move the database to a dedicated server

Keep your application and database on different servers. Deploykin connects the site to MySQL on a dedicated database server and opens port 3306 only to the servers of the same cluster — the firewall is configured automatically.

  • Connect a site to MySQL on another server
  • The firewall automatically lets in only the cluster's servers
  • .env is updated with the host, port and credentials automatically
  • Scale your application and database independently
Firewall db-01UFW · port 3306 closed to the outside
MySQL
Allowed forPort
web-0110.0.0.2
3306/tcp
worker-0110.0.0.3
3306/tcp
web-0210.0.0.4
3306/tcp
Port 3306 is open to web-02 — and to no one else
Redis

Redis for cache and queues

Install Redis on a server in one click and configure it with a form: password, memory limit, eviction policy, AOF. Access for the cluster's servers is one switch — bind and the firewall configure themselves.

  • Install Redis as a service on the server
  • Redis configuration editor from the panel
  • Bind and firewall for the right network
  • Redis access between servers of one cluster
Redisdb-01 · redis.conf
Applied
Cluster accessport 6379 open to the cluster
bind 127.0.0.1 10.0.0.5port 6379
requirepass ••••••••••••
maxmemory 512mb
maxmemory-policy allkeys-lru
appendonly yes

What else

Backups, clones and database sizes — from the panel too.

What happens to the data once the database exists — also without a console.

  • Scheduled backups

    A dump of any database — from every 10 minutes to once a month, or on your own cron. With encryption and archive verification.

  • MyDumper for large databases

    Two dump engines: classic mysqldump and parallel MyDumper, which dumps large databases in several threads.

  • Database cloning

    When you clone a site, its database is copied in full — to the same server or to another one.

  • Database sizes

    The size of each database is tracked automatically — you can see what's growing and using disk.

  • Passwords under watch

    A user's password is hidden and revealed on click — only to those who manage servers. Every reveal is logged.

  • SQL for the AI assistant

    The assistant and MCP clients read the database as a separate SELECT-only user — the application's credentials are never handed to them.

In the panel 203.0.113.21 Connect done in 4 min 52 s

Manage databases without SQL.

Create databases and users and configure permissions — all from the panel, without the command line.

Start for free Backups
  • 7 days free
  • No card required
  • Human support

We use cookies and the Yandex Metrica web-analytics service (including Session Replay) to improve the site. Details are in the privacy policy.