Feature Availability & Release Gates

QA Studio uses a release-aware availability model. Core functionality is not unlocked through arbitrary production toggles. Instead, the visible surface follows the active setup and the current license context.

Current availability model

Capability	Availability	Notes
Runner and Test Hub	All paid plans	Core execution and test selection
AI assistance with project context	All paid plans	BYOK model
Swarm QA	All paid plans	8-agent scan surface
Accessibility Auditor	All paid plans	BFSG / WCAG 2.1 AA
Scout	All paid plans	Research and discovery support
Evidence and PDF outputs	All paid plans	Export and audit documentation
Device Lab	Team	Team-scale execution capability
Architecture Audit	Team	Structural analysis and dependency insight
Ops Portal	On request	Private deployment and advanced operations setup
Scheduled Swarm scans	On request	Recurring scans for custom/private rollout scenarios
Webhooks	On request	Slack, Teams, Discord notifications for advanced deployments
Checkmk integration	On request	Monitoring correlation for private deployment setups
AI Proxy	On request	Self-hosted provider routing for controlled infrastructure

How gating works in the app

1. Shared core modules are available according to the active product baseline.
2. Team areas are unlocked by license or show an upgrade gate.
3. Advanced private-deployment areas remain internal or on-request and are not part of the standard public self-serve plan flow.
4. Developer override controls are reserved for internal diagnostics and support workflows, not normal release usage.

Related

• Licensing & Feature Tiers
• Settings Overview
• Proxy & Network