Changelog

Every release. Updates arrive in the app through Sparkle.

0.1.3 23 Sep 2026

• Update checks now go to updates.uresk.net and include the app version and license state (trial, licensed, trial ended, or needs attention), which we count per day to see how many copies are in use. Nothing that identifies you is sent or stored; see the privacy page.

0.1.2 23 Sep 2026

• License problems are easier to fix: if a key stops validating, the License window says why and offers Try Again, and a key removed from this Mac in the customer portal is re-activated automatically when a slot is free.
• A brief license-server hiccup can no longer mark a paid license as invalid.
• When a paid license needs attention, Start, Stop, Restart and Open Client say so and point to the License window, instead of saying the trial has ended.
• Renewing updates is $9/year.

0.1.1 19 Sep 2026

• The popover works from the keyboard: arrows move through the services, Return opens the window on the one highlighted, ⌘C copies its connection string, ⌘R refreshes, Escape lets go. Rows are read out as buttons by VoiceOver.
• Stop checks that the process is still the one in the list before it signals it, and again before the forced kill five seconds later. A process id gets reused, the list can be half a minute old, and the wait is long enough for the service to exit and its id to go to something else.
• Passwords, tokens and keys in a service's log are hidden until you press Reveal credentials. A container's first-boot log prints POSTGRES_PASSWORD, and services log the URLs they connect to.
• Fixed: a service that accepted the connection and then sent nothing (Postgres in crash recovery, a published container port with nothing behind it, a stalled tunnel) stopped its health check from ever finishing, and every refresh after it. The dashboard kept showing the last state it had. Health checks now give up at their deadline whatever the other end does.
• Fixed: Open Client put a container's user, password and database name into the terminal command as they were, so a name containing quotes or a semicolon ran as shell commands. They are now passed as quoted arguments, and the connection URL is percent-encoded.
• The Client row and the command echoed in the terminal show the password masked. The command file Open Client writes is readable by you only.
• The HTTP health check reads at most 256 KB of a response.

0.1.0 16 Sep 2026

• Discovers PostgreSQL, Redis, MySQL and MariaDB, MongoDB, and anything a Docker-compatible runtime exposes, and detects Elasticsearch, OpenSearch, Kafka, RabbitMQ, Mailpit, LocalStack, Memcached, NATS, and MinIO when present.
• Attributes each service to its source: Homebrew (read from the launchd plists Homebrew installs), Docker Desktop, OrbStack, Colima, or Podman (through the engine API over the socket), Postgres.app, or a bare process. No brew or docker subprocesses.
• Protocol-level health probes: Redis PING, the Postgres startup handshake, the MySQL handshake packet, MongoDB buildInfo, HTTP for Elasticsearch, OpenSearch, Mailpit, LocalStack, and MinIO, the AMQP handshake for RabbitMQ, Memcached version. Latency and last-checked time; one connection, one message, then close; each probe can be turned off in Settings.
• Details per service: version, port and bind address, PID, uptime, memory, data directory, config file, log file with an in-app tail, and the Compose project or git repository that owns it.
• Copyable connection strings with passwords masked on screen; copied in full only when the password is the container's own default environment variable.
• Start, Stop, and Restart through brew services, the container API, or a signal. Open Client (psql, redis-cli, mysql, mongosh) in Terminal. Open Data Directory. Copy Summary for Slack.
• Menu bar icon with one dot per service: green answers, yellow listening but wrong or slow, red running but not answering.
• Stopped Homebrew services and exited containers are listed so they can be started.
• 14-day unrestricted trial; after it, viewing is free and actions need a license.
• Demo mode for screenshots.

Next

In this order: profiles (start and stop a named set of services together), conflict detection (two services on one port or one data directory, and which one to stop), and a wider catalog with data-directory and log heuristics for the services that are only detected today.