Answers, documentation, and a way to reach us.

No. NTPSense is built from scratch on FreeBSD 14.3 — a Rust control-plane daemon and a PHP Web UI, communicating over a Unix socket. It shares the same underlying OS (FreeBSD) and some of the same components (pf, Kea DHCP) that pfSense/OPNsense also use, but the daemon, Web UI, and Site Mesh VPN architecture are our own code, not a derivative codebase.

No product can honestly claim that, and we won't either. NTPSense is designed to reduce risk through correct firewall, VPN, and proxy configuration — but security also depends heavily on how you deploy and maintain it. See our Software License & Disclaimer for the full, plain-language explanation of what is and isn't guaranteed.

Yes. The entire Web UI, including the EULA and license documents linked from the login screen, is bundled directly on the appliance itself — nothing critical to managing your gateway depends on reaching an external site. This matters for air-gapped or WAN-not-yet-configured deployments.

If it's x86-64 with enough NICs for your zone plan, likely yes — NTPSense doesn't require proprietary silicon. Officially validated hardware is listed on the Products page, but the installer targets standard FreeBSD-compatible hardware more broadly.

NTPSense bundles Squid, Kea DHCP, WireGuard, Headscale/Tailscale, PHP, and lighttpd, among others — full license details (including GPL source-offer compliance for Squid and wireguard-tools) are on our Open Source Notices page. As an end user running the appliance, you're not distributing these components yourself, so your own compliance obligations are minimal — but read the page if you plan to resell or redistribute NTPSense hardware.

Not yet formalized — reach out and tell us your situation (uptime requirements, number of sites) and we'll work out something reasonable.