1. DBeard
  2. Databases
  3. PostgreSQL

PostgreSQL GUI clientstable

Browse PostgreSQL and review changes

Explore schemas, run SQL and inspect the server from a native desktop client.

macOS first, with Linux to follow early. Windows is planned.

Tested against PostgreSQL 17. Dump and schema diff require PostgreSQL 12 or later. Remote SSH, most real-server mutual TLS paths and cloud IAM sign-in still need verification.

The DBeard mascot sails a boat with the PostgreSQL elephant on the flag.
Verified server
PostgreSQL 17
Schema diff and dump
PostgreSQL 12 or later
First desktop release
macOS for Apple Silicon and Intel

The lay of the land

Everything Postgres keeps, where Postgres keeps it

DBeard lists each object at the level the engine scopes it, so the sidebar matches what you would see from the engine’s own catalog.

postgres://app@db.example.com:5432/orders?sslmode=verify-full
  • Paste a PostgreSQL URL or enter the host, port, database and user in the connection form. Enter the password separately for system credential storage.
  • Use TLS with hostname verification. Add a CA, client certificate or key when the server requires one.
  • Connect through SSH with system keys, agent and configuration. Jump hosts were tested through a local SSH server.
  • Cloud IAM sign-in and Kerberos are implemented. Live paths have separate verification caveats.
  1. Database connectionThe connection opens one database.
  2. Schema folderShown when the catalog spans multiple schemas. The default schema starts expanded.
  3. Tables and viewsTables come first. A single-schema catalog lists Tables and Views directly under the connection.
  4. Child partitionsEach partition nests directly under its parent and can contain further partitions.
  5. Partition columns
  6. Columns
  7. Schema object groupsFunctions, procedures, sequences, types, domains, and composite and range types. Expand a group to see its objects.
  8. Database-wide object groupsExtensions, publications, subscriptions, foreign data wrappers, servers and user mappings appear at database scope.

Made for Postgres

What you get on this engine

  1. Your whole schema, in view

    Browse schemas, domains, composite and range types, partitions and row-level security policies.

  2. Review edits before applying

    Stage row edits, inspect their SQL and apply them together. Conflict checks refuse a row that someone else changed.

  3. Look after the server

    Use the LISTEN/NOTIFY console, client COPY, pg_stat_statements, vacuum and index-usage reports.

Demo coming soon
Browse PostgreSQL schemas and nested partitions.

Support

PostgreSQL features, one by one

“Coming soon” means it is on the roadmap. “Not planned” means we have decided against it.

Browse and edit
FeatureDBeard
Schema browsing and nested partitionsYes
Table and column completion in SQLYes
Follow foreign keysYes
SQL review and conflict checks for grid editsUses the primary key or ctid when the table has no primary key.Yes
Ask first and Read only connection policiesYes
Schema and administration
FeatureDBeard
Table designerYes
Schema diff and dumpRequires PostgreSQL 12 or later.Yes
LISTEN/NOTIFY console and client COPYYes
Query statistics and maintenance reportsQuery statistics require pg_stat_statements on the server.Yes
PL/pgSQL debuggerBeta. Requires pldbgapi and has yet to debug a live routine.Partial
Desktop availability
FeatureDBeard
macOSYes
Windows releaseComing soon
Linux releaseComing soon

PostgreSQL benchmarks

Benchmark results coming soon.

Ports of call

Hosted Postgres it connects to

ServiceStatusNotes
Self-hosted PostgreSQLTestedThe repo records local PostgreSQL 17 runs.
NeonShould workUse a PostgreSQL endpoint and its TLS settings. Live Neon access is unverified.
SupabaseShould workUse a PostgreSQL endpoint and check reachability from your network. Live Supabase access is unverified.
Amazon RDS and Aurora PostgreSQLShould workPassword access, discovery and IAM token support are implemented. Live provider verification is pending.
Google Cloud SQL for PostgreSQLShould workDiscovery and IAM token support are implemented. The instance must be reachable, and live provider verification is pending.
Google AlloyDBShould workCloud discovery fills a PostgreSQL connection draft. Verify endpoint access and credentials.
Azure Database for PostgreSQLShould workDiscovery and Entra sign-in are implemented. Live provider verification is pending.
TimescaleDBShould workThe extension workspace handles hypertables, chunks, jobs and policies. Real TimescaleDB lifecycle tests have not been run.
CockroachDBShould workUses distinct catalog and row identity rules over the PostgreSQL wire protocol. The repo records no real-server run.

On deck

Postgres in DBeard, up close

EXPLAIN (FORMAT JSON)
SELECT id, status, total
FROM sales.orders
WHERE id = 42;

The longer read

A PostgreSQL client worth switching to

Explore the database you are connected to

Open tables, follow foreign keys, and write queries with table and column name completion. DBeard uses a native Rust and GPUI interface on your Mac.

Each connection opens one PostgreSQL database. When objects span several schemas, the sidebar groups them by schema, with tables before views. Expand a partitioned table to find its children and inspect columns, policies and triggers on the relevant relation. Functions, sequences and user-defined types have their own groups. Roles are available from Administration › Users and roles.

Review a change before applying it

Stage a grid edit to inspect the SQL and apply several changes together. DBeard identifies a row by its primary key, or by PostgreSQL’s ctid where there is no primary key. If the row no longer matches the values originally read, the conflict check refuses the edit. Choose Ask first or Read only for a connection when you need an extra guard. The PL/pgSQL debugger is beta and requires the server’s pldbgapi extension. Live routine debugging remains unverified.

Inspect slow queries and plan schema work

Open the query plan for a selective lookup to see which scan PostgreSQL chose. In Administration, use the index-usage and vacuum reports to investigate a table, or open query statistics on a server that has pg_stat_statements enabled. The LISTEN/NOTIFY console is useful for checking that an application publishes to the channel you expect. Use the dedicated client COPY workflow when loading a file.

Compare schemas before applying a migration and review generated DDL against a disposable database. Dump and schema comparison require PostgreSQL 12 or later. PostgreSQL 17 is the version recorded in the repo’s real-server verification.

Set up a managed connection

Start with the provider’s hostname, port, database and user. For TLS identity checking, select verify-full and supply a CA if the provider uses a private one. Enter credentials separately. If the database is reachable only from a private network, check network access and any SSH routing before testing with a read-only role. The provider list shows where live verification is still pending. The download page lists available builds by platform.

Questions

Postgres and DBeard, answered

Is DBeard a PostgreSQL GUI client for Mac?

Yes. The native Mac app opens PostgreSQL connections, browses schemas, runs queries and stages grid edits so you can review the SQL before applying changes.

Does DBeard run on Windows or Linux?

macOS is first, with Linux to follow early. Windows is planned. The download page shows which builds are available.

Which PostgreSQL versions are supported?

PostgreSQL 17 is verified. Schema diff and dump require PostgreSQL 12 or later. Browsing and the table designer remain available on PostgreSQL 10 and 11.

Can I connect to Neon, Supabase or Amazon RDS?

Expect a reachable PostgreSQL endpoint with appropriate credentials and TLS settings. Live verification on those providers is pending. RDS IAM sign-in is implemented and has separate testing caveats.

Can I compare schemas and make backups?

Yes. DBeard includes table design, schema diff and dump tools. Dump and diff require PostgreSQL 12 or later.

Can I browse PostgreSQL without writing data?

Use a least-privilege database role and set the connection to Read only. DBeard applies PostgreSQL’s session-level read-only protection alongside its own checks.

Open your Postgres database in DBeard.

Free for one connection at a time, with every feature. No account, and your data stays on your machine.