System Requirements
What your application and CI/CD environment need to work with VigilQA.
Application requirements
VigilQA tests your application externally — it doesn't require any SDK or agent installed in your codebase. Your application needs to meet the following:
| Requirement | Details |
|---|---|
| Network reachability | Application URL must be accessible from VigilQA cloud infrastructure. Staging and preview environments on public URLs are ideal. VPN or private network apps require Enterprise plan with network peering. |
| Stable base URL | A consistent HTTPS base URL per environment (production, staging, etc.). |
| Web UI apps | Must render in a standards-compliant browser (Chromium-based). JavaScript-rendered SPAs are supported. |
| API apps | REST or GraphQL endpoints returning JSON. OpenAPI/Swagger spec improves generation quality but is not required. |
| Authentication | Apps behind login require test credentials or API keys configured per environment in the dashboard. |
Supported application types
| Type | Supported modules | Status |
|---|---|---|
| Web application (SPA, MPA) | Web UI, Visual Regression, Accessibility, Performance | Supported |
| REST API | REST/GraphQL API, API Contract, Security/VAPT, Performance | Supported |
| GraphQL API | REST/GraphQL API, API Contract | Supported |
| Mobile web (responsive) | Web UI, Accessibility, Visual Regression | Supported |
| Native mobile apps | — | Not supported |
| Desktop applications | — | Not supported |
CI/CD platforms
VigilQA integrates with any CI/CD platform that can make outbound HTTPS calls. Native integration guides are provided for:
| Platform | Integration type | Status |
|---|---|---|
| GitHub Actions | Official action + webhook | Available |
| GitLab CI | API call step + webhook | Available |
| Jenkins | Shell step + webhook | Available |
| CircleCI | Webhook / API call | Available |
| Bitbucket Pipelines | Webhook / API call | Available |
| Azure DevOps | Pipeline task (beta) | Beta |
Dashboard browser requirements
The VigilQA web dashboard is tested against:
- Chrome / Chromium 110+
- Firefox 115+
- Safari 16+
- Edge 110+
JavaScript must be enabled. The dashboard does not require any browser extensions.
Network requirements
Outbound from your CI/CD
Your CI/CD runner needs outbound HTTPS (port 443) access to:
api.sentinelflux.in— trigger runs and fetch results via the VigilQA API
Inbound to VigilQA from your app
No inbound connections required. VigilQA's agents initiate all connections outbound to your application URL.
VigilQA to your application
VigilQA agents make HTTPS requests to your application from a fixed set of IP ranges. You can whitelist these in your firewall/WAF rules. The current IP allowlist is available in Settings → Network → IP Allowlist in the dashboard.
Private or VPN-gated applications: If your staging environment is behind a VPN or firewall, you'll need to either whitelist VigilQA IPs or use the Enterprise plan's network peering feature. Contact engage@sentinelflux.in for assistance.
LLM provider requirements
VigilQA's AI agents use a large language model for generation. By default, this is a Mistral-based model hosted on VigilQA infrastructure. No configuration is required.
Enterprise plans support connecting a local Ollama model for air-gapped environments. See LLM Configuration for details.