Local Instance Discovery And Introspection For Datasette

Issue 96 Edition 2026-04-06 4 min read

General

Sources: 1 • Confidence: High • Updated: 2026-04-12 10:01

Key takeaways

After installing datasette-ports, running the command "datasette ports" produces a list of every running Datasette instance.
The author describes datasette-ports as an example of README-driven development aimed at solving a problem that may be unique to them.
The output of "datasette ports" includes each instance URL, its Datasette version, and associated databases and plugins.
Version 0.1 of the Datasette plugin "datasette-ports" has been released.
The author frequently runs many different Datasette instances across dozens of terminal windows 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 associated databases and plugins.
Version 0.1 of the Datasette plugin "datasette-ports" has been released.

The author describes datasette-ports as an example of README-driven development aimed at solving a problem that may be unique to them.
The author frequently runs many different Datasette instances across dozens of terminal windows and sometimes loses track of them.

By what method does the command determine which Datasette instances are running (and what are its failure modes or false positives/negatives)?
What environments are supported (operating systems, containerized vs non-containerized runs, virtualenv vs system installs) and are there compatibility constraints?
How is "associated databases and plugins" determined for each instance, and are there cases where this metadata is incomplete or misleading?
Are there any security or privacy considerations in enumerating and displaying local service URLs and configuration-like metadata (databases/plugins) in shared terminals or logs?
Is there evidence of broader demand or user adoption beyond the author’s stated workflow (downloads, issues, community references)?

Incremental developer tooling around Datasette suggests continued ecosystem activity that could support higher retention among power users who run many local instances.
Demand for local service discovery and introspection features may indicate a broader need for observability and developer experience tooling in lightweight data serving workflows.

Evidence of adoption beyond the author such as rising downloads, community mentions, or issues and pull requests for datasette-ports.
Expansion of supported environments and clearer documentation of discovery method and limitations, indicating maintainers are responding to real user feedback.
Integration of similar instance listing or metadata features into core Datasette or other widely used plugins.

Minimal external usage signals such as few installs or no community engagement, aligning with the author describing the workflow as potentially unique.
Frequent false positives or negatives in instance detection or incomplete metadata for databases and plugins, reducing trust in the tool.
Security or privacy concerns from enumerating local URLs and configuration-like metadata that lead users to avoid running or sharing outputs.