AFFiNE combines documents, whiteboards, databases, and collaboration in a self-hosted workspace. When a team exposes it, users expect a web application. Administrators also have an /admin surface for users and host configuration. An external inventory should identify the workspace and then test the management boundary separately.
A standalone ZoomEye SDK query using sub_type=all, page 1, and page size 1 produced two useful observations on 30 October 2026 at 00:40 UTC. The application-fingerprint query app="AFFiNE" returned 0 matching observations. The title query title="AFFiNE" returned 2,424. The zero app count does not show that AFFiNE is absent from the internet. It shows that this candidate app fingerprint did not cover the product in the observed data.
That difference changes how an analyst should read the result. A title can identify a login page, a workspace name, or a page that mentions AFFiNE. It can also match a service that is not an AFFiNE deployment. The 2,424 count is evidence of title matches under the exact query, not a confirmed count of exploitable or vulnerable AFFiNE servers.
Start with identity and management scope
Self-hosted AFFiNE documentation places the admin panel at /admin and describes the first administrator account creation path. Treat that route as a management interface even if the application as a whole is intended for broad users. Restrict access through the identity provider, a private network, or an explicitly reviewed proxy rule. Do not assume that a successful workspace login also grants the administrator role.
AFFiNE supports external identity providers for self-hosted deployments, including OIDC and other OAuth integrations. The identity provider policy should define who can join a workspace, who can create a workspace, and which accounts can become administrators. If MFA is required, enforce it at the identity provider or through a policy that the deployment actually evaluates. Record the issuer, client, redirect URI, and allowed groups.
Review the supporting data plane
The workspace is not the only sensitive component. The deployment has application configuration, database access, file storage, backups, and possibly AI provider keys. Review those separately from the front-end title. A public login page does not prove that the database, object storage, or admin settings are exposed, and a healthy login page does not prove the supporting services are private.
Check backup locations and restore access. Collaboration records can contain internal plans, customer information, and credentials pasted into documents. Apply retention and access control to exports, attachments, and administrator-created backups. Log administrator changes to identity providers and workspace settings.
Use layered fingerprints
For an internet inventory, combine the title observation with response headers, certificate names, asset ownership, and a controlled follow-up query. Do not submit login attempts or configuration changes to unrelated hosts. Validate the product on an asset the organization owns, then use the confirmed fingerprint to search for similar deployments.
The useful conclusion from this measurement is methodological. A zero result for a candidate application fingerprint is not a negative inventory result. A positive title query is a lead, not proof of product identity. Review the admin path and identity configuration before treating AFFiNE as an internet-facing service with a manageable data boundary.