Skip to main content
There is no database outside the console. Not behind the registry, not behind the API, and not behind the MCP server. Checked 29 September 2026.

​
Files are the data layer

The registry, mzizi-dev/mzizi-registry, holds no database. Supabase was removed from it on 29 September 2026 (mzizi-registry#368). What it holds is files: A human changes the registry with a file edit, where a diff and a reviewer can see it. Writing component source with SQL was retired before the database itself was removed, and no component is stored in a database row.

​
Who serves the files

Because both Workers pin a registry commit, “what does api.mzizi.dev serve?” always has an exact answer: the registry at that commit. The API names it in its x-mzizi-source header, and the MCP server names it in catalogue.json.

​
The console is the one database

The Mzizi console at app.mzizi.dev, run under Nyuchi, is the only part of Mzizi that uses a database, Supabase. It holds what cannot be a file:
  • accounts, users, keys and anything else per-user;
  • component version history, written by releases;
  • usage telemetry;
  • the Fundi issue desk, self-healing log and observability events.
That is why the API’s version-history route answers 503, and why /v1/stats reports zeroed usage totals alongside real per-node counts. The data behind them belongs to the console, not to the registry.
If you find a Mzizi page, README or response that says the registry, the API or the MCP server reads from Supabase or another database, it predates 29 September 2026 and is wrong. The API’s own discovery document and OpenAPI text are two such places; see the API gateway.