Data Browser and Queries
Explore schemas, run SQL, inspect Redis keys, and import or export whole databases.
Look inside a database without installing a client or opening a tunnel. Every request runs as a job on the server that hosts or reaches the database, and results come back to the dashboard.
Explore
Browse what is in an instance, level by level:
Run SQL
The query editor runs SQL against a chosen database. Queries are read-only by default: PostgreSQL, MySQL and MariaDB run them in a read-only transaction, so an accidental UPDATE is rejected by the database itself.
Turn off read-only to make changes. Every query is recorded in the audit log as read-only or read-write with a fingerprint of the SQL rather than the SQL itself, which may contain secrets. SQL reaches the database client on stdin, never on a command line.
Import and export
The Import & Export tab of a PostgreSQL, MySQL or MariaDB instance moves whole databases in and out, without SSH.
Files pass through the control plane encrypted (AES-GCM) and are deleted after a day, or as soon as an import finishes. Exports and downloads are audited. On PostgreSQL, imported tables belong to the database's owner, so an app's own login can use them.
Move a database into VPSPilot
- Connect the existing database (host
127.0.0.1if it's on the same server) and Export it. - Create a managed instance, then Attach it to the app: this creates the app's database, login and
DATABASE_URL. - On the managed instance, Import the file into the app's database, then deploy the app.
Do it at a quiet time: writes to the old database after the export aren't copied.
Redis
For Redis instances the browser speaks Redis instead of SQL:
- info: memory, clients, keyspace and persistence.
- scan: iterate keys matching a pattern, 100 at a time by default.
- get: show a key’s type, TTL and value.
- delete: remove a key.