DockView

Checking whether a service actually wrote a row is a five second question that takes five minutes. Find the credentials, open a database client, configure a connection, fix whatever is wrong with it, and repeat for the next service.

It is small friction, which is exactly why it never gets fixed, and it happens every single day.

Automatic detection and browsing across PostgreSQL, MySQL and MariaDB, MongoDB, and Redis, covering schemas, tables, columns, rows, collections, documents, inferred document structure, keys by type, and time to live.

Live synchronisation through Docker's own event stream, so a container starting or stopping appears without a refresh, export of any view as comma separated values, a manual credential path for the cases detection cannot cover, light and dark themes, and an installable progressive web app.

Mount the Docker socket and everything else follows: scan the running containers, identify each database by its image, read the connection details out of its environment, and hand it to the right adapter.

Adapters are the extension point. Each database family implements the same interface, so support for another engine is another adapter rather than another branch in a growing conditional.

Read only, with no exception. There is no write path in the codebase at all, which is what makes it safe to point at something that matters.

Creator and lead developer.

Published as a public container image and a public repository. Free and open source under MIT, with no plan to commercialise it.