Databases
In preview
MariaDB or MySQL, PostgreSQL and a Valkey instance per account, with three privilege levels that mean the same thing on every engine.
Built and lab-tested
- Databases and users named after the account, with read-only, read-write and admin privileges on both engines.
- Generated passwords are shown once. Optionally keep them in the vault and reveal them later; every reveal is audited.
- Remote access per user for IPv4 or IPv6 addresses and ranges, with TLS required. The engine listens on loopback only until someone needs remote access.
- Size quotas: a database over its quota becomes read-only until it fits again. Connection limits per user.
- Export and import of
.sqland.sql.gz - Valkey per account: runs as the account inside its slice, with its own ACL user, a memory cap and dangerous commands denied.
- Your own external database servers, managed through the same actions.
- A full database tool (Adminer) on each database, opened from the panel as one of its users with no password to type. It runs as your account without network, in its own browser tab (not made for a phone), covers MariaDB, MySQL and PostgreSQL on the server itself, and ends when you sign out or stop using it.
- Scheduled dumps per database, restore to a new database by default, a query console, and a slow-query list with an Explain button.
Not there yet
- Point-in-time recovery.
Every action in this area is in the panel, one keystroke away in the command palette (Ctrl K), on the command line and in the API, and most changes can be previewed as a plan first. Built and tested in our lab; RespireCloud is not released yet.
