Datasette has added a feature called Datasette Apps, enabling users to create and host custom HTML applications directly within a Datasette instance, according to an official blog post published on June 18, 2026.

The feature works by wiring those custom applications to Datasette's existing JSON API. That means an app can query, filter, and display data using the same API surface that external clients already use — no separate backend logic required, no additional service to run. The HTML lives inside Datasette; the data layer is Datasette.

For anyone who has worked with Datasette in a production context, the appeal is immediate. The tool has long excelled at exposing SQLite databases as browsable, queryable endpoints, and its JSON API has been a quiet workhorse for lightweight data pipelines and internal tooling. The friction point has always been the last step: when you wanted a purpose-built interface — a dashboard, a lookup tool, a custom form — you had to stand something up separately and point it at the API from outside. Datasette Apps collapses that gap.

The practical effect is that a single Datasette deployment can now serve both the data and a bespoke interface for that data. For small teams, journalists, researchers, and solo developers who rely on Datasette precisely because it keeps infrastructure minimal, that consolidation matters. Hosting one thing is simpler than hosting two.

Looking at what this means for how Datasette fits into a broader stack: the JSON API-first architecture is a deliberate constraint, not a limitation. By making the custom app a consumer of the same API any external client would use, Datasette Apps avoids the trap of a privileged internal data path that diverges from what third-party tooling sees. The interface and the API stay honest to each other. That is a sound design choice, and it keeps the system auditable.

Worth noting: Datasette has historically occupied an interesting niche — genuinely useful for data journalists, researchers, and civic tech practitioners, but also increasingly adopted by developers who want a fast path from a SQLite file to a shareable, queryable endpoint. Apps extends that trajectory. The feature does not change what Datasette is; it extends how far a single deployment can reach without requiring additional infrastructure.

The extent of what Datasette Apps can express — the complexity of apps it can host, any sandboxing or security model for the embedded HTML, plugin hooks — is not detailed in the available announcement. Those specifics will matter for teams considering whether to rely on it for anything externally exposed. The documentation at datasette.io is the appropriate place to verify current capability boundaries before committing it to a production workflow.