License Usage - apviso [APVISO](/)Product

Resources

Developers

Company

[Pricing](/#pricing)[Partners](/partners)[Enterprise](/enterprise)

[Login](/login)[Get started](/register)

[Login](/login)[Start pentest](/register)

[Home](/)[Knowledge Base](/docs)License UsageBilling & PlansLicense Usage
=============

How self-hosted license state, runner health, and target visibility control pentest starts.

Current Model
-------------

Pentest starts are checked against your plan (pay per pentest or a Launch/Team/Partner/Enterprise subscription), target visibility, runner health, and runner concurrency.

What Starts a Pentest Now
-------------------------

A pentest can start when:

- The organization is on the pay-per-pentest tier or holds an active subscription.
- The target visibility is allowed by the plan.
- At least one non-revoked runner has sent a recent heartbeat.
- Runner concurrency is available.
- The runner preflight passes provider, image, Docker, and network checks.

Pay Per Pentest
---------------

On the base tier there is no subscription. You pay $19 per pentest, and each pentest is fully refunded automatically if it finds zero findings or errors out. Launch, Team, Partner, and Enterprise subscriptions include unlimited scans instead.

Usage Responsibility
--------------------

BYOK model spend is billed by your provider, and runner execution costs remain in your environment. APVISO billing covers the control plane, runner limits, target limits, support, and plan features — either per pentest or through your subscription.

### Related Articles

[Subscription Plans

Compare the APVISO plans — Pay per pentest, Launch, Team, Partner, and Enterprise — and understand what each includes.](/docs/subscription-plans)[Pay Per Pentest

How the pay-per-pentest base tier works, including the automatic refund for empty or errored pentests.](/docs/pay-as-you-go)[Starting a Pentest

How to initiate a pentest, choose a pentest package, and understand what each package means for depth and runtime.](/docs/starting-a-scan)[Retesting Findings

How to verify that vulnerabilities have been fixed by running targeted retests against specific findings.](/docs/retesting-findings)

[Back to Knowledge Base](/docs)

[APVISO](/)Autonomous AI-powered penetration testing for modern web applications.

Subscribe

[](https://github.com/apviso)[](https://x.com/Apviso_com)[](https://www.linkedin.com/company/apviso/)

[![Featured on Good AI Tools](https://goodaitools.com/assets/images/badge.png)](https://goodaitools.com/ai/apviso)

Product

- [Features](/#features)
- [Sentinel](/sentinel)
- [Pricing](/pricing)
- [Integrations](/integrations)
- [Benchmarks](/#compare)
- [Affiliate Program](/affiliate)
- [Partners](/partners)
- [Enterprise](/enterprise)

Resources

- [Blog](/blog)
- [Use Cases](/use-cases)
- [Glossary](/glossary)
- [Comparisons](/comparisons)
- [Alternatives](/alternatives)
- [Compliance](/compliance)
- [Vulnerabilities](/vulnerabilities)
- [Industries](/industries)
- [OWASP APTS](/trust/apts)

Developers

- [Knowledge Base](/docs)
- [API Reference](/docs/api)
- [MCP Server](/docs/mcp)

Company

- [About](/about)
- [Contact](/contact)
- [Status](https://status.apviso.com)
- [Privacy Policy](/legal/privacy)
- [Terms of Service](/legal/terms)

© 2026 APVISO. All rights reserved.