-
Notifications
You must be signed in to change notification settings - Fork 2
getting started onboarding
Welcome to your first run with Siyarix!
We know that configuring security tools, managing API keys, and setting up environments can be a headache. That's exactly why we built the Interactive Onboarding Wizard.
On your very first launch, Siyarix will greet you with a warm, guided 11-step process. It automatically detects your system environment, recommends optimal settings based on your hardware, and sets up your entire workspace with virtually zero friction.
Usually, you won't even need to think about this. If Siyarix detects that it hasn't been set up yet, the wizard starts automatically when you run the main command:
# Auto-starts if not initialized
siyarix
# Or, if you want to start it manually:
siyarix init
# Need to start fresh? Re-run the wizard from scratch:
siyarix init --force Curious about what the wizard actually does? Here is the complete breakdown of the 11 steps (Steps 0 to 10) it walks you through in under two minutes:
| Step | What Happens | Why We Do It |
|---|---|---|
| 0 | Welcome & Ethics Pledge | We ask you to acknowledge our acceptable use policy. You must accept the ethical use pledge to continue. Safety first! |
| 1 | Platform Detection | The wizard scans your OS, hardware specs, GPU, RAM, and shell to ensure Siyarix runs perfectly on your specific machine. |
| 2 | Requirements Check | Verifies you have Python 3.12+, pip, git, curl, and a writable configuration directory. |
| 3 | Dependencies Check | Ensures all core Python libraries (like pydantic, rich, httpx, and cryptography) are properly installed. |
| 4 | Tool Discovery | Siyarix scans your PATH for installed cybersecurity tools (like nmap or nuclei) and offers to install missing ones automatically! |
| 5 | Credential Vault | Initializes your ultra-secure AES-256-GCM encrypted credential store. |
| 6 | AI Provider Configuration | The brain! We help you select and configure your AI engine (Cloud APIs like OpenAI, or Local offline models like Ollama). |
| 7 | Mode Selection | Choose your default execution mode: Integrated (default), fully Autonomous, or Registry-only. |
| 8 | Persona Setup | Pick your default AI mindset (e.g., Red Team, Blue Team, AppSec) to frame how the AI approaches problems. |
| 9 | Preferences | Make it yours! Pick your terminal theme, output format, stealth mode toggles, and notification preferences. |
| 10 | Diagnostics & Finalization | Tests your internet connectivity, DNS, and API connections, then initializes your semantic learning system. You are ready to go! |
The most important step of the wizard is connecting Siyarix to its AI brain. You have two main paths:
If you prefer raw power and speed, you can connect Siyarix to commercial APIs. Supported: OpenAI, Anthropic (Claude), Google Gemini, Groq, Together AI, DeepSeek, xAI (Grok), Mistral, and many more. (Note: These require you to paste in your API key during setup).
Working in a sensitive environment? You can run Siyarix 100% offline with zero data leaving your machine! Supported: Ollama, LM Studio, llama.cpp, vLLM.
Hardware-Based Recommendations: If you choose to run local models, the wizard analyzes your available RAM and GPU to suggest the absolute best cybersecurity-tuned model for your machine:
-
≤ 4 GB RAM: Lightweight models (e.g.,
IHA089/drana-infinity-3b) -
4-8 GB RAM: Balanced models (e.g.,
IHA089/drana-infinity-7b) -
8-16 GB RAM: Highly capable models (e.g.,
supergoatscriptguy/mythos-sec:8b) -
16+ GB RAM: High-end models (e.g.,
supergoatscriptguy/mythos-sec:24b)
Once the wizard finishes, it creates a neat, organized workspace in your home directory (~/.siyarix/). Here is a peek at what lives inside:
~/.siyarix/
├── 🎭 personas/ # Core AI personality definitions
├── 🛠️ profiles/ # AI provider profiles
├── 🧠 memory/ # The Knowledge Graph (how Siyarix remembers past scans)
├── 📝 logs/sessions/ # Standard session logs
├── 🔒 logs/audit/ # Your tamper-evident audit trail
├── ⚡ cache/ # Cached tool outputs, DNS, and intel
├── 📊 templates/ # Customizable templates for reports and playbooks
├── 🛡️ playbooks/ # Your saved automated IR playbooks
├── 💾 sessions/ # Saved sessions you can resume later
└── ⚙️ settings.toml # Your central configuration file
Setting up Siyarix in a CI/CD pipeline or a headless server? You can bypass the interactive wizard entirely using environment variables and direct configuration commands:
# 1. Set the provider via environment variables
export MODEL_PROVIDER=openai
export OPENAI_API_KEY=sk-...
# 2. Tell Siyarix to use that provider
siyarix config set model_provider openai
# 3. Securely store the key
siyarix auth set-key openaiNow that your wizard is complete, the fun begins!
- Your First Run — Let's launch your very first automated scan.
- Setup & Configuration — Want to tweak the settings you just made? Read this guide.
Note
👋 Welcome to Siyarix! This is a personal passion project built by a single developer. It's currently under active development and growing fast. Expect rough edges, but lots of love! ❤️
Welcome to the Siyarix Documentation Map! This page serves as your master compass for navigating the extensive documentation we have built for the platform.
Whether you are a brand new user, a seasoned security operator, or a developer looking to contribute to the core engine, you can find exactly what you need here.
Not sure where to start? Pick the path that best describes you:
Just getting started? We highly recommend following these guides in order:
- Installation Guide — Get Siyarix running on your machine.
- Onboarding Wizard — Let our interactive wizard help you set up your API keys and environment.
- Setup & Configuration — A deeper dive into customizing your setup.
- Your First Run — A gentle walkthrough of your very first Siyarix command.
Ready to put Siyarix to work? Dive into our operational guides:
- Interactive Chat (REPL) — Learn how to use the powerful interactive terminal.
- Security Workflows — Best practices for recon, vulnerability assessment, and incident response.
- Cloud & IaC Scanning — How to secure your cloud environments and infrastructure code.
- Compliance Frameworks — Map your scans to SOC 2, HIPAA, ISO 27001, and more.
Looking under the hood or wanting to write some code? Start here:
- Contribution Guide — Our workflow, standards, and how you can help!
- Codebase Overview — A comprehensive map of our 82+ source modules.
- Testing Standards — How we ensure reliability with pytest and CI/CD.
- Module Architecture — Component design and responsibilities.
If you prefer to browse the raw structure, here is a complete layout of the docs/ folder:
docs/
├── 🚀 getting-started/ # Installation, onboarding, and configuration
│ ├── installation.md # Multi-platform install (pip, brew, winget, docker)
│ ├── onboarding.md # The interactive 11-step setup wizard
│ ├── setup.md # Managing API keys, credentials, and settings
│ ├── first-run.md # A walkthrough of your first session
│ ├── configuration.md # A deep-dive into advanced settings
│ └── troubleshooting.md # Common issues and how to fix them instantly
│
├── 📖 user/ # Daily operations and workflows
│ ├── cli-commands.md # Reference for 50+ CLI commands across 12 groups
│ ├── interactive-chat.md # Mastering the AI REPL and 54+ slash commands
│ ├── security-workflows.md # Recon, vulnerability assessment, incident response
│ ├── cloud-scanning.md # Multi-cloud security scanning (under development)
│ ├── compliance.md # Framework mapping (SOC 2, NIST, GDPR, PCI-DSS)
│ ├── threat-intelligence.md# Integrations with OTX, NVD, and MITRE ATT&CK
│ ├── playbooks.md # Building automated YAML-based IR playbooks
│ ├── workflow-files.md # DAG workflow reference (programmatic API)
│ ├── reporting.md # Multi-format report generation
│ ├── offline-registry.md # Running without AI (Offline/Registry execution mode)
│ └── ai-workflows.md # Advanced AI-driven autonomous operations
│
├── 💻 developer/ # Building, testing, and extending Siyarix
│ ├── codebase-overview.md # Full module structure mapping
│ ├── contribution-guide.md # How to submit PRs and our coding standards
│ ├── module-architecture.md# Component design and responsibilities
│ ├── testing.md # Writing tests (pytest), coverage, and CI/CD
│ └── building.md # Packaging, distribution, and Docker builds
│
├── 🏗️ architecture/ # System design and core internals
│ ├── overview.md # High-level data flow and layered orchestration
│ ├── ai-agent-pipeline.md # The AgentCore reasoning and execution pipeline
│ ├── provider-abstraction.md# How we unify 26 different AI providers
│ ├── execution-engine.md # Plan-based step orchestration
│ ├── memory-and-state.md # Knowledge graph, session persistence, and learning
│ ├── security-model.md # The Permission Gate, DLP, audit logging, and OPSEC
│ └── intent-routing.md # Semantic intent classification and routing
│
├── 🧠 ai/ # Deep dive into the AI provider & agent systems
│ ├── routing.md # Managing 26 providers, failovers, and circuit breakers
│ ├── persona-system.md # Overview of our 10 security personas
│ ├── agent-reasoning.md # The Observe-Reason-Act loop and tool call repair
│ ├── tool-execution.md # The tool registry, capability graph, and parsers
│ ├── ensemble.md # Parallel LLM voting strategies
│ ├── multi-wave.md # Iterative goal execution with context carry-over
│ ├── prompt-architecture.md# System prompt design and management
│ └── safety.md # Our rigorous 8-layer hallucination mitigation system
│
├── 🛡️ security/ # Safety, ethics, and threat models
│ ├── reporting.md # How to safely report vulnerabilities to us
│ ├── threat-model.md # System threat model and our mitigations
│ ├── operational-security.md# TOR routing, stealth modes, and OPSEC controls
│ ├── ethical-policy.md # Mandatory rules of engagement for all users
│ └── abuse-prevention.md # How we prevent misuse of the AI engine
│
└── ⚖️ legal/ # Licensing and governance
├── agpl-guide.md # A plain-English overview of the AGPL-3.0-or-later license
├── why-agpl.md # The philosophy behind our license choice
├── trademark-policy.md # Branding and trademark guidelines
├── responsible-ai.md # Our framework for ethical AI usage
├── disclaimer.md # Important legal disclaimers
└── plugin-exception.md # The license exception for building custom plugins
As you read through the documentation, you might encounter some specific terms. Here is a quick cheat sheet:
| Term | What It Means |
|---|---|
| Provider | The backend AI engine powering Siyarix (e.g., OpenAI, Anthropic, Ollama). |
| Tool | A traditional security executable installed on your system (e.g., nmap, nuclei). |
| Plan | A step-by-step sequence of tool commands intelligently generated by the AI. |
| Workflow | A hardcoded, predefined execution path (usually defined in YAML/JSON) that doesn't require AI generation. |
| Persona | A specialized behavioral profile given to the AI (e.g., instructing it to act specifically as a "Network Recon Specialist"). |
| Knowledge Graph | Siyarix's internal memory where it stores findings (like IP addresses, open ports) to contextually inform future steps. |
Need help finding something specific? Feel free to use the search bar at the top of the documentation site, or open a discussion on our GitHub!