What it does not do

Limits

• There is no Windows build. macOS and Linux are the supported platforms, and Windows is out of scope.
• There is no Intel macOS build. The macOS package is Apple Silicon only. An Intel install is told that updates are not published for it.
• The supported engines are PostgreSQL, CockroachDB, MySQL, MariaDB, TiDB, Microsoft SQL Server, ClickHouse, Snowflake, SQLite, Google BigQuery, Oracle Database, Redis, Valkey, Apache Cassandra, ScyllaDB and MongoDB. There is no DuckDB support.
• There is no restore button for a database snapshot. The finished job shows the exact command that replays the file, and switches to pg_restore for a custom-format archive.
• Snapshots cannot be resumed, scheduled or encrypted, and are not split into volumes. A snapshot is a transaction, so an interrupted one is restarted rather than continued.
• Bucket backups never run on their own. A saved backup runs when you start it. There is no scheduler and nothing runs in the background.
• Connections do not sync between computers. Export an encrypted connection file and import it on the other computer.
• There is no telemetry and no crash reporting.
• The AppImage may fail on Mesa 25 or newer. The Debian package is the primary Linux package and is unaffected.
• Without a license, the app allows one saved database connection and one saved file connection.
• There is no plugin system, no chat assistant, no charts or dashboards, and no database user or role management.
• Cross-server file transfers relay through the app rather than being pushed server to server. A server-side push would depend on agent forwarding, host-key state on the source server and tools installed on the far side.