License Usage - apviso [APVISO](/)Product

Resources

Developers

Company

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

[Login](/login)[Start free pentest](/register?intent=free-local-pentest)

[Login](/login)[Start free](/register?intent=free-local-pentest)

[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 self-hosted license, target visibility, runner health, and runner concurrency.

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

A pentest can start when:

- The organization has an active self-hosted license.
- 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.

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

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

### Related Articles

[Subscription Plans

Compare the APVISO subscription tiers — Solo, Launch, Team, Partner, and Enterprise — and understand what each includes.](/docs/subscription-plans)[Legacy Pay-As-You-Go

How legacy PAYG billing records relate to the current self-hosted license model.](/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)
- [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.