Open Notebook is a self-hosted research notebook with a web interface, an API, document ingestion, and stored model-provider keys. Its security defaults are designed for a single user on a trusted machine. A public instance therefore needs a deployment review rather than an assumption that a password field provides multi-user isolation.
Observation
At 07:51 on November 20, 2026 (UTC+8), a count-only ZoomEye SDK query used sub_type=all, page 1, and pagesize 1. app="Open Notebook" returned 0 matches. title="Open Notebook" returned 385 matches.
The title lead can include project documentation, demos, and unrelated notebooks. It is a population for validation, not a count of exposed research environments. A verified deployment should be classified by whether authentication is enabled and whether it is reachable beyond a trusted network.
One password, many data cells
The project's security documentation says OPEN_NOTEBOOK_PASSWORD acts as a single shared password rather than a user account system. Without that value, authentication is off and the interface and API can be used by anyone who can reach them. The same guide recommends a separate authenticating proxy for per-user access.
The API and UI use ports described by the deployment documentation. Review both listeners and the CORS policy in addition to the frontend. The security guide notes that the default CORS behavior is open to every origin and recommends tightening it for production.
Stored model-provider keys require OPEN_NOTEBOOK_ENCRYPTION_KEY. Inventory the key source, the database backup, and the users who can configure models. Adding a provider key can create outbound spend and may permit data to leave the environment when a notebook asks a model to process a document.
A production checklist
Require a long shared password or an authenticated proxy.
Restrict the UI and API to approved networks.
Replace open CORS with the exact frontend origin.
Configure and back up the encryption key separately.
Review external model providers and data-egress policy.
Test API access with the password absent, wrong, and rotated.
Confirm that browser sessions and application data survive only as intended.
ZoomEye provides 385 title leads for ownership and validation. Open Notebook's documented single-password model makes the distinction between a private research tool and a shared internet service especially clear. The organization should choose that model deliberately before exposing the service.