Pro Sells Time, Not Safety — ELY Agent Input Preflight v0.8.0

A developer released ELY Agent Input Preflight v0.8.0, a local-first verification layer for AI coding agents that independently checks whether an agent's work actually succeeded rather than trusting a zero exit code. The release adds an optional Pro entitlement (499 RUB) covering upgrade and license-status commands, while the developer kept the full verification and safety core in the free Community edition, stating "Pro sells time, not safety." The paid path was validated end-to-end through payment webhook, license issuance, Windows activation and signed entitlement.

ELY Agent Input Preflight v0.8.0 is released. This release introduces an optional paid Pro entitlement, but I made one rule non-negotiable: Pro sells time, not safety. The Community edition keeps the complete verification and safety core. GitHub Release: https://github.com/Golovenkov79/ely-agent-input-preflight/releases/tag/v0.8.0 https://github.com/Golovenkov79/ely-agent-input-preflight/releases/tag/v0.8.0 Product page: https://elyzorix.ru/tools/agent-input-preflight/ https://elyzorix.ru/tools/agent-input-preflight/ ELY Agent Input Preflight is a local-first verification layer for AI coding agents. Its job is not to replace the coding agent. Its job is to independently answer questions such as: exit code 0 ? The project is built around an important distinction: PROCESS → EXECUTION → ACCEPTANCE → FINAL A successful process exit is not automatically proof of a successful result. v0.8.0 adds the foundation for an optional Pro entitlement. New functionality includes: ely-preflight upgrade ely-preflight license status elyzorix.ru The important part is what did not change. I did not move the safety core behind the paywall. Community still includes: You do not need Pro to know whether an AI coding agent did something unsafe or failed verification. That would defeat the purpose of the tool. The design principle is simple: Community protects correctness. Pro should reduce time and friction. The paid layer is intended for convenience, automation and productivity rather than making the free version artificially unsafe or incomplete. I think developer tools should earn money by making work faster — not by intentionally weakening the free safety layer. Before releasing v0.8.0, I tested the commercial route with an actual 499 RUB subscription purchase. The verified path was: payment → payment provider webhook → license issued → license claim → Windows activation → signed entitlement → PRO ACTIVE