Databases

MySQL and MariaDB VPS HostingA Database Server That Is Only Yours

Move your database off a shared server or off your app server. We install MySQL or MariaDB, size the InnoDB buffer pool for your plan, allow connections only from the servers you name and hand you root.

View VPS Plans Talk to an Engineer

Full root & SSH NVMe storage Daily backups Anti-DDoS 99.9% uptime SLA 11 locations

  • Reserved RAM

    Memory for the InnoDB buffer pool, not shared with others.

  • NVMe storage

    Fast random I/O for indexes and writes.

  • Root access

    Full control over my.cnf, users and replication.

  • Daily backups

    Whole-server backup of the previous 24 hours.

Why a VPS

Why Put Your Database on a VPS

On shared hosting the database server is shared too, with fixed limits on connections and queries. On a VPS it is yours to size and tune.

  1. No shared limits

    Set max_connections, timeouts and query limits for your application, not for a host's thousands of accounts.

  2. Memory sized for your data

    Give the InnoDB buffer pool most of the plan's RAM so hot tables and indexes are served from memory.

  3. App and database apart

    Run the database on its own VPS so heavy queries do not slow your web server, and size each server separately.

  4. Control over versions

    Pick MySQL 8.4 LTS or a MariaDB LTS release, enable binary logs and add replication when you need it.

The stack

A Dedicated Database Server

Applications connect over a restricted port with their own users; the engine and fast storage sit underneath.

Query from your application server

  1. Network

    UFW allow-list

    Port 3306 open only to your app servers, or closed if the app runs on the same VPS.

  2. Access

    Users and grants

    One user per application, limited to its own database and the hosts it connects from.

  3. Engine

    MySQL or MariaDB with InnoDB

    Transactions, row-level locking and crash recovery, with the buffer pool sized to the plan.

  4. Storage

    NVMe disk

    Data files, redo logs and binary logs on fast local storage.

Worth knowing

  • MariaDB began as a fork of MySQL and stays largely compatible: most PHP apps work with either.
  • The two have diverged in newer versions, so test before switching an existing database.
  • Enable binary logs if you want point-in-time recovery or replication.
  • For remote connections, require TLS or use a private tunnel.
What you can run

What a Database VPS Is Used For

  • WordPress and WooCommerce databases

    Move a large store database off the web server.

  • Laravel, PHP and Python back ends

    One database server shared by several application servers.

  • Read replicas

    A second VPS replicating from the primary to take reporting queries.

  • Analytics and reporting

    Heavy reports run against a replica instead of the live database.

  • Development and staging

    Shared databases for your team, separate from production.

  • Software tied to a version

    Applications certified for a particular MySQL or MariaDB release.

VPS Plans

VPS Plans for MySQL and MariaDB

Choose by RAM and disk: the buffer pool should hold your hot data. VPS-2 or VPS-3 suit most production databases; VPS-4 adds 24 GB RAM and 200 GB NVMe.

VPS-1

Small websites, APIs, bots and development servers.

₹1,008 /mo
Get Started
  • 2 vCores
  • 4 GB RAM
  • 40 GB NVMe
  • 500 Mbps
  • Full root and SSH access
  • Free initial stack installation
  • Server hardening and firewall setup
  • Daily backup of the previous 24 hours
  • Unlimited traffic *
  • Anti-DDoS protection
  • Dedicated IPv4 and IPv6
  • KVM virtualisation
Most Popular

VPS-2

Production apps, WordPress and online stores.

₹1,906 /mo
Get Started
  • 4 vCores
  • 8 GB RAM
  • 75 GB NVMe
  • 1 Gbps
  • Full root and SSH access
  • Free initial stack installation
  • Server hardening and firewall setup
  • Daily backup of the previous 24 hours
  • Unlimited traffic *
  • Anti-DDoS protection
  • Dedicated IPv4 and IPv6
  • KVM virtualisation

VPS-3

Busy stores, SaaS products and several projects.

₹2,748 /mo
Get Started
  • 6 vCores
  • 12 GB RAM
  • 100 GB NVMe
  • 2 Gbps
  • Full root and SSH access
  • Free initial stack installation
  • Server hardening and firewall setup
  • Daily backup of the previous 24 hours
  • Unlimited traffic *
  • Anti-DDoS protection
  • Dedicated IPv4 and IPv6
  • KVM virtualisation

VPS-4

High-traffic apps, large databases and agencies.

₹5,274 /mo
Get Started
  • 8 vCores
  • 24 GB RAM
  • 200 GB NVMe
  • 3 Gbps
  • Full root and SSH access
  • Free initial stack installation
  • Server hardening and firewall setup
  • Daily backup of the previous 24 hours
  • Unlimited traffic *
  • Anti-DDoS protection
  • Dedicated IPv4 and IPv6
  • KVM virtualisation

* Unlimited traffic in Europe and North America. In Mumbai, Singapore and Sydney a monthly allowance applies (VPS-1 500 GB, VPS-2/VPS-3 1 TB, VPS-4 3 TB), then speed is limited to 10 Mbps until the next month.

Sizing guide

Which Plan for Your Database Server

Size by the data you use most: the InnoDB buffer pool should hold it, with room left for connections and the OS.

Recommended VPS plan for each MySQL & MariaDB workload
Workload Start with Why
Small app or staging database VPS-1 2 vCores · 4 GB RAM A buffer pool of about 2.5 GB.
Production store or app database VPS-2 4 vCores · 8 GB RAM About 5–6 GB of buffer pool.
Busy database or reporting replica VPS-3 6 vCores · 12 GB RAM About 8–9 GB of buffer pool and 6 vCores.
Large database VPS-4 8 vCores · 24 GB RAM Up to about 16–18 GB of buffer pool and 200 GB NVMe.

