GuidesOnly show guides for your app
GuidesGuidesCreate a managed MySQL, PostgreSQL, or MongoDB database from your server's Databases page — one that stays up even when your server doesn't.
Your server's files get wiped when you reinstall or switch to a different application — but your data shouldn't have to go with them. A managed database is storage that lives on a separate, always-on host, so your bot's scores, your app's users, and anything else worth keeping survive whatever happens to the server. This guide creates one in a couple of clicks.
| At a glance | |
|---|---|
| You need | Any Falix server — the database is part of your server, nothing extra to sign up for |
| Plan | Any |
| Time | Five minutes |
s{serverId}_yourname and generates a username shaped like u{serverId}_random — the prefixes keep your database from clashing with anyone else's.🎯 Good to know: You can create up to 20 databases per server (the exact number depends on your plan; free servers get up to 5). Most projects only ever need one.
For a MySQL database the form also has a Remote Access field. Leave it at % — the default — to allow connections from anywhere, which is what you want when your app runs on a different server. Set a specific IP address or hostname instead to lock the database down to one source. PostgreSQL and MongoDB don't show this field.
Open the database you just made and the page shows everything a program needs to connect:
| Field | What it is |
|---|---|
| Host and port | The address of the shared database host — not your server's own address |
| Username and password | The panel generates a strong password for you; you never type one in, and can rotate it if it ever leaks |
| Connection string | A ready-made line that packs all of the above into one |
The format depends on the type:
mysql://user:pass@host:port/dbname
postgresql://user:pass@host:port/dbname
mongodb://user:pass@host:port/dbname?authSource=dbname
Copy the string for your database — it's the fastest way to point code at it. Wiring it into an actual app is the next guide: Connect your app to a database.
For a MySQL database, the page also has a phpMyAdmin button. That opens a full web interface where you can browse tables, run SQL, and import or export data by hand — handy for a quick look without writing any code. (phpMyAdmin is MySQL-only; PostgreSQL and MongoDB don't get the button.)
This is the part worth understanding. A managed database runs on a shared database host that Falix keeps online — it is not running inside your server container. That has one big consequence:
So a managed database is the safest home for anything you can't afford to lose — a Discord bot's data, an app's user accounts, saved settings. Keep it there and a wiped server is a minor inconvenience instead of a disaster. (If you'd rather run a database engine inside your own server for caching or full control, see Run your own database server — but read the trade-offs there first.)
The Databases page also backs up individual databases, under Manual and Automatic tabs. A backup captures that database's contents so you can roll it back later; you can download, restore, or delete each one from the list. Take a manual one before anything risky — a schema change, a bulk delete, a migration.
⚠️ Heads up: The connection string contains your username and password in plain text — anyone who has it can read and change your data.
.env works on Falix.For MySQL, click phpMyAdmin, sign in with the username and password from the page, and you'll land on your (empty) database — proof it's live. For any type, seeing the database's host and port on the page means it's ready for an app to connect.
.env and restart the app right after.