Shelf's Eight Application Matches Are Too Ambiguous for an Asset Count
Shelf is a self-hostable asset-management platform for tracking equipment, custody, locations, kits, audits, bookings, and labels. Teams use it to answer who has a device, where it is, and when it is due back. The self-hosted Docker setup relies on an external Supabase environment for the database, authentication, and storage.
A ZoomEye query on 2026-11-22 returned 8 matches for app="Shelf". title="Shelf Asset Management" returned zero and http.body="Shelf Asset Management" returned 2. The application name is a common English word, so the eight matches cannot be treated as a confirmed Shelf inventory without inspecting ownership and page context.
The ambiguity is the finding
A weak product name makes a convenient but unsafe search. The app field is more specific than a bare body word, yet it can still match another product, a custom deployment label, or a page whose metadata includes the word. The zero title phrase and two body phrase matches show how much the result depends on the chosen field.
This is not a reason to discard the query. It is a reason to pair it with a stronger assertion: an owned domain, a known Supabase project, a login page, a product-specific route, or a certificate record. The count should not appear in a board report as "eight exposed Shelf servers."
What the platform holds
Asset data includes serial numbers, purchase information, locations, user assignments, maintenance status, and sometimes photos or attachments. Custody records can reveal which employee holds a laptop or which site stores a test instrument. The inventory also supports label printing and QR scanning, so asset identifiers may appear in physical spaces and public photographs.
Shelf's Docker documentation says the community-supported deployment needs Supabase for database, authentication, and storage. That architecture splits the trust boundary. The web app can be reachable while the database and authentication remain private, or the Supabase project can be exposed separately. The product query does not reveal either state.
The documentation also notes that production logs an insecure-configuration warning when example values are used. That is a useful owner check: deployment secrets and URLs should not remain at documentation defaults, especially when the service is reachable outside the local network.
Reviewing a candidate
Start with the domain and certificate. Confirm that the page is actually Shelf, identify the workspace or organization, and verify ownership before sending any request beyond a harmless public page. For an owned instance, review authentication, workspace membership, role assignments, guest or self-service access, and public links.
Check Supabase project exposure. The API keys used by a browser application are not all equivalent to service-role credentials. A service-role key must never be shipped to the client. Verify row-level policies, storage permissions, and authentication redirect URLs as part of the Shelf deployment rather than assuming the front end enforces every rule.
Review custody and audit workflows. A user who can edit assets should not automatically be able to erase history. Record who can move an asset, change a location, close an audit, and export the inventory. Check dormant accounts and former staff assignments.
A reliable baseline
Keep a private asset list with the public hostname, Supabase project, authentication mode, role model, backup state, and owner. Re-run the app="Shelf" query only as a lead source, then verify each candidate with an independent product signal.
The eight matches are not a meaningful population estimate. They are a reminder that a product with a generic name needs a compound fingerprint and an ownership record before its exposure can be measured.