The proposed Verglos Free, Pro, Studio, and Enterprise model

Verglos does not currently sell Free, Pro, Studio, or Enterprise plans. The public package is an alpha, and its working product surface is the local scanner.

The four names describe a proposed segmentation model. Publishing the distinction helps explain product intent, but it is not a price sheet, service commitment, or launch announcement.

Proposed Free: local scanning

The principle is that a developer should be able to see scanner findings without paying to reveal them. A sustainable free surface could include local scanning and local report output, subject to the actual package documentation and supported capabilities.

Proposed Pro: bounded verification

Pro could fund local sandbox verification, richer policy, and repeatable project configuration. That depends on hunt becoming a safe, functional product. It is a command shell in 2.0.0-alpha.1, so there is no Pro entitlement to buy today.

Proposed Studio: portable evidence

Studio could add signed summaries and controlled verification links for agency and client handoffs. This introduces hosted identity, storage, signing, retention, and support responsibilities. attest is also an unavailable shell in the current alpha.

Proposed Enterprise: organizational controls

An enterprise layer could address centralized policy, identity, auditability, private deployment, and support. Those needs should be validated with organizations before features or pricing are promised.

What remains undecided

Prices, usage limits, team models, hosting regions, service levels, data retention, and launch dates are undecided and unavailable. The boundaries may change as the product is tested.

The durable principle is simpler than the matrix: do not hide urgent local findings behind a payment step, and charge only where the product assumes real ongoing operational cost or delivers a distinct workflow. Everything else is a hypothesis until it ships.