GitHub Actions Integration — 5-Minute Setup
Drop a workflow file into .github/workflows/bachao-security-scan.yml and trigger a VAPT scan on every push or pull request. The action calls POST /api/scans/book with your target URL and session token, polls until the scan completes, and surfaces critical findings as PR review comments. Bachao.AI is callable from any runner — ubuntu-latest, self-hosted ARM, custom containers — without bundling secrets in the workflow.
GitLab CI Pipeline Example (.gitlab-ci.yml)
Add a `security:vapt` stage that invokes Bachao.AI's REST API from a curl step. Pin the API key as a masked GitLab CI/CD variable. Use the `allow_failure: false` flag to break the pipeline if critical findings are detected, or `allow_failure: true` to report-only until your team has built remediation muscle. Bachao.AI's pipeline plays well with GitLab's self-hosted ARM/AMD runners and merges cleanly with existing SAST + secret-scanning jobs.
Jenkins Plugin & Webhook Config
From Jenkins, call the Bachao.AI scan API via the standard HTTP Request step or a small shell stage. Configure a webhook back to Jenkins from Bachao.AI for the `scan.completed` event — your pipeline picks up the report URL automatically. The webhook payload is HMAC-signed so you can verify authenticity before kicking off downstream stages.
SBOM Generation for DPDP & CERT-In Audits
Bachao.AI's automated VAPT generates a Software Bill of Materials (SBOM) as a side-effect of every scan, listing direct and transitive dependencies, license posture, and CVE exposure per component. The SBOM is exportable as SPDX or CycloneDX and is accepted by DPDP-Act compliance reviewers, ISO 27001 auditors, and increasingly by enterprise procurement teams as part of vendor security assessments.
Shift-Left ROI — Bugs Caught Pre-Prod
Indian manual VAPT engagements (Astra, CyberNX, Kratikal — see their public pricing pages) use enterprise-bracket per-cycle fees and surface findings 4-6 weeks after code lands in production. Bachao.AI's CI/CD integration moves discovery left to the PR — same depth, near-zero marginal cost per run, and findings remediated by the engineer who wrote the code, not handed off to a separate team. Customers running automated VAPT in their pipeline typically catch 60-80% of OWASP Top 10 findings before they ship, which is the highest-leverage ROI in the entire security stack.
SAST + DAST + SCA in a Single Pre-Merge Gate
Most pipelines run SAST and SCA as separate jobs with no shared context. Bachao.AI runs static analysis, software composition analysis, and dynamic testing in a coordinated gate — SAST catches code-level vulnerabilities, SCA flags CVEs in your open-source dependencies, and DAST hits the running app for injection and auth issues, all before the PR can merge. Findings are deduplicated across the three scan types so the same underlying vulnerability does not generate three separate tickets.
PR Comment Bot — Findings With Fix Diffs
When a scan finds a vulnerability, the bot posts a comment directly on the PR with the finding, its severity, and an AI-generated fix diff. The developer sees the problem and the proposed solution in the same review context — no context-switching to a separate dashboard or ticket. Critical findings block the PR from merging by default; medium and low findings are posted as informational comments so the team has full visibility without being blocked on non-critical issues.
Cost: Per-Repo vs Per-Developer Pricing
Global DevSecOps tools like Snyk price per developer at $25/month or more — a 20-person team pays $6,000/year before enterprise add-ons. Bachao.AI offers per-repo options so smaller teams can start without a headcount tax. A free starter plan is available for early-stage teams; full-team and enterprise pricing is scope-based — book a 30-minute call to get a number tailored to your repo count and developer headcount. Indian teams should not pay US per-seat prices for code security.
GitHub Actions & GitLab CI setup in 10 minutes
Bachao.AI CI/CD integration requires one file and one API key. For GitHub Actions: create .github/workflows/bachao-security.yml, add your API key as a repository secret, and paste the workflow template. Every push and pull request triggers a scan automatically. For GitLab CI: add a security:vapt stage to .gitlab-ci.yml with a single curl step calling the scan API, pinning the key as a masked CI/CD variable. Both integrations work on self-hosted runners, cloud runners, and ARM infrastructure without network changes on your end.
SAST + DAST + SCA in one pipeline
Running SAST, DAST, and SCA as separate CI jobs means three scan cycles, three finding queues, and three dashboards to reconcile. Bachao.AI runs all three in a coordinated sequence: SAST analyzes source code for injection, auth, and logic flaws; SCA checks open-source dependencies for CVEs; DAST probes the running staging app dynamically for issues static analysis cannot see. Findings are deduplicated across the three scan types before they surface in the report — the same underlying vulnerability does not generate a SAST ticket, a DAST alert, and a SCA finding independently.
Blocking vs advisory gates for Indian release cadences
Indian engineering teams typically run weekly or biweekly releases rather than continuous deployment. Bachao.AI's CI gate supports both models. In blocking mode, Critical severity findings prevent the PR from merging. In advisory mode, findings are posted as review comments but do not block — useful while teams are building remediation habits. Both modes are configurable per repository and per severity level. A common starting configuration: block on Critical, advisory on High, informational on Medium and Low — then tighten thresholds as the team's security posture matures.
Jira & Slack triage workflows
Security findings that live only in a security dashboard rarely get fixed. Bachao.AI integrates with Jira and Slack so findings flow directly into your existing engineering workflow. Jira: each Critical or High finding automatically creates a bug ticket with CVSS score, reproduction steps, and the AI-generated fix suggestion. Slack: critical findings trigger an alert in your configured channel before the PR merges. Teams that route findings into Jira typically see remediation rates significantly higher than teams using standalone security dashboards — because the finding is where the engineer already works.
Cost vs Snyk / SonarQube for ≤50-dev teams
Snyk charges $25 per developer per month — a 50-person engineering team pays $1,500 a month or $18,000 a year. SonarQube Cloud pricing starts around $150 per month for small teams and rises with code volume. Neither tool was priced for Indian team economics. Bachao.AI offers scope-based pricing for small and mid-size Indian teams — starting free for small teams, with full access at materially lower cost than US-priced per-seat subscriptions. Request a quote on a 30-minute call and compare against your current Snyk or SonarQube bill directly.
Supported CI/CD: GitHub Actions, GitLab, Jenkins, Bitbucket
Bachao.AI integrates with every CI/CD platform Indian engineering teams run. GitHub Actions: drop a workflow YAML file and every PR triggers a security scan automatically. GitLab CI: add a security:vapt stage to your existing pipeline in minutes using a single curl step. Jenkins: call the scan API from a shell stage or the HTTP Request plugin with an HMAC-verified webhook for results. Bitbucket Pipelines, CircleCI, and Azure DevOps: supported via the same REST API with pre-built pipeline templates for each platform. No proprietary agent, no network changes required — the scanner probes your app from outside the perimeter, exactly as an attacker would.
Per-repo pricing in INR for Indian dev teams
Global DevSecOps tools price per developer at US rates — a 10-person team pays a subscription sized for US engineering salaries. Bachao.AI offers per-repo options so smaller Indian teams pay for what they actually use rather than headcount. A free starter plan covers basic SAST and secret scanning for early-stage projects. Full-team and enterprise pricing is scope-based — request a quote on a 30-minute call to get a number matched to your repo count and developer headcount. INR billing with GST invoices included; no USD conversion on your finance team's plate.
SAST + SCA + secrets scan in one PR check
Three scan types typically run as separate CI jobs — static analysis, dependency scanning, and secret detection — execute as a single coordinated pre-merge gate in Bachao.AI. SAST catches code-level vulnerabilities: injection, auth bypass, crypto issues, and insecure patterns across 30+ languages. SCA flags CVEs in open-source dependencies before a vulnerable package ships to production. Secret detection blocks API keys, tokens, and passwords from reaching the repo — running on every commit, not just scheduled scans. All three execute in parallel; findings are correlated across scan types so the same underlying issue does not generate three separate tickets.
DPDP-aware pre-merge gates
The Digital Personal Data Protection Act 2023 requires data fiduciaries to implement reasonable security safeguards. Catching data handling vulnerabilities before they merge — rather than discovering them at an annual audit — is one of the clearest demonstrations of that obligation. Bachao.AI's pre-merge gates flag common DPDP-adjacent issues: unencrypted personal data fields, missing access controls on data endpoints, logging of sensitive personal information, and insecure data deletion patterns. Each finding is tagged with the relevant DPDP Schedule I technical safeguard so remediation maps back to specific compliance requirements rather than a generic security ticket.
Secret Scanning for Indian Stack (Razorpay, UPI, Aadhaar)
Indian engineering teams integrate payment, identity, and KYC APIs that carry distinct secrets: Razorpay API keys and webhook signatures, UPI Virtual Payment Address credentials, Aadhaar eKYC tokens from UIDAI, GSTIN verification keys, and PAN validation API credentials. Leaking any of these to a public repository or CI log exposes payment rails and personal data — often without an obvious alert. Bachao.AI's secret scanning includes detection patterns for the Indian API surface: Razorpay test and live keys, UPI gateway credentials, Setu and Decentro API tokens, and Aadhaar bridge API keys. Scanning runs on every commit and across git history — catching keys that were committed, then deleted, but remain accessible in the repo's commit history.
GitLab CI Self-Hosted (incl. VPN-Only) Setup
Many Indian engineering teams — particularly BFSI and government-adjacent SaaS companies — run self-hosted GitLab on internal infrastructure behind a VPN. Bachao.AI's GitLab CI integration works on any self-hosted GitLab runner: on-premise, cloud VPC, or networks accessible only through WireGuard or OpenVPN. The integration uses a single curl step in your .gitlab-ci.yml that calls the Bachao.AI scan API from the runner — so the runner does not need to reach the public internet for the integration itself; only the scan target URL needs to be reachable from Bachao.AI's scan infrastructure. For fully air-gapped environments where even the target is not publicly reachable, contact ceo@bachao.ai to discuss a self-hosted scan agent option.