A closed appliance. No telemetry.
It runs on your hardware and holds attack tools and vulnerable systems. Here is what it opens, what it sends and how to report a problem.
What it opens.
Two ports
Only 80 and 443 are open. A WireGuard port opens only if you turn on remote access. The appliance makes its own certificate on first boot, so your browser shows a warning.
No SSH
The shipped image has no SSH service. You manage it from the browser or your hypervisor's console. Remote access publishes the management interface only.
Sealed by design
Safety is architecture, not a setting. Every environment starts with no path to the host, your network or another environment. A cloud node is the one way out; in bridge mode it joins your network by design.
What it sends.
Nothing on its own
There is no telemetry. The license is checked on your box against the signed license file. The Privacy Policy has the details.
Only what you ask for
Discover downloads, the first build of a Content Hub blueprint, container pulls, and the AI builder calling your model. Once deployed, environments run offline. The operating system also needs DNS, time and its own updates. The full table is in the documentation.
Reports you choose to send
Reports go out only when you send them. They're encrypted, and ONEP strips the passwords, keys, certificates and license files it can recognize before anything leaves the appliance.
Who can sign in.
Accounts and MFA
Role-based access, TOTP multi-factor authentication, one browser session per user, and rate-limited sign-in.
Secrets stay put
Remote-access keys and tokens stay on the appliance and are never shown again after you save them.
Your data stays yours
We never host, access or receive your environments or images. See the Terms and the Privacy Policy.
Tell us. A person reads it.
Found a security problem in the product or on this site? Write to us with the subject Security: what you found, the version you ran and how to reproduce it. Test only on your own box.
hello@onep.io