Databases

The Databases tab on a server lets you create databases and users on the database engine already installed there, without remembering client syntax.

CloudPilot does not install a database engine for you, and it does not run one of its own. It talks to what is on the machine.

Signing in to the engine#

Some engines — MySQL in particular — refuse socket authentication for the user the agent runs as. When that happens, CloudPilot asks you for a database username and password.

Those credentials are not stored anywhere. They are held in the browser tab you typed them into and attached to each request you make. Close the tab, reload, or come back tomorrow, and CloudPilot will ask again.

That is a deliberate trade. It means:

• Your database root password is never written to CloudPilot's database, so a compromise of the panel does not hand over your data.
• You will re-enter it each session. There is no "remember me" for this.

Creating a database#

1. Open the server → Databases.
2. Pick the engine.
3. Create database, give it a name.
4. Create a user and grant it access to that database.

Use a dedicated user per application rather than pointing everything at root. If one application is compromised, the damage stops at its own data.

Connecting from your app#

Applications on the same server should connect over localhost or the local socket. That keeps the database off the network entirely, which is both faster and safer than exposing a port.

If something genuinely needs to connect from another machine, open the port to that machine's IP specifically — never to 0.0.0.0 — via the firewall.

Backups#

Creating a database does not back it up. Set up off-site backups pointed at storage you control, and restore from one at least once so you know it works.