LoafDB is the managed database feature built into the Loafhosts panel. Plenty of game servers, web apps, bots, and plugins need a real database behind them — a place to keep player data, economy balances, web content, or stats — and LoafDB gives you one without ever leaving the panel. It supports three engines (MySQL, MariaDB, and PostgreSQL), and on top of plain database creation it adds a full table and row browser, a typed table builder, a scoped SQL console, and import/export. Whether you searched for game server database hosting, how to create a MySQL database, PostgreSQL hosting, or just “where are my server’s databases”, this guide walks through everything LoafDB actually does and how to use it on a server you host with Loafhosts.
What LoafDB Is
LoafDB replaces the old, bare MySQL-only database tab with a multi-engine, fully managed experience. It is not tied to any one game — every server that comes with a database allowance gets it, so the same tools work whether you run Minecraft, a Rust server, a Discord bot, or a web application. You manage your databases directly from the panel: create them, view their connection details, browse and edit their contents, and back them up, all in one place. Behind the scenes every database gets its own dedicated user whose access is scoped to that one database, and all stored credentials are encrypted at rest.
Note: LoafDB supports three engines — MySQL, MariaDB, and PostgreSQL
Note: It is available on any server that includes a database allowance, regardless of game
Note: Each database you create gets its own isolated user — it can never touch another customer’s data
Finding Your Databases
Open the server you want to work with in the panel, then go to the Databases page in the server’s sidebar. This is the same Databases area you may already know, upgraded with the LoafDB tools. It lists every database attached to the server, shows how many you have used against your plan’s allowance, and is where you create new ones and open the management tools for the ones you already have.
Tip: Your database allowance comes from your plan — the Databases page shows how many you have used and how many remain
Tip: If the Databases page says databases are not enabled, your plan does not include a database allowance — contact support or upgrade
Creating a Database
To make a new database, open the New database dialog, give the database a name, and create it. If your host offers more than one engine or database host you pick which one to use; if only one is available it is selected for you automatically. The name must be 1 to 48 characters made of letters, digits, or underscores. You do not need to invent a username or password — the panel generates a unique, namespaced database name, a dedicated username, and a strong random password for you. Once it is created, the new database appears in the grid with its connection details on its card.
Creation is limited by your plan’s database allowance, and there is a hard ceiling of 50 databases per server regardless of plan.
Note: You only pick a short name (and an engine or host if more than one is offered) — the username, password, and final database name are generated for you
Tip: The password appears on the database’s card if you have permission to view it — copy it somewhere safe, and you can rotate it later from the panel
Note: The database name you type is automatically prefixed so it stays unique to your server — the full name is shown in the connection details
Your Connection Details
Each database’s card lists the engine, the host, the port, the database name, and the username — everything an application needs to connect. The password is shown on the card too if you have permission to view it. Point your game server, plugin, bot, or app at those values and you are connected. If you ever need a fresh password — for example after sharing access or rotating credentials — you can rotate it from the panel, and the new password is shown to you once when you rotate.
By default, your database user is confined to the hosts that legitimately need it (the Loafhosts panel and your server’s node), rather than being thrown open to the entire internet. That keeps your data reachable by your own server and the management tools while staying off the public web, unless your host has deliberately configured the database host to accept connections from anywhere.
Tip: Use the exact host and port shown in the panel — they point at the managed database host, not your game server’s IP
Note: Rotating the password immediately invalidates the old one, so update your application’s config at the same time
Note: By default the database is not exposed to the open internet — it is reachable by your server and the panel tools
Browsing Tables and Rows
You do not need an external tool like phpMyAdmin or Adminer to look inside your database. LoafDB has a built-in browser: it lists the tables in your database alongside each table’s size, and lets you open any table to page through its rows. Rows are shown a page at a time, with Prev and Next controls to move between pages.
Tip: The database size shown on the page is cached for fast loading, so it may lag a few seconds behind a large import or delete
Editing Data and Building Tables
The browser is read-and-write. You can insert a new row, edit the values in an existing row, or delete a row — each edit is matched against the row’s primary key so you only ever change the row you meant to. LoafDB also includes a typed table builder so you can create a new table without writing SQL: you name each column and pick its type from a supported list — including INT, BIGINT, SMALLINT, TINYINT, DECIMAL, FLOAT, DOUBLE, BOOLEAN, VARCHAR, CHAR, TEXT, MEDIUMTEXT, LONGTEXT, DATE, DATETIME, TIMESTAMP, TIME, JSON, and BLOB — and set options like length, whether it is a primary key, and whether it auto-increments. You can also drop a whole table from the browser.
Note: Row edits and deletes are keyed on the primary key, so they target a single row precisely
Tip: The table builder covers the common column types — for anything more specialized, use the SQL console
Note: Dropping a table is permanent — export a backup first if you are unsure
The Scoped SQL Console
When you want to run SQL directly, open the console and type your statement. This is the headline safety feature of LoafDB: the console connects to your database as that database’s own scoped user, so it physically cannot reach any other database on the host — the database engine itself rejects anything outside your own database. You run one statement at a time. There is a size limit on a single statement, and result sets are capped, with a clear indicator when the output was truncated. SELECT, SHOW, DESCRIBE, EXPLAIN and similar read-only queries are treated as reads; anything that changes data or structure is treated as a write. The console also shows how long each statement took and how many rows it returned or affected, and if the engine rejects your statement the error is shown so you can fix it.
Note: The console can only ever touch your own database — that boundary is enforced by the database engine, not a filter that could be tricked
Tip: Run one statement at a time; the console rejects stacked, semicolon-separated statements
Tip: If a big SELECT comes back marked as truncated, add a tighter WHERE clause or a LIMIT
Importing and Exporting
LoafDB can back up and restore your database from the panel. Export downloads a SQL dump of your whole database, which you can optionally compress as a gzip file. Import goes the other way: upload a SQL file and LoafDB loads it into your database. The import must be a plain, uncompressed .sql text file — compressed archives (gzip, zip, and similar) are rejected, so decompress a dump before uploading it.
Note: Export can produce a gzip-compressed file, but import expects a plain
.sqlfile — unzip a compressed dump before importing itTip: Take an export before any big change — a mass delete, a schema edit, or an import — so you always have a restore point
Note: Both import and export run as your database’s scoped user, so they only ever read or write your own database
Sharing Access With Your Team
If you add sub-users to your server, what each one can do with databases is controlled by per-action permissions: viewing databases and their contents, creating new ones, modifying data and structure, deleting, and revealing the password. That means you can give a teammate read-only access to browse and export without letting them drop tables or see the password, or hand a developer full control while keeping a helper limited to viewing.
Tip: Grant the “view password” permission separately — a teammate can browse and edit data without ever seeing the connection password
Note: Database permissions follow the same sub-user system as the rest of your server, so you manage them from the server’s user settings
Wrapping Up
LoafDB turns the panel’s Databases page into a complete database workbench: create MySQL, MariaDB, or PostgreSQL databases in a couple of clicks, get ready-to-use connection details, browse and edit your data, build tables without writing SQL, run a console that is locked to your own database, and import or export backups — all without a separate tool and all scoped tightly to your server. Whenever your game server, plugin, bot, or app needs a database, the Databases page on your Loafhosts server is where you start.