Sequel Ace

Sequel Ace is a free, open-source Mac graphical client for MySQL and MariaDB. Developers, database administrators and analysts can inspect schemas, browse and edit records, run SQL and import/export data. It is a successor to Sequel Pro, not a database server; a separately installed or remotely hosted database is required.

Features

• Browse table structure, content, relationships, triggers and table information.
• Run SQL queries, manage query favorites and inspect results.
• Edit records with inline controls or Record View.
• Filter content with AND/OR groups and search tables with fuzzy type-ahead.
• Import and export supported SQL, CSV and other data formats.
• Manage saved connections, tabs and connection colors.
• Connect with TCP/IP, supported local sockets, SSH tunnels, SSL/TLS or configured AWS IAM authentication.

The supported database family is MySQL/MariaDB, not a general PostgreSQL, SQLite or SQL Server client. SQLite references in internal release fixes concern application storage, not newly promised database-server support. Features depend on server version, authentication method and the user's database privileges.

Install and connect

Install with brew install --cask sequel-ace, or download the official GitHub release ZIP and move Sequel Ace.app into Applications. The publisher also distributes through the Mac App Store. The website describes Homebrew as an unofficial community-maintained cask of the GitHub release. App Store delivery uses an Apple account and store updates; direct GitHub delivery follows its own packaging/update path. Do not confuse release metadata or overwrite one distribution unintentionally.

Create a connection using the host, port, database username and appropriate authentication details supplied by the server administrator. Confirm which server and database you are connected to before executing queries or editing data. Use a narrowly privileged account and a test database for unfamiliar operations. Imports, edits, schema changes and many queries can change server data immediately; an export alone is not proof of a complete restorable backup. Back up important data and test restoration separately.

The captured cask lists no additional formula dependency or explicit conflicting cask. MySQL/MariaDB is a runtime service requirement, not a database server installed by this cask. Sequel Pro can coexist, but connection migration and stored credentials should be reviewed; historical saved-connection files do not automatically guarantee compatible sandbox access.

TLS, SSH, files and credentials

Prefer a properly configured TLS connection or SSH tunnel for remote databases instead of plain TCP. Supply trusted certificate material and follow your administrator's verification requirements. SSH authentication may need a private key and passphrase, with the correct SSH host/user and database endpoint as seen from that host. Keep private keys private, verify host identity and grant access only to the required files. SSH access and database authentication are separate permissions.

Sequel Ace is sandboxed. Use the application's file selectors/authorization controls for SSH keys, certificates, imports/exports and optional AWS configuration folders. Full Disk Access does not bypass the documented socket sandbox restriction: a socket outside the container may be inaccessible, and a /tmp symlink alone is insufficient. Consult the official local-connection guide or use an appropriate TCP connection. On systems requesting Local Network permission, grant it when connecting to intended local servers; not every connection failure is a denied-permission error.

AWS IAM requires a configured RDS/Aurora account, enabled IAM database authentication and authorized credentials; it uses TLS and short-lived tokens. It is optional, and ordinary MySQL/MariaDB connections do not require an AWS account. The client does not create arbitrary SSM sessions or network tunnels for you. Saving connections or credentials requires attention to the app's Keychain and file-access behavior; avoid exposing them in exports, screenshots or shared connection URLs.

System and versions

Current Sequel Ace 6 documentation requires macOS Ventura 13.5 or later, Intel or Apple Silicon, MySQL 5.7+ or MariaDB 10.0+. The captured cask's coarse macOS 13 requirement should not override the publisher's more precise 13.5 minimum. Older macOS systems need the last compatible historical release listed by the project. Windows/Linux database servers can be remote targets, but this graphical application is for macOS.

The current recorded release is 6.0.2 build 20115. The records 6.0.2,20115 and 6.0.2 refer to the same release, as do 6.0.1,20114 and 6.0.1. The latest three distinct releases are 6.0.2, 6.0.1 and 6.0.0. Official GitHub API metadata currently marks production/6.0.2-20115 as a non-prerelease; an older cached page still called it Release Candidate 1, so the precise tag/build and fresh metadata matter.

The official 6.0.2 Mac ZIP is 21,784,147 bytes, verified by HTTP HEAD without downloading the application archive. Installed usage, exports and database backups need additional storage. Database operations require access to the server; this is not an offline substitute for a running database. Keep the app current and review authentication, server and import/export compatibility after updates.

Cost and license

Sequel Ace is free under the MIT license, with separate licenses for bundled components. No Sequel Ace subscription or universal client account is required for basic use. Database hosting, cloud providers, SSH infrastructure and organizational services can require their own accounts and charges. App Store installation can require an Apple account. The client sends queries and data to the server you choose; encryption and the server operator's policies determine that connection's privacy properties.

Sources: Official requirements and installation, Connections, Remote connections, Official repository and releases, MIT license.