About
What NetOkay is
Small connection checks that separate "the browser works" from "the app, container, or Agent fails".
NetOkay is a free set of connection checks for developers. In the browser it shows the
public IP your requests use, tests a WebSocket round trip, watches a server-sent event
stream arrive, and checks a website's HTTP status. The same checks run from a terminal
through the netokay CLI and from an AI coding agent through an Agent Skill, and
write one JSON EvidenceBundle that records what was observed, what stayed unknown, and what
was redacted.
How the pieces fit together
- Browser tools on this site run from your browser to NetOkay and need no installation. Start on Tools.
- Control is NetOkay's public service at netokay.net, hosted on Cloudflare. Every check reaches it first, so a failing target can be compared with a path that is known to work.
- The CLI, published as netokay on npm with source on GitHub, runs the same checks from the environment where the failure happens. See API & CLI.
- The Agent Skill lets Codex, Claude Code, or Cline run a bounded diagnosis and hand back Evidence without changing anything. See Agent handoff.
What every check has in common
Each check is bounded: read-only, limited in time and size, aimed at one public target, and unable to change network or system configuration. Results describe what was observed and list what they cannot prove. A missing observation is reported as unknown rather than turned into a pass; the Evidence contract spells out the fields.
What NetOkay does not do
There are no accounts, dashboards, or uploads. The Worker keeps no request bodies, credentials, or Evidence, and the CLI writes Evidence only to your terminal or a file you name. The website uses client-side Google Analytics for page views and a few named button clicks; the privacy page lists exactly what is sent.
Who makes it
NetOkay is built and run by one independent developer, published on GitHub as flreey. It is not backed by a company. Release state, including the current CLI version and its checksum, is kept on the status page.
Contact
Questions, bug reports, and pilot requests go to flreey@gmail.com or the GitHub issue tracker. Do not send Evidence, secrets, payloads, or customer data by email.