Creating a database#
The Databases tab gives your server a database to work with. A lot of plugins rely on one to store player data, economy balances, and other state that needs to survive a restart, so this is usually one of the first things you set up when a plugin asks for database credentials. The tab description sums it up: create and manage databases, configure access, and view connection details.
To make one, click New Database in the top right. That
opens the Create new database dialog. The first field is
Database Name, which has to be 3 to 48 characters and can
use letters, numbers, dashes, dots, and underscores. The second is
Connections From, which controls where connections are
allowed to come from. Leave it blank and it defaults to
%, meaning any host can connect. When you're happy, click
Create Database.
Some servers offer more than one engine. When they do, the dialog adds
a Database Type dropdown where you pick between
MariaDB and Valkey (Redis). Most servers only
offer MariaDB, in which case the dropdown is hidden and that type is
used automatically. The Valkey option does not ask for a connections
host, since it works a little differently.
yourname becomes something like s12_yourname.
That full prefixed name is the one you put in your plugin configs, and
it's shown at the top of the database's card once it's created.Connection details#
Every database appears as a card in the list. The card shows a type
badge (MariaDB or Valkey (Redis)) next to the
name, then the endpoint, the From value you set, and the
username at a glance, and you can click any of those to copy it. For
the full set of credentials, click Details to open the
Database connection details dialog.
For a MariaDB database the dialog lays out the database name, the
Endpoint, the Connections From value, the
Username, and the Password, each in a field
you can click to copy. The username is generated for you when the
database is created, so you don't choose it yourself. The endpoint
already includes the host and port your plugin needs to reach the
server. Both the password and the JDBC string are masked behind dots by
default, with a Show / Hide toggle beside each
so you can reveal them when you need to.
At the bottom of the dialog there's a ready-made
JDBC Connection String you can paste straight into a
config. It follows this form, with the real username and password
baked in:
jdbc:mysql://username:password@endpoint/databaseThe Show toggle on the password and the one on the JDBC
string reveal both at once, since the string already contains the
password. Below the fields a small line reminds you that you can click
any field to copy its value.
Whether a teammate can see the password and the JDBC string depends on the role you've given them. The endpoint, username, and connections from value are visible to anyone who can open the dialog, but the password is gated behind its own permission. See users and permissions for how access works.
Host, Port, Username,
Password, and Key Prefix. There's no JDBC
string for Valkey, since it isn't an SQL database.Managing your data in the browser#
For MariaDB databases the card has a Manage (MariaDB)
button. Clicking it opens a web-based database manager in a new tab,
where you can browse tables, run queries, and inspect rows without
installing anything locally. The button reads Opening...
while it spins up, then the manager loads in its own tab.
The manager opens in a popup tab, so if nothing happens, check that your browser isn't blocking popups for the panel and try again. This button is only shown for MariaDB databases and only to teammates whose role lets them view the password.
Rotating the password#
If a password leaks, or you just want a fresh one, you can rotate it
from inside the Database connection details dialog. The
rotate button sits to the right of the password field, and clicking it
generates a new password right away.
Because the change is immediate, any plugin still using the old password will fail to connect until you update it. Copy the new password (or the updated JDBC string, which changes to match) into your plugin configs as soon as you've rotated, then restart the plugin or server so it picks up the new credentials.
Deleting a database#
To remove a database, click Delete on its card. This opens
the Confirm database deletion dialog, which spells out that
the action is permanent, cannot be undone, and removes all of the data
inside. Back up anything you want to keep before you go ahead.
The dialog asks you to type the database name into the
Confirm Database Name field before the
Delete Database button turns on. You can enter either the
short name you originally chose or the full prefixed name shown on the
card.
Database limits and disabled databases#
How many databases you can create comes from your plan. The header
above the list shows where you stand: it reads "{count} of
{limit} databases" on a normal plan, or "{count} databases
(unlimited)" when there's no cap. Once you reach the limit, the
New Database button stops appearing until you free up a
slot or move to a bigger plan.
Before you create your first one, the page shows a friendly empty state
that reads No databases found with the line "Your server
does not have any databases. Create one to get started." Once a database
exists, that placeholder is replaced by the list of cards.
Some plans don't include any databases at all. On those, the header
shows Databases disabled in red, the
New Database button is hidden, and the empty state reads
Databases unavailable with a note that databases cannot be
created for this server. To get a database, switch to a plan that
includes one, and the button comes back as soon as your limit is above
zero.