Overview
Your database's main dashboard for a quick health check without digging through settings.
Quick Status Check
At the top, you'll see your database's name and status at a glance. The info card shows eight fields in a grid:
| Field | Description |
|---|---|
| Status | Whether your database is Running, Provisioning, Failed, or another state. Green means everything's good. |
| Database | The type and version. |
| Containers | How many container instances are running. |
| Instance Size | The name of your instance tier. |
| Region | Where your database is deployed. |
| Type | Standalone for single instances or Replicaset for high-availability across multiple nodes. |
| Storage | How much disk space is allocated. |
| Instance Details | The actual resource specs for your instance. |
Credentials
Your database connection details appear in the Credentials section below the info card.
Admin User Is for Administration Only
The admin user is a SUPER user and should only be used for administrative actions, not in applications. Create application-specific users with access to specific databases for your app connections.
Each credential field has two icons on the right: an eye icon to reveal the value, and a copy icon to copy it directly to your clipboard without revealing it.
- Username: Your admin username, masked by default.
- Password: Your initial admin password, masked by default.
- Connection String: The complete connection URL. The format varies by database type (e.g.,
mongodb://...,postgres://...,redis://...).
After Changing Your Database Password
For all database types, connect directly to the database to change a password. The Galaxy dashboard doesn't offer password changes or resets. It always displays the initial password and doesn't sync password changes made in the database.
If you've changed the password, use the new one in your applications and database clients, including any connection strings you copied from the dashboard.
Change a Database Password
Choose your database below. You'll need the current credentials and a database client that can connect directly to your instance.
Use TLS When Changing MongoDB Passwords
Use a TLS connection for this operation. The password prompt keeps the new password out of the command, but doesn't encrypt the connection.
Connect and Select the User's Database
Connect with mongosh using your current credentials. Select the database where the user was created. For the admin user shown in the dashboard, this is admin; application users may belong to a different database.
Replace YOUR_AUTH_DATABASE with that database's name:
use YOUR_AUTH_DATABASEEnter the New Password
Replace YOUR_USERNAME with the user whose password you want to change, then run:
db.changeUserPassword("YOUR_USERNAME", passwordPrompt())Enter the new password when prompted. Your account needs permission to change that user's password. changeOwnPassword allows changing your own password; changePassword on that database allows changing any user's password.
See MongoDB's password-change reference and user-management privileges for details.
Connect as the User
Connect with psql using the current credentials of the user whose password you want to change.
Enter the New Password
At the psql prompt, run:
\passwordEnter and confirm the new password when prompted. This changes the connected user's password without putting the new password in an SQL statement or command history.
See PostgreSQL's \password reference for details. To change another user's password, check the role-permission requirements first.
Redis ACL users can have multiple passwords. Adding a new password doesn't revoke the old one, and saving ACL changes depends on the server's configuration. Follow the procedure confirmed for your instance rather than applying a generic Redis password command.
See Redis's ACL guide, including how ACLs are saved, for the underlying behavior.
Once you've changed the password and updated your applications and clients, open a new connection with the new credentials to check that you can sign in.
What's Next?
Databases Menu
Manage all your hosted databases in one place. MongoDB, PostgreSQL, or Redis, everything lives here. Your databases and apps work together seamlessly.
Metrics
The Metrics section shows real-time and historical performance data for your database. Watch CPU, memory, connections, disk usage, and network activity to understand how your database is performing.