Argus

Autonomous QA for the real world. Argus reads your requirements, scores them, generates Playwright tests, runs them on every deploy, and shows what broke — in Mission Control, a live ops console.

No LLM key required for smoke tests, rule-based parsing, and most dashboard actions. Add a provider when you want richer generation and analysis.

Grouped side rail · dark theme · Ask Zyra · macOS Terminal live job · Search / ⌘K · 25+ actions

Contents

• Quickstart
• Mission Control
• Architecture at a glance
• Capabilities
• Why Argus
• Important boundaries
• License

🚀 Quickstart

Requires Python 3.10+, Node 20+, and Docker (only for the container path). make install handles the rest, including Playwright's Chromium download.

git clone https://github.com/zyvorai/argus.git && cd argus
cp .env.example .env          # set ZYVOR_BASE_URL
make install                    # Python venv + Playwright Chromium
argus test exec --grep @smoke   # first green run — no API key
argus serve --port 8080         # → http://localhost:8080/dashboard

Remote deploy in one command:

./scripts/deploy-remote.sh YOUR_HOST YOUR_USER --service --key
# Mission Control on port 30080 — credentials printed in deploy summary

Container:

docker pull ghcr.io/zyvorai/zyvor-argus:v0.9.2
docker run --rm -p 8080:8080 --env-file .env ghcr.io/zyvorai/zyvor-argus:v0.9.2 serve --port 8080 --host 0.0.0.0

Track	Where
Non-production use (free under the Zyvor Production License)	This repo
Production / commercial license	https://zyvor.dev
Docs	Tutorials · zyvor.dev/docs

More: user manual · feature guide · configuration · remote deploy · enterprise overlay.

🖥 Mission Control

argus serve exposes Mission Control at /dashboard.

• Grouped side rail — Console (Overview, Ask Zyra) · Testing (Pipeline, Visual, Quality, Journeys, API, Probes, Requirements) · Security · Operations (Runs & schedules)
• Header — knowledge lamp, dark/light theme, Search (also ⌘K)
• Overview — hero status, pass rate, next smoke, and a live macOS Terminal job panel (Copy / Save / Stop)
• Hash routes — #pipeline, #ask, #requirements, #operations

Full action list: dashboard tutorial.

🗺 Architecture at a glance

flowchart LR
  subgraph Sources["Specs"]
    GH["GitHub"]
    PDF["PDF"]
    Email["Email"]
    Jira["Jira"]
    Transcript["Transcript"]
  end
  Sources --> Pipeline["LangGraph pipeline"]
  Pipeline --> Playwright["Playwright"]
  Playwright --> Console["Mission Control"]
  Pipeline -->|"fail"| Autofix["autofix"]
  Autofix --> Playwright

Loading

argus test run --source github --spec docs/specs/feature.md
argus test run --source document --spec requirements/checkout.pdf
argus flow run https://zyvor.dev --steps docs/assets/zyvor-dev-demo.steps --video

Command reference: docs/test-authoring.md.

🧰 Capabilities

• Requirements — versioned, scored, and traced to every generated test, plus impact by shared data models and flows
• One pipeline — the same LangGraph path from the CLI or one dashboard click
• Self-healing autofix — suggests and applies repairs, then re-runs
• Contracts — OpenAPI contract test, breaking-change diff, and HAR consumer verify
• Authorized security — misconfig, CVE, SCA, DAST, LLM red-team, and chaos jobs with an audit trail and sandboxed PoC
• Mission Control — Console, Testing, Security, and Operations in one rail

Ask Zyra (optional knowledge extra): docs/tutorials/14-ask-zyra-knowledge.md. What DAST covers, and what it deliberately defers: docs/security-network-attack-gaps.md.

⚖ Why Argus

	Without Argus	With Argus
Specs and tests	Drift apart	Requirements are versioned, scored, and traced
Smoke runs	A tribal ritual	One command, or one dashboard click
Flaky selectors	Waste the afternoon	Autofix suggests a repair and re-runs
API drift	Tribal knowledge	Contract test, OpenAPI diff, HAR verify
Security checks	Spreadsheets	Authorized jobs with an audit trail
Tooling	Five products	One Mission Control

🔍 Important boundaries

What's free under the Zyvor Production License vs. what needs a commercial license (full guide):

Use case	Allowed without a paid license?
Development, testing, evaluation, research, education	Yes
Non-production laboratory and proof-of-concept use	Yes
Production environments and customer workloads	No — needs a commercial license
SaaS, managed services, OEM, appliances	No — needs a commercial license
Redistribution or resale	No — needs written permission and a commercial license

📈 Star History

📄 License

Licensed under the Zyvor Production License v1.0.

• Free for development, testing, evaluation, research, education, and non-production labs
• Paid commercial license required for production, customer workloads, SaaS, managed services, OEM, redistribution, and other revenue-generating use

Commercial terms are issued separately: https://zyvor.dev.

See docs/LICENSING.md. Contributions: CLA.md + DCO.md (git commit -s), governed by our Code of Conduct.