A starting point, not a limit: every plan upgrades in place, keeping your data, IP address and configuration.

Shared, Managed or Your Own Database Server?

Three ways to run MySQL or MariaDB, and what each gives you.

Feature Shared hosting database Managed database service Database VPS
Resources Shared with other accounts Dedicated, priced by tier Reserved, flat price
my.cnf settings None Limited parameters Full
Remote connections Often blocked Yes Yes, from IPs you choose
Replication No Managed replicas Configure your own
Administration The host The provider You, after our free setup
Explore Shared hosting database See Plans
After handover

First Steps on Your Database Server

Typical first tasks after handover: a database for an app server, access and backups.

  1. Create a database and user

    The user may connect only from your app server.

  2. Open the port to that server

    Everyone else stays blocked.

  3. Find slow queries

    Turn on the slow query log, then read it.

  4. Back up

    A consistent dump without locking InnoDB tables.

# 1. Create a database and user

sudo mysql -e "CREATE DATABASE shop; CREATE USER 'shop'@'203.0.113.10' IDENTIFIED BY 'change-me'; GRANT ALL ON shop.* TO 'shop'@'203.0.113.10';"

# 2. Open the port to that server

sudo ufw allow from 203.0.113.10 to any port 3306 proto tcp

# 3. Find slow queries

sudo mysql -e "SET GLOBAL slow_query_log = 1; SET GLOBAL long_query_time = 1;"

# 4. Back up

sudo mysqldump --single-transaction --routines shop | gzip > ~/backups/shop-$(date +%F).sql.gz

Example shell commands; adjust paths, names and versions to your project.

Example commands; adjust names, paths and versions to your project. Deploying and maintaining your application is yours to do (or ask us for a quote).

Free one-time setup

Installed and Secured Before You Log In

The VPS is unmanaged: after handover the server is yours to run. Before that, our engineers do the first setup once, free, so you start from a hardened server with MySQL & MariaDB in place.

  1. Choose a plan and location

    Pick the resources you need and the datacentre closest to your users.

  2. Tell us your MySQL & MariaDB setup

    Versions, database and domain: at order or right after.

  3. We install and secure it

    Server hardened, MySQL & MariaDB installed and tested, HTTPS on your domain.

  4. You take over with root

    SSH access to a working server, ready for your code and data.

Your database server

  • MySQL or MariaDB from the OS or the vendor's repository
  • Insecure defaults removed: no anonymous users, no remote root
  • InnoDB buffer pool sized for your plan
  • A database and user for each application you name
  • Port 3306 open only to your app servers

Yours to run after handover

  • Ongoing server administration
  • Application maintenance and updates
  • Debugging your code
  • Migrating existing sites or data

Not included in the free setup, but we can quote for it. No control panel by default: CloudPanel, HestiaCP or Virtualmin on request at no cost; cPanel and Plesk need their own licence.

Under the hood

Platform Specs and Locations

The same KVM platform on every plan; only the CPU, RAM, storage and port speed change.

VPS platform specifications
Virtualisation KVM with reserved vCores and RAM
Storage NVMe SSD on every plan
Network Dedicated IPv4 and IPv6, 500 Mbps to 3 Gbps per plan
Operating systems Ubuntu 26.04, 24.04 and 22.04 LTS · Debian 13, 12 and 11 · AlmaLinux · Rocky Linux · Fedora · FreeBSD
Access Full root over SSH, key-based login
Backups Automatic daily backup of the previous 24 hours; snapshots and longer retention on request
Protection Always-on anti-DDoS mitigation
Availability 99.9% uptime SLA

Secured before we hand it over

  • Non-root sudo user created for daily work
  • SSH key login, password login for root disabled
  • Firewall (UFW) open only for the ports you use
  • Fail2ban blocking repeated login attempts
  • Automatic security updates enabled
  • Free Let's Encrypt SSL on your domain
  • Timezone, swap and hostname configured

Asia-Pacific

  • Mumbai
  • Singapore
  • Sydney

Europe

  • London
  • Limburg
  • Roubaix
  • Gravelines
  • Strasbourg
  • Milan
  • Warsaw

North America

  • Beauharnois

Availability per location changes with demand; we confirm your location before setup. In Mumbai, Singapore and Sydney each plan includes a monthly traffic allowance (VPS-1 500 GB, VPS-2 and VPS-3 1 TB, VPS-4 3 TB); beyond it, speed is limited to 10 Mbps until the next month.

Who it's for

Who a Database VPS Suits

  • Sites outgrowing shared databases

    Stores and apps hitting connection or query limits on shared hosting.

  • Teams splitting app and database

    You want the database on its own server, sized separately.

  • Developers with specific needs

    Particular versions, replication or settings a managed service will not give you.

Running it well

Security and Performance for MySQL and MariaDB

Security

  • Remove anonymous users and remote root login; use a named admin account.
  • Grant each application only the privileges and hosts it needs.
  • Keep port 3306 closed to the internet except for known IPs.
  • Use TLS for connections between servers.

Performance

  • On a server that only runs the database, the buffer pool often gets 60–75% of RAM.
  • Enable the slow query log and add indexes for the queries it lists.
  • Size max_connections to what your apps use; each connection costs memory.
  • Keep tables on InnoDB; MyISAM has no crash recovery or row-level locking.
MySQL & MariaDB VPS FAQs

Questions Before You Deploy

Not covered here? Ask an engineer before you order.

Give Your Database Its Own Server

Pick a plan sized for your data. We hand over MySQL or MariaDB installed, secured and open only to your apps.

Deploy Your VPS Talk to an Engineer