Local Multi-Instance Visibility For Datasette

Issue 96 Edition 2026-04-06 4 min read

General

Sources: 1 • Confidence: High • Updated: 2026-04-13 03:36

Key takeaways

After installing datasette-ports, running the command "datasette ports" produces a list of every running Datasette instance.
Version 0.1 of the Datasette plugin "datasette-ports" has been released.
The output of "datasette ports" includes each instance URL, its Datasette version, and the associated databases and plugins.
The author describes datasette-ports as README-driven development intended to solve a problem that may be unique to them.
The author frequently runs many different Datasette instances concurrently and sometimes loses track of them.

After installing datasette-ports, running the command "datasette ports" produces a list of every running Datasette instance.
The output of "datasette ports" includes each instance URL, its Datasette version, and the associated databases and plugins.
The author frequently runs many different Datasette instances concurrently and sometimes loses track of them.

Version 0.1 of the Datasette plugin "datasette-ports" has been released.
The author describes datasette-ports as README-driven development intended to solve a problem that may be unique to them.

By what detection method does "datasette ports" identify 'every running Datasette instance' on a machine, and what are its known failure modes (e.g., containers, different users, nonstandard networking, multiple Python environments)?
What platforms and environments are explicitly supported (operating systems, containerized workflows, remote dev boxes), and are there documented limitations?
How does the plugin obtain the per-instance metadata (Datasette version, databases, plugins), and under what conditions might that metadata be incomplete or incorrect?
Is there evidence of user adoption, maintenance commitment, or planned iteration beyond the initial 0.1 release?
Is there any clear decision-readthrough (operator, product, or investor) implied by the corpus beyond 'try the plugin if you have this workflow problem'?

Pain point exists for developers running multiple local Datasette instances; a discovery command suggests demand for lightweight local observability and instance management within the Datasette ecosystem.
Ecosystem maturation: plugins are expanding from data features into workflow tooling, implying increasing professional and repeat usage that values time savings and reduced debugging friction.
Metadata surfacing of versions, databases, and plugins hints at future needs for standardized instance introspection and operational visibility, potentially enabling broader tooling for coordination and debugging.

Evidence of adoption beyond the author, such as downloads, stars, issues, or third party mentions showing the multi instance tracking problem is common.
Rapid iteration after version 0.1 with documented support across common environments and clear limitations, indicating maintenance commitment and growing scope.
Integration or references by core Datasette community or documentation that position the command as a standard workflow tool.

Discovery method proves fragile or limited across platforms, users, containers, or networking setups, making the tool unreliable for typical workflows.
No follow up releases or maintenance activity after 0.1, suggesting the plugin remains a personal utility with minimal ecosystem impact.
User feedback indicates the problem is niche or already solved via existing workflows, reducing the relevance of the plugin category.