Agnixa Documentation

After purchasing your Agnixa subscription plan, log in to your account and complete your user profile with the following information:

• Full Name: Your complete name for account identification
• Username: A unique username for your Agnixa account
• Mobile Number: Contact number for important notifications
• Timezone: Your local timezone for accurate scheduling and logs

Create a new project in Agnixa by providing the following details:

Connect your repository by adding your personal access token:

1. Navigate to the Settings section in your Agnixa dashboard
2. Select your Git provider (GitHub or GitLab)
3. Create a personal access token from your Git provider (see Access Token Setup section)
4. Paste the token into the "Personal Access Token" field
5. Click "Save" to establish the connection

Once your project is configured, Agnixa automatically creates a brain.agent file to maintain conversation history and context for your project.

Once everything is set up, you can use Quick Actions for common DevOps tasks. Click on any quick action button to instantly execute pre-configured workflows:

1. Access Configuration Panel

After logging in, navigate to your dashboard and click on "Add Repository" or "Configure New Project" button.

2. Select Git Provider

Choose your Git provider from the dropdown menu (GitHub, GitLab, or Bitbucket).

3. Paste Access Token

In the "Access Token" field, paste the personal access token you created earlier. This token will be encrypted and stored securely.

4. Enter Organization Name

Enter your organization or username. This is the account that owns the repository.

5. Enter Repository Name

Enter the exact name of your repository as it appears in your Git provider.

6. Specify Branch

Enter the branch name you want Agnixa to work with. This is typically your development or staging branch (e.g., "develop", "staging", "feature/new-feature").

7. Save Configuration

Click "Save" or "Connect Repository" to complete the configuration. Agnixa will validate your credentials and establish the connection.

Automatic Verification

When you submit your configuration, Agnixa will:

• Validate your access token
• Verify access to the specified organization and repository
• Check permissions on the specified branch
• Test API connectivity with your Git provider

Connection Status Indicators

You'll see visual indicators showing the connection status:

Example Prompts

Best Practices

• Be specific in your prompts - include details about what you want to accomplish
• Review Agnixa's proposed actions before confirming execution
• Start with simple tasks to understand how Agnixa interprets your requests
• Use clear, action-oriented language (e.g., "deploy", "test", "build")
• Specify environments, branches, or services when relevant

AI Response Flow

When you submit a prompt, Agnixa will:

1. Analyze your request and understand the intent
2. Check your repository for relevant code and configuration
3. Propose a plan of action with specific steps
4. Ask for your confirmation before executing
5. Execute the approved actions
6. Provide detailed feedback and results

Code Review Requirement

Before any code changes are merged, you must:

• Review all proposed changes carefully
• Understand what Agnixa is doing and why
• Verify the changes align with your requirements
• Check for any unintended side effects
• Approve or reject the changes explicitly

Scope Limitation

Agnixa will only perform the specific tasks you request. It will:

• ✓ Execute only what you explicitly ask for
• ✓ Ask for clarification if your request is ambiguous
• ✓ Warn you about potentially risky operations
• ✗ NOT make unauthorized changes to your codebase
• ✗ NOT perform actions beyond your request scope
• ✗ NOT make assumptions about what you "might" want

Recommended Permissions

Grant ONLY the minimum permissions required:

Token Security Guidelines

• Set expiration dates: Configure tokens to expire after 90 days and rotate them regularly
• Use unique tokens: Create separate tokens for each service or application - never reuse tokens
• Store securely: Never commit tokens to version control or share them in plain text
• Monitor usage: Regularly review token activity in your Git provider's audit logs
• Revoke immediately: If a token is compromised or no longer needed, revoke it immediately
• Limit scope: Only grant access to specific repositories that need automation, not all repositories

Additional Security Measures

• Enable two-factor authentication (2FA): Protect your Agnixa account with 2FA for an extra layer of security
• Use IP allowlisting: If your Git provider supports it, restrict token usage to specific IP addresses
• Review audit logs: Regularly check Agnixa activity logs to ensure all actions are authorized
• Implement branch protection: Use your Git provider's branch protection rules to require reviews before merging
• Separate environments: Use different tokens and configurations for development, staging, and production

How to Start Your Trial

1. Sign up for a free Agnixa account
2. Complete your profile information
3. Click "Start Free Trial" on the pricing page
4. Connect your first repository and start automating

After Your Trial

When your 14-day trial ends, you'll automatically transition to the Basic Plan at $19/month. You can upgrade to Pro or Enterprise at any time, or cancel if Agnixa isn't the right fit.

All your projects, configurations, and conversation history are preserved when you transition to a paid plan.

The Three Brains

Each Brain specializes in a different aspect of DevOps automation:

Plan-Based Access

Brain availability depends on your subscription plan:

How Blueprint Works

Blueprint's agentic AI analyzes your requirements and creates comprehensive plans:

1. Requirement Analysis: Understands your business goals, technical constraints, and success criteria
2. Architecture Design: Creates system diagrams, component relationships, and data flow models
3. Risk Assessment: Identifies circular dependencies, single points of failure, scalability bottlenecks, and compliance gaps
4. Task Breakdown: Generates sprint-ready tasks with dependencies, effort estimates, and acceptance criteria
5. Documentation: Produces technical documentation, API specs, and implementation guides

Example Use Cases

How Recon Works

Recon's agentic AI performs comprehensive security and compliance analysis:

1. Static Analysis: Scans code for syntax errors, code smells, and anti-patterns
2. SAST Scanning: Identifies security vulnerabilities using static application security testing
3. Compliance Checking: Cross-references code against SOC 2, GDPR, HIPAA, and other regulatory frameworks
4. Secret Detection: Finds hardcoded credentials, API keys, and tokens in current code and git history
5. CVE Detection: Checks dependencies against known vulnerability databases (OWASP Top 10, CVE)
6. Priority Mapping: Ranks issues by severity and maps each to exact line, file, and regulation violated

Supported Languages & Frameworks

Recon currently supports:

• Python, Node.js, Go, Java and others
• Terraform and Infrastructure as Code (IaC)
• Docker and container configurations
• Kubernetes manifests and Helm charts
• More languages and frameworks on the roadmap

Example Use Cases

How AutoX Works

AutoX's agentic AI handles the complete deployment automation workflow:

1. Stack Analysis: Reads your codebase to understand languages, frameworks, dependencies, and build requirements
2. Pipeline Generation: Creates optimized CI/CD pipelines tailored to your tech stack and deployment targets
3. Infrastructure Provisioning: Generates Terraform configurations and provisions cloud resources
4. Security Configuration: Sets up OIDC authentication, IAM roles, security groups, and network policies
5. Deployment Execution: Runs builds, tests, and deployments with health checks and validation
6. Monitoring & Rollback: Monitors deployment health and triggers automatic rollbacks on failure

Supported Platforms

AutoX integrates with:

Example Use Cases