How to Use Browser-Private Tools for Cron, CIDR, YAML, JWT and Kubernetes
A step-by-step DevOps workflow built on client-side-only tools — cron parsing, CIDR maths, YAML and .env conversion, JWT debugging and Kubernetes resources.
Practical guides to developer, DevOps and electrical-engineering tasks — written around tools that run entirely in your browser.
A step-by-step DevOps workflow built on client-side-only tools — cron parsing, CIDR maths, YAML and .env conversion, JWT debugging and Kubernetes resources.
OAuth2 is a flow, JWT is a format — and neither one authorises anything. The claims your backend verifies and validates are what actually decide access.
Data-egress policy made third-party utility sites a compliance problem. Our answer is architectural — every tool runs in your browser, so credentials never leave the machine.
RS256 fails quietly — the happy path verifies while the key, the PEM format or the algorithm allowlist is wrong. Here is how to catch it before it ships.
An LLM will hand you a cron expression and a manifest that look right and run wrong. Here is the verification pass that catches them before a scheduler does.
Why we built a tool platform with no backend, no accounts and no uploads — and what 35 finished tools, a 12 KB app shell and WCAG-audited contrast actually took